4 ms·

Right. I hear you. Pretend I'm a person who agrees with you about React (I might be, after all[1]). Have you ever seen that page "You might not need Jquery"?

Right. I hear you. Pretend I'm a person who agrees with you about React (I might be, after all[1]). Have you ever seen that page "You might not need Jquery"? Can you please write a similar blog post (or even put it into a comment here so that I can bookmark it) titled "You Might Not Need React"? I want to know what it is that React gives (maybe)millions of developers that you don't need. All those things that React is commonly used for: what are you using instead? Show snippets, please. So, yeah, throw me a bone here, please write "You Might Not Need React", because I can guarantee you that there are numerous devs who want to read such a post. Pretty please. [1] I looked at the React tech stack and learning curve for someone who only knows HTML, CSS and Javascript out of the entire web-stack, and noped right out of it.

kristopolous 2y ago
Here's a framework-free SPA I wrote about 2 years ago: https://9ol.es/pl/ https://9ol.es/pl/ as part of this project: https://github.com/kristopolous/music-explorer https://github.com/kristopolous/music-explorer This is all the code: https://9ol.es/pl/scripts.js https://9ol.es/pl/scripts.js . It supports, for instance, Bluetooth controls and I use it as my car audio player literally everyday It does take longer to learn and require more intellectual rigor to do things this way but you also get 10 year solutions instead of 10-month ones and things are way easier to debug, pivot, modify, repurpose, support, All the long-term things you have to do after the act of building when people are actually using the thing. Those are now easier
- lelanthran 2y ago
  Thanks; I've got pretty much similar projects. What I was looking for was literally a "You Might Not Need React" equivalent to the https://youmightnotneedjquery.com/ https://youmightnotneedjquery.com/ site. It doesn't need to be as polished as that, I just want to see <this is what react lets you do>:<this is how you'd do it without react>, even if all the "this"es in there were just patterns. I just want to be clear here, I'm not engaging in bad faith, or trying to prove something. I truly just want to know what react code is commonly used for, and what a vanilla solution would look like.
  - kristopolous 2y ago
    It's hard because it's conceptually and fundamentally different. Like what about useEffect? There's many many terse ways to implement this that in practice do the same things but in a slightly, arguably inconsequentially different kind of way. I'm sure there's a large legion of pedants out there who would have a field day slapping their suspenders against their chests nitpicking how "not exactly!" the alternatives are. If we can somehow avoid that trolly bullshit then I'm game.

kristopolous 2y ago

Here's a framework-free SPA I wrote about 2 years ago: https://9ol.es/pl/ https://9ol.es/pl/ as part of this project: https://github.com/kristopolous/music-explorer https://github.com/kristopolous/music-explorer This is all the code: https://9ol.es/pl/scripts.js https://9ol.es/pl/scripts.js . It supports, for instance, Bluetooth controls and I use it as my car audio player literally everyday It does take longer to learn and require more intellectual rigor to do things this way but you also get 10 year solutions instead of 10-month ones and things are way easier to debug, pivot, modify, repurpose, support, All the long-term things you have to do after the act of building when people are actually using the thing. Those are now easier

lelanthran 2y ago
Thanks; I've got pretty much similar projects. What I was looking for was literally a "You Might Not Need React" equivalent to the https://youmightnotneedjquery.com/ https://youmightnotneedjquery.com/ site. It doesn't need to be as polished as that, I just want to see <this is what react lets you do>:<this is how you'd do it without react>, even if all the "this"es in there were just patterns. I just want to be clear here, I'm not engaging in bad faith, or trying to prove something. I truly just want to know what react code is commonly used for, and what a vanilla solution would look like.
- kristopolous 2y ago
  It's hard because it's conceptually and fundamentally different. Like what about useEffect? There's many many terse ways to implement this that in practice do the same things but in a slightly, arguably inconsequentially different kind of way. I'm sure there's a large legion of pedants out there who would have a field day slapping their suspenders against their chests nitpicking how "not exactly!" the alternatives are. If we can somehow avoid that trolly bullshit then I'm game.