But will they fix command line autocompletions?
Readit Newshungryhobbit commented on Anthropic acquires Bun bun.com/blog/bun-joins-an... · Posted by u/ryanvogel
What a terribad front page!
Telling me to install an extension without ever telling me what that extension actually does is the most rookie move ever!
hungryhobbit commented on Launch HN: JSX Tool (YC F25) – A Browser Dev-Panel IDE for React · Posted by u/jsunderland323
Surprised by all the hostility in the comments: if this tool actually works as described in the video, you've created a whole new generation of dev tool with JSX Tool!
hungryhobbit commented on Launch HN: JSX Tool (YC F25) – A Browser Dev-Panel IDE for React · Posted by u/jsunderland323
Pretty cool project! I love to see progress on the UX of how we write and manage code.
My honest feedback to you here is, this isn’t very valuable by itself as a local dev tool. Make it so it can be run targeting a git repository with live preview and deployment to a real environment and you may have something much better!
Take a look at Theia IDE, maybe you could find a bridge to do that?
Good luck on the launch!
You seriously don't think anyone develops locally in 2025?
Recently switched to Harper https://writewithharper.com/, a vastly superior grammar checker
Harper is a nice alternative, but it's still rough around the edges.
For instance, if you have a misspelled word, and the correction options come up, you can't get out of them and return to where you were by using the keyboard. You can hit Escape to close them, but it doesn't restore your place in the text field, so you have to use your mouse to get back where you were.
As a programmer who tries to use the keyboard as much as possible, this (incredibly easy to fix, I'm sure) bug drives me crazy! Almost enough to make me go back to Grammarly.
https://colton.dev/blog/tailwind-is-the-worst-of-all-worlds/
This is a pretty good post.
In general, I don't think `class` is a good place for styling.
What a terrible article! The author is so very ignorant, but presents themselves as an expert :(
I barely got into the "dunking" on Tailwind when I saw this.
> If you misspell one of these plain strings your editor is not going to tell you.
Ummm ... sure, if you're one of the 1% of devs who refuse to use a linter. Either the author is part of that 1%, or maybe they just weren't aware of Tailwind's linting capabilities (https://tailwindcss.com/blog/introducing-linting-for-tailwin...).
Now, to be fair, they wrote the article in 2025, and Tailwind linting was only released five years prior (in 2020) ... five years is hardly long enough to learn relevant tech for your industry /s
The rest of the article seemed similarly ill-informed, with the author fixating on meaningless byte-size differences in contrived examples. However, he ignores the fact that Tailwind is used on some of the most performant sites on the Internet. He also ignores the fact that (for 99% of sites at least) sacrificing a k or two of bandwidth is well worth it for a major increase in developability.
With Tailwind you completely get rid of stylesheets: that alone is huge! There's a reason why so many devs use Tailwind: they don't worry about minimal file size differences, but they do care about massive savings in development time and complexity reduction.
hungryhobbit commented on React vs. Backbone in 2025 backbonenotbad.hyperclay.... · Posted by u/mjsu
People don’t or even can’t remember how was front end development before React/Flux/Redux. You could easily had problems with state management even with less than 1000 LOC simple pages. Of course, you could mitigate it, but it wasn’t trivial at all.
Look, I wrote one of the only published books on Backbone, and it will always have a special place in my heart, but ... the OP has no idea what he is talking about.
Backbone employed a two-way data binding flow. You're responsible for updating the models (ie. state) (way #1) when the user triggers events, AND you are responsible for updating the DOM whenever the models (ie. state) changes (way #2).
In React, they used a revolutionary new paradigm (flux), making it so you only worry about one direction (updating the models/state in response to events); you never render anything (React renders everything for you in response to state changes)!
If you've tried developing a non-trivial site with both, it quickly becomes apparent how much that one difference completely simplifies a huge aspect of development.
Dead Comment
Author and his spouse both work for pharma companies.
So they actually know what they're talking about?
Fear and hatred of experts is how we got into this mess. If pharmaceutical executives aren't all cartoon mustache-twirling villains (and they're not: many actually want to help sick people), then maybe not every employee is either?
Happy to answer any questions