2 ms·
Yeah, I cringe at a lot of it too. I think this is a result of all of the tooling and automated building that's "necessary" to cludge everything together. ES6
by berdon 10y ago
Yeah, I cringe at a lot of it too.
I think this is a result of all of the tooling and automated building that's "necessary" to cludge everything together.
ES6 features and TypeScript are great, for many reasons, but they don't work immediately in the browser. You need precompiling and something like CommonJS or SystemJS to handle importing libraries not defined in HTML. SASS/SCSS really improves stylesheets, tremendously improves them, but you need to...precompile. Finally, JS heavy apps turn into a hodgepodge of JS, CSS, and HTML that just doesn't really...sit well, so most people will use tooling to establish some sense of ordering.
That last step is both a boon and a curse. Automating the process makes development very easy and saves a lot of time. That tooling is also inherently complicated to an outsider and is a large, ugly barrier to entry.
- doingmyting 10y agoI don't know if I agree that automatating the process makes development easier. If I could punch someone in the face everytime I spent an entire night tracking down some obscure webpack error caused by some shitty library I imported, I'd need prosthetic arms by this. I am a part of the problem for using this crap :(