The conversation

Lessons learnedExperience excerpt · English

React single-handily killed it

… React single-handily killed it. It encouraged, usually required, all of the awful design patterns I used to chase all the junior engineers and interns about. This has become endemic in the JS world. Here's an example: did you know that the uuid npm used Math.random up through 2020 (v.7)? Cryptographically secure random number generation had been available in basically all browsers since 2011. 9 years. If I had an engineer submit that code, I'd rake them over the coals. Speaking of that, I'd usually need a half-time engineer on larger projects just for the management of the complexity . All of the various frameworks and updates and breaking changes. It was a 20/hour a week job just to stay on top of things. For instance, koajs. It's a bunch of dependency code of quality I would never let fly, but now I have to use it and grow my team, increase budget, push back deadlines - all to manage the piles. No thanks. I left that job, quit the industry entirely about 2 1/2 years ago. Reactjs was such atrocious self-aggrandizing bullshit, it made me quit programming. …

Original discussionA Rant about Front-end Development223 source comments · at import
4

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 4

Direct replies available in this import. Original-language excerpts.

TH

Could it be that you never tried to understand react and why the approach makes sense to millions of developers?

Full original
AE

That seems like kind of an overreaction. Sure, the first time I saw React I also thought it was an abomination. But in the end it’s fine. Different, sure, but there really is something to using the same language on both front and back-end, and not having to wonder about how to reconcilliate data and markup. React and the whole ecosystem gives you a thousand extra problems to care about, but it also takes a ton of them go away. It makes the simple things annoying but the hard things also merely annoying.

Full original
LE

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.

Full original
HU

Take a look at this video from 4 hours ago. You'll like it, I promise. It validates your opinion. React became an insanity. Just note all the nuances and minefields they are adding to an already bloated tech. https://www.youtube.com/watch?v=fXugpgknScY For one, it's 2024 and React still has this infinite newbie trap of double rendering. [1] But, it's perfect for job security. "Nobody ever got fired for buying solutions from IBM" became: "Nobody ever got fired for choosing React." [1] https://chanduthedev.medium.com/why-react-app-rendering-twic...

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.