4 ms·
If 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 miss
by untog 8y ago
If 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.