Funding Open Source: How Webpack Reached $400k+/year • Hacker News Board

Re: Funding Open Source: How Webpack Reached $400k+/year

#61

Post by thelarkinn » Mon, Nov 06, 2017, 1:58 AM UTC

Waterluvian wrote: post #7

techdragon wrote: post #4

Earlier 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…

JS needs a standard library that ships in all the browsers. "There, you're all using the same tools. They're not perfect for any of you but they're good enough for all of you." I noticed recently that module support is now in chrome. When module support lands for all the browsers, it's going to be a huge step toward getting rid of a lot of build complexity. I've been writing vanillajs toys the past month and wow have…

Native modules are still pretty slow. So much that we as an oss org are working with browsers to help them find ways to make them faster. Although native modules will be nice, we still believe that bundlers are still needed to ship the fastest most optimized code

Re: Funding Open Source: How Webpack Reached $400k+/year

#62

Post by techdragon » Mon, Nov 06, 2017, 9:09 AM UTC

arglwarg wrote: post #10

techdragon wrote: post #4

Earlier 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…

> By not hiring a JavaScript developer. aka "the lisp curse": http://www.winestockwebdesign.com/Essays/Lisp_Curse.html

You posting this link and giving me a chance to read it has been a highlight of my day. The fundamental lispishness of JavaScript by way of scheme explains everything I hate about working with JavaScript after reading that essay.

Re: Funding Open Source: How Webpack Reached $400k+/year

#63

Post by naspeh » Mon, Nov 06, 2017, 10:52 AM UTC

thelarkinn wrote: post #58

infinity0 wrote: post #44

>> fuck webpack >> sorry to hear you feel this way! [..] >> [..] When I first read the quote, I thought "that's nice of webpack". Then I saw this: > The greatest power you have for haters or trolls is love. I would not call someone saying "fuck webpack" a hater or a troll, I would call them a frustrated user. OTOH, you can turn a frustrated user into a hater or a troll by dismissing their concerns or by trying to shi…

It's more then nice words. It's showing you listen, it's empathizing, it's putting yourself in that persons shoes. To fix things like usability we have a lot of long work ahead of us and we want to do so. I don't consider that person a hater etc. I think maybe the transcript of my talk didn't really mean to couple that statement with that slide etc.

Anyway, thanks @thelarkinn for great write up, it's just good success story to learn from. Keep rocking!

Re: Funding Open Source: How Webpack Reached $400k+/year

#64

Post by patcon » Mon, Nov 06, 2017, 11:21 AM UTC

infinity0 wrote: post #50

Ar-Curunir wrote: post #48

Earlier quoted context omitted.

Lol you absolve frustrated users of all blame. Even if you're frustrated, it's not difficult to be civil.

I don't consider it uncivil for someone else to say "fuck [my project]" after having trouble with it. I would consider it uncivil to write me messages saying "fuck you, you are an asshole for writing [my project]". Maybe that's just me.

I personally feel that's just you. I'm genuinely happy for you that you can be unfazed, but many many people can't -- it costs them and taxes them. Someone not sticking up for those latter folks makes for a world where only folks with your brand of relating can cut it. That's kinda needlessly limiting, when the cost of things being better is just setting our collective arbitrary bar a little higher :)

Holding people to a higher standard doesn't make the world any worse -- it just means those people have to adapt, but that makes for a world that more and more of us (even those without your sorta soft skills) can navigate. That seems healthy?

Re: Funding Open Source: How Webpack Reached $400k+/year

#65

Post by gortok » Mon, Nov 06, 2017, 5:43 PM UTC

aaron-lebo wrote: post #8

gortok wrote: post #6

Earlier quoted context omitted.

I had a similar issue very recently with webpack. I was attempting to use its bundling capabilities to bundle css and js files for a web application. Believe it or not, the very simple end-user use case of bundling css is not a part of the core library, nor is it well demonstrated or explained in the docs. After a few hours, I simply gave up and continued to use gulp. We don’t treat user time as precious because our…

Does this not work? https://github.com/webpack/webpack/blob/master/examples/css-... https://webpack.js.org/loaders/css-loader/#src/components/Si... Note: examples at bottom of second link, found it by searching "css" in the doc site

I've seen those docs. I tried implementing webpack to replace our gulp bundler (which was initially an ASP.NET Core Bundler) for an ASP.NET Core project.

Unanswered questions that I left the project with (I time-boxed myself to 4 hours; as that was the initial length of time it took me to get gulp up and running in totality):

- Why do I need a require for my CSS? I literally want to replace the css with its minified form. Maybe even bundle it together (I'd settle for the former).

- How the heck is web-pack doing all this; and why is the package called 'extract-css-loader'? I don't want to extract CSS; I want to minify it.

- If I want a source folder and a dist/ folder for my CSS; how would I get Webpack to update the URLs in the .html files?

- Am I crazy for still doing this through HTML? Is there a 'better way' ?