43 ms·

webpack and the entire "modern" js frontend... all because of an inability to manage versioning change across the standard browser js api... great for a giant

webpack and the entire "modern" js frontend... all because of an inability to manage versioning change across the standard browser js api... great for a giant megacorp looking to waste money on busywork and divide the workload across more employees (front-end devops?!?) less useful when you already have to compile a backend, don't really have a problem with ES5, and understand that you are basically only tasked with making your dom updates dependent upon data model changes, YMMV

gear54rus 8y ago
so because you don't see the obvious problem with being stuck on a single version of anything forever, webpack, representing progress in this case, is bad? nice try what does versioning has to do with bubbling, wtf?
- coldtea 8y ago
  >so because you don't see the obvious problem with being stuck on a single version of anything forever, webpack, representing progress in this case, is bad? In fact, the parent does see (and called) that "obvious problem with being stuck on a single version of anything forever". That's why he doesn't cheer for the band-aid solution that's webpack and doesn't thing it "represents progress".