5 ms·
Jeez. Why does anyone do this to themselves? All the work by the javascript guy and then all the work by the server to produce simple HTML/CSS output. I am pos
by sureaboutthis 8y ago
Jeez. Why does anyone do this to themselves? All the work by the javascript guy and then all the work by the server to produce simple HTML/CSS output.
I am positive someone will come here and make a claim of large, dynamic sites and reddit's favorite nonsense phrase about DRY but I am also positive more people learn React because online articles tell them to than a real need for them.
If one would spend all this time learning HTML/CSS/Javascript fundamentals, and how to properly use them, they would have the same questions I have after 14 years of doing this, for companies large and small, as to why anyone bothers with this, Angular, and all the others. It just makes no sense at all.
- k__ 8y ago"more people learn React because online articles tell them to than a real need for them" Yes, like with most software. But I guess the average dev is better off with learning React/Vue/Angular than cobbling together its own thing
- gear54rus 8y agoThis isn't react only, it's component approach in general, do you, after 14 years, really denounce component approach?
- sureaboutthis 8y agoAre you saying one cannot use a "component approach" without React? That's like saying I'm denouncing cars cause I don't like Chevys.
- realusername 8y agoYeah you can totally reinvent your component system yourself, or you can just use React which is used in production on thousands of websites and big products with top-level support of hundreds of engineers.
- sureaboutthis 8y agoOr we can use our own component system, which we created ourselves at least 10 years ago, and not use React at all. When you are into programming, like we are, you think of these things long before some big company tells you what to do.
- pault 8y agoI am into programming, like you are. I also would rather benefit from the thousands and thousands of developer hours that have gone into the react core, and not have to train every new team member on a crufty ten year old bespoke codebase. I do try to keep my external dependencies low, but core utilities are not worth rewriting from scratch.
- sureaboutthis 8y ago>a crufty ten year old bespoke codebase. Anything you want to show up to us, bring it on, and our code will run rings around anything you can give us while spitting in its face. We are high performance. Don't think that we wrote the first run 10 years ago that we haven't modified and improved and left it as is all this time. If you think you need react to do your job, then you can't work for us. We are professional programmers.
- dang 8y agoI appreciate that you've mostly stuck to being civil with this account, but please don't cross into flamewar like this. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- abiox 8y agosadly we aren't all as smart and worthy as you are, and don't have a decade old react-like hanging around. some of us even prefer the idea of using an open source library for the various benefits of doing so.
- dan1234 8y ago
- untog 8y agoIf you've been in the industry for 14 years, know JS and CSS inside out, and still don't understand why anyone wants to use React... I think you're the one missing some understanding, not the people who choose to actually learn the framework in question.
- olavgg 8y agoI disagree, everything is much simpler without React. I'm actually working on writing a tutorial for creating structured code for dynamic content with vanilla JS. With Ecmascript 6, a lot of advanced concepts has become much simpler and easier to read.
- dan1234 8y agoI hope you'll submit it here when it's ready, I'd quite like to see a good "Stripped back modern JS" series.
- ng12 8y ago> everything is much simpler without React What's "everything"? Writing a mostly static webpage with a few moving bits? Yeah, sure. Building and maintaining a complex SPA on a team of 4+ developers? I'll take React any day.
- untog 8y agoSounds like you're proposing a framework, just one that people write themselves. I'll be interested to read your piece though, I'm curious to know how ES6 makes things like state management simple.
- purerandomness 8y agoNo. Remember the repeated rise and fall of NoSQL, and the repeated rise and fall of mainframes/cloud, and everything else that's happening cyclical. Style-Attributes in HTML, CSS-in-JS, etc. There's a coaching gap because of the high demand in dev roles. New talent freshly out of uni and coding bootcamps lacks basic concepts and has to go through all the same architectural pitfalls and relearn the same mistakes over and over again. The longer you're in business, the more such cycles you see repeat.