[deleted]
Funding Open Source: How Webpack Reached $400k+/year
11–20 of 65 posts
Re: Funding Open Source: How Webpack Reached $400k+/year
#12The difficulty I have with Webpack is that there does not seem to be any unifying principle of how things work.
The stream model of gulp and the resulting highly structured code that most often results means that I can generally find and fix bugs quickly, this is even possible in the horribly convoluted gulp file that we use at my current working place. In my experience when you have even a bit of webpack and there is a problem somewhere it can be difficult to figure out the cause because it seems every capability of the system works in its own way.
Re: Funding Open Source: How Webpack Reached $400k+/year
#13Maybe they could employ a programmer who knows how to turn unbelievably complex software into incredibly simple software that doesn't include constant relentless breaking changes.
Which breaking changes are you referring too? I remember updating some configs in the jump from 1 -> 2, but none since then
Re: Funding Open Source: How Webpack Reached $400k+/year
#14Earlier quoted context omitted.
By not hiring a JavaScript developer. More seriously... I've just today finished updating some C++ code that integrates the Chromium Embedded Framework into Unreal Engine 4 to work with current versions of both CEF and UE4 and even building all this, Separate CEF sub process binaries without a strait forward make && make install, and debug builds of the entire unreal engine editor to track down CEF initialisation err…
It just sounds like you found a quality C++ library, there's thousands that are horrific messes. Compiling some of them is unbelievable amounts of frustration, which npm mostly avoids. Webpack works fine and is easy to use, part of the issue is that people criticizing JS don't know what they are talking about because they don't actually use JS that much and they don't understand why that makes their criticism not tha…
Webpack is terrible to use. Very inconsistent and results in a mess of code for your configuration. I suppose part of that comes from the 10+ loader interfaces it uses under the hood. But most of it comes from organic growth (I assume) and the fact that there are no JavaScript standards (e.g. no filesystem or pipe like interfaces, the competing module systems and no standard library)
This is a nice guide to starting with webpack that I think describes it very well: https://what-problem-does-it-solve.com/webpack/index.html I'd recommend this guide to anyone who is trying to get started with webpack.
I wish there was an intuitive way to chain JavaScript file transformations together, but it doesn't seem like there is one yet. Webpack is close, but I think it has too much baggage to get there.
Re: Funding Open Source: How Webpack Reached $400k+/year
#15Re: Funding Open Source: How Webpack Reached $400k+/year
#16Earlier quoted context omitted.
How do you hire programmers like that?
By not hiring a JavaScript developer. More seriously... I've just today finished updating some C++ code that integrates the Chromium Embedded Framework into Unreal Engine 4 to work with current versions of both CEF and UE4 and even building all this, Separate CEF sub process binaries without a strait forward make && make install, and debug builds of the entire unreal engine editor to track down CEF initialisation err…
Except it’s more like “ha ha only serious”. I work with people who know nothing but boot camp JavaScript and it’s a goddamn nightmare.
Re: Funding Open Source: How Webpack Reached $400k+/year
#17Maybe they could employ a programmer who knows how to turn unbelievably complex software into incredibly simple software that doesn't include constant relentless breaking changes.
Not if they use JavaScript. Somehow the language and the ecosystem around it breed nothing but overly complex, brittle software. I blame bootcamps.
Re: Funding Open Source: How Webpack Reached $400k+/year
#18Maybe they could employ a programmer who knows how to turn unbelievably complex software into incredibly simple software that doesn't include constant relentless breaking changes.
How do you hire programmers like that?
Seriously, don’t hire JavaScript programmers. Why is this so difficult? There’s a goddamn one-liner in npm that determines an array’s length, and like a billion packages depend on it. Anyone who has JS on their resume and is proud of it will soon find their resume as part of a child’s birthday confetti.
Re: Funding Open Source: How Webpack Reached $400k+/year
#19Maybe they could employ a programmer who knows how to turn unbelievably complex software into incredibly simple software that doesn't include constant relentless breaking changes.
Which breaking changes are you referring too? I remember updating some configs in the jump from 1 -> 2, but none since then
Webpack 1 -> 2 had several breaking changes, primarily around loader configuration syntax. The migration guide at https://webpack.js.org/guides/migrating/ covers the changes. 2 -> 3 was primarily internal changes, with little to no migration steps needed other than bumping the installed version.