3 ms·
We all do basically the same thing in every app ever, it's the fragmentation that is such a huge pain with JavaScript. Most apps don't have to be unique snowfla
by tjholowaychuk 10y ago
We all do basically the same thing in every app ever, it's the fragmentation that is such a huge pain with JavaScript. Most apps don't have to be unique snowflakes, we make them that way with hacky css-in-js and so on.
Webpack is great for what it is, but I strongly disagree that people should have to understand the config boilerplate aspect to get something functioning. All it does is prevent you from doing real work, not to mention if you're working on dozens of apps, this quickly becomes a hellish thing to deal with.
- hashkb 10y agoI have great respect for you but this seems a bit mean spirited. Why shouldn't devs want to be as many things as possible? Is css-in-js is more ridiculous than regular CSS? I've left regular CSS behind and gained a lot of sanity.
- tjholowaychuk 10y agoIt's just my opinion of course :) but I think css-in-js is a step backwards in the majority of cases. I do like CSS modules in terms of scoping / modularity, but I don't want to replace CSS with (what I consider to be) really gross JS implementations. I don't want to discourage people trying new things, but I also don't want people to waste thousands of collective hours dealing with crazy configuration. I think toying around with those things are fun for people who get paid by startups etc, but for those of us who simply want to get things done, the ecosystem is not enjoyable.
- fuzionmonkey 10y agoI think you are conflating multiple things. There's several JS styling libraries have literally zero configuration (and don't involve build tooling, etc). They "just work" out of the box.