You know what?
Fuck Webpack and Babel, too.
They're way too complicated and finicky to set up.

I want to write a simple library, not a freaking research paper.

I still don't fucking understand the concept of web frameworks. The web IS a framework. Maybe people don't do enough ground-up development anymore. No web developer has ever needed to go even close to reinventing the wheel.

Not needing to reinvent the wheel is a good thing, I would say, but it has taken a toll on the way people write programs. Devs are so afraid of writing something themselves that they add megabytes of bloatware to their websites, just to give a cushion of code between them and any sort of work they would need to do.

If I can't get a layout to do what I need, my first thought is to render it on a canvas, not to import some crazy framework.

Then I just go for flex because what can't you do with it.

@AlgoRythm while I agree with you on frameworks, I'm not adding a framework; these two are build tools. I want destructuring and private class members. I want code that works on all browsers.

I can't have those two features without transpiling via babel, and can't do the latter without writing a neigh-unreadable, unmaintainable mess because polyfills and browser quirks... or again: using babel.

I hate that setting up a javascript project takes longer than writing the freaking project itself.

I'm writing my lib in ES6, the consumers can decide which environments they want to support (what to polyfill). I package it up with rollup and call it a day. Here's what the author of webpack has to say about it: https://github.com/w3ctag/...

@Root I knew what Babel was (admittedly only ever heard of webpack and have no clue what it is) but I saw web tools and just went off, I'm always so angry about this shit... I don't know, it was just a knee-jerk reaction to rant about frameworks for the hundred millionth time.

I love having all the ES6 features, but damn that build pipe is prone to errors...

I just built an entire Vue app with the script tag and completely ignoring webpack! And it's super lightweight and performant; FUCK the bundling and packing and transpiling bullshit.

Dear JS "ninjas", if your edgy "framework" needs webpack, you can bundle your fist and shove it where the sun doesn't shine

Why not for once appreciate that someone out there is spending their valuable time to develop libraries like Babel? I don’t understand why most of the developers are full of hatred nowadays. Don’t like it? Don’t use it, simple as that.

@lambdaCurry @Bitkris
Obviously webpack and babel are amazing projects, but fucking hell, setting them up is a bloody convoluted mess. 😡

webpack makes me cringe, parcel on the other hand is very good out the box

@Root appreciated :)

@hell 😉

@gruff parcel is totally magic :v

"I want my code to work on all browsers"

This is like saying you want your gas station to accomodate LEADED gasoline for the older cars, and you then put the effort forth to install extra pumps in your gas station to accomodate for such cases. What's that you say? They don't make leaded gas anymore? Well we can bundle the refinery into the whole deployment package.

There are reasons why IE is not a thing anymore.

And if any browser out there wants to do things their own way, then it better be better than the growing standard use cases that majority of the best browsers are accomodating. Otherwise, take that shit and get it the f*** outta here.

I grow tired of trying to keep up with all the "modern" dev bullshit... and at this rate I think it's only going to get worse the more we cater to this type of ass backwards bloated nonsense.

@Root I find it easier to have a message warning that their browser is incompatible.

And I might be gracious to put the extra work into telling them which browsers are compatible.