jackdh

I've followed all the main migrations and I've say they where really quite smooth, can't remember having any major issues and each time it tended to be worth it.

I was always roughly of the mind that Backblaze was just too close to the "If it's too good to be true it probably is", seems like that may have been a good decision.

Depending on how you define "new" but there are certainly examples of this, Spotify is the first to come to mind, AWS could be another.

Hardly, they banned fully disposable. You can still by them but now you can swap in a refill cartridge. The price of this refillable one is the same as the original.

Many places apparently don't even sell the refills so it's practically the same.

Sounds like a nice way for someone to get a free fence.

My point is that there is no one CSS library to rule them all and likely never will be. The closest to that is going back to pure raw CSS which I highly doubt people will do.

And yes while it's obviously not ideal to have a hundred competing libraries in your code, you can create what works for you / your team.

I used to be a naysayer of tailwind. However after getting practically forced into it I'm now drinking the koolaid. Yes things like having to duplicate styles using multi cursor is kind of silly, however for the vast majority of the time, having the styles written clearly each time, for me, makes it worth it.

There is also nothing stopping you mixing and matching.

Yes that worked so well the last time ha.

Ha, that is definitely not type of abandoned that I was expecting. That poor chap who was killed, what an incredibly unlucky event for him.

Unless you're with Apple, in which case a solid 8GB should be enough for the next decade or so! /s

It hadn't even occurred to me that working on OSS outside of work hours on your own equipment might be against policy and get you fired.

Is this perhaps only a US thing? I've never heard of that in the UK / Europe.