Re:Future JavaScript: what is still missing?
by tonto on Sunday January 27, 2019 @10:54PM
(#19015235)
We are now in an intermediate hell of Babel and webpack though...the language is cool, but the toolchains are really crazy right now. Someone could dismiss my argument if they got a comfy setup but often times if you're doing even just a little trailblazing you get into some wtf territory. I spent all day this week setting up a karma test cause my node module was failing only in the browser so then I added Babel and karma-webpack, but then regenerator runtime kept giving me errors, then mixing require() and es6 import gave me insanity errors and I almost gave up. Deep googling gave me barely enough clues to get through it...
[ Parent
| on HN ]
Re:Future JavaScript: what is still missing?
by scarface74 on Sunday January 27, 2019 @11:03PM
(#19015262)
I’ve avoided any serious JavaScript development for years because of crap like this except when absolutely necessary. I’ve learned it well enough to get pass “full stack developer” interviews, but as soon as I get hired, I get migrated to the back end.
I’m just now putting the finishing touches on my first Node/Express microservice for production. I’m putting off front end development for another year or so.