Earlier quoted context omitted.
Brunch.io maybe?
No, brunch is a major step backwards. So are Browserify, gulp, and grunt. We need something new.
Funding Open Source: How Webpack Reached $400k+/year
51–60 of 65 posts
Re: Funding Open Source: How Webpack Reached $400k+/year
#52>> 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…
Re: Funding Open Source: How Webpack Reached $400k+/year
#53Earlier 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.
Re: Funding Open Source: How Webpack Reached $400k+/year
#54Earlier quoted context omitted.
Brunch.io maybe?
No, brunch is a major step backwards. So are Browserify, gulp, and grunt. We need something new.
It's easy to complain about something without offering an alternative. You just shot down every tool, so let's see this impressive tool that you surely must have in your head.
As a tool becomes sufficiently generalized, it always picks up what looks like cruft in the simple cases. But the simple cases cannot tell you how good or versatile a tool is because you can solve a simple problem with virtually anything. That's why people who need to concat 2 files think you can replace all of Webpack with `cat`.
The cycle continues when someone creates a new tool with a simple API because it doesn't generalize, but then they realize they need to extend it such that it generalizes over the real-world problems that people have when bundling, like hot reloading (different than live reloading) and code splitting and arbitrary transformations.
Re: Funding Open Source: How Webpack Reached $400k+/year
#55Earlier quoted context omitted.
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…
Issues you might have are related to broken web frameworks (angular4) than webpack itself.
Re: Funding Open Source: How Webpack Reached $400k+/year
#56>> 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…
Sean Larkin's favorite game is to respond to every single Tweet containing the word "Webpack" and not help them in any way
I don't consider this a game, I take it pretty seriously to help others. However, I am human like many others and as of late I've been a bit caught up with family. If this happened to you then by all means I can own it and apologize. Otherwise shoot me a DM if you really need help and if I can't help I'll find someone who can
Re: Funding Open Source: How Webpack Reached $400k+/year
#57How did you get the companies to sponsor? It seems like once you are above a certain threshold/community level, it makes sense for a company, but did you just reach out or was it people you already knew? Or people you bumped into while talking at a conference? But how do you know if they are the ones at a company that can sign off on sponsorship? This very much seems like "sales", how does an Open Source-loving engineer get good at sales?
Re: Funding Open Source: How Webpack Reached $400k+/year
#58>> 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…
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.
Re: Funding Open Source: How Webpack Reached $400k+/year
#59The state of Webpack does not reflect a 400k/year budget. The docs, API, source code, ecosystem... so happy to hear people making software engineering money get a second salary to keep doing this. We're all waiting for the thing that will replace Webpack so we don't have to keep using it. Maybe we should just go and make it.
I think it does. This area where webpack is trying to shine is just over-complex, so the tool can't be simple, that's it. And most importantly as for me, developers who works full-time on such projects can sustain the higher quality and improve it over time and if you chose it for now it may been relevant year later or 2-3... I hope at least.