The bug won't get fixed right away, most will just work around it, use different plugins, copy/paste yet another webpack config etc. Why? Because if a bug shows up in a build-system you stop a million developers from being productive. The web-way of: we can fix it and everyone will reload the browser, leads to a "don't care" attitude.įor web/backend this is approachable, though still not good.įor build-systems this is terrible. You have to spend many brain-cycles on learning Browser-problems, which muddles your understanding of the language. ![]() The JavaScript-ecosystem just isn't very productive for multiple reasons. I have written JS since 1997 and kept up with ES6 and so on over the years. That is because it is NOT written in JavaScript. Me too! I dread package upgrades because it can instantly turn into an all-hands-on-deck emergency, and these are just the stand-alone packages, not all the ones I mentioned above. As I read through pages of closed-but-not-really GitHub issues for each package, sometimes going back years and years, it feels like a constant stream of hacking that erodes the well-intentioned first versions. Only, it is too many cooks + death by a thousand cuts. I appreciate what the developers are trying to do, I really do. I naively thought I could webpack with electron+vue+pug+ts and was soundly smacked down repeatedly, even after trying the boilerplate from each components' docs. ![]() I've been spending an hour or so a day coming up to speed for the past few weeks, and every yarn/npm package I installed had some kind of error/warning that required a hack, or version contortion. I recently was convinced to start using a packer (webpack, parcel) and was blown away by the hoops people have to jump through to make stuff work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |