3 ms·
Oh good, another .js. Throw it in the pile. The quagmire of subtly different JavaScript frameworks is definitely the leading reason I avoid front end work like
by taywrobel 6y ago
Oh good, another .js. Throw it in the pile.
The quagmire of subtly different JavaScript frameworks is definitely the leading reason I avoid front end work like the plague.
- swyx 6y agoin this case, they are related toolchains. the title and premise is just really bad clickbait.
- warent 6y agoIf you just said the first two sentences and we could have inferred that you don't work in frontend. Every technology has tradeoffs, and frankly I'd like to hear about this mystical backend panacea you're implying.
- taywrobel 6y agoI generally work in go, where the standard library covers the vast majority of use cases. If you have some crazy specific performance needs there are frameworks for that, but generally vanilla go will get you where you need to go. I’d love to see a “modern” web app built in pure JavaScript without a framework.
- warent 6y agoThat's _most_ modern web apps. React is a library, not a framework. jQuery is also a library. That covers probably about 95% of the web today.