3 ms·
> It's always the CSS framework, the bundler, the minifier, the something else. Well, for 4 things, the rate of change of that group is on average 4x the rate
by michaelcampbell 6y ago
> It's always the CSS framework, the bundler, the minifier, the something else.
Well, for 4 things, the rate of change of that group is on average 4x the rate of any one thing.
I get your point, but it's rare that something that would cause a break in any one framework is not some biggish change IN that framework, so ...
> It's not like they ever give me any startlingly new benefit;
... may not be a "startingly new" change FOR YOU, but it may be for someone else.
- savanaly 6y agoI mean, looking at the change notes for e.g. Tailwind 2.0 which is the latest one to cause me pain, hardly anything in it was a response to changes in the CSS handling of the browsers. It's all shuffling of namespaces, additions of little conveniences, etc. The sort of thing that makes sense in isolation, but overwhelms one when every part of your stack needs to do it several times per year. Sure, Elm could do the same thing, rearranging the chairs on deck, and make some people marginally happier. I'm really happy it doesn't though because of the externalities that would cause.