Unlikely, I've used apps similar to this such as passbook [0] for a while now and they're still up.

[0] https://apps.apple.com/us/app/passbook-wallet-pass-creator/i...

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

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.

> There is also nothing stopping you mixing and matching.

Yes, common sense. Having multiple approaches to solve the same thing tends to be a bad idea.

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.

> The closest to that is going back to pure raw CSS which I highly doubt people will do.

Huh? Tons of people write vanilla CSS which is getting better every year.

Very very few people, in practice, write vanilla CSS. They use libraries and frameworks often, like Bootstrap. Sure, that might be "vanilla CSS", but you didn't write it, presumably because you didn't want to.

Look, after a certain point we have to call a spade a spade and acknowledge that CSS is just too cumbersome, too awkward, and too complicated for most developers and companies. How much CSS do you see that seems to be read-only? People just... tack on to the end of the style sheet, right?

The promise of re-usability is great, but is it actually happening? IME, no.

> Very very few people, in practice, write vanilla CSS.

That's not what I've seen. Most frontend developers I know usually write CSS (or SCSS previously).

> CSS is just too cumbersome, too awkward, and too complicated for most developers and companies.

Really?

I disagree but are you arguing TW solves any of that?

This is an extremely limiting view. They are both CSS at the end of the day. If extracting the complicated inline TailwindCSS class to its own vanilla CSS class makes sense for readability then what's the harm? You could also just define your own variables. Tailwind gives you full control to do this.

The harm will be in a complicated project where you might have to figure out where some styles are coming from.

Yes that worked so well the last time ha.

There is a very good set of podcasts[0] by Cautionary Tales about the German V2 rockets in WW2 which tried to use this. It was so hard the Allies allowed them to continue wasting money on it during the war. Well worth a listen to if you're into that.

[0] https://timharford.com/2023/07/cautionary-tales-the-v2-trilo...

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.

Can you imagine the odds? Literally ... any of us could go, at any time. That's what gets me whenever I think about this.

Ça plane pour moi

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

Who needs to run anything other than TextEdit.app anyway.

Vim

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.

That is incredible to read. It's one of the things which makes you stop thinking about all the awful things in the world and realise just how incredible modern science and medicine is.