Hmm ok

Linked in sucks but I have to say all my jobs have been found by recruiters contacting me through it.

I am fine with installing apps I use or want to try. I’m also okay with forgetting them and wasting the space honestly. All of that probably would take me ten years of “bloat” to match windows out of the box so yeah that’s not bloat, that’s just making software decisions. This post is really criticizing people for installing software? Wtf

They also stay pretty current with the kernel and many other packages. Their new DE is hopefully going to be good. They are trying to make a better gnomish experience. We’ll see.

That’s interesting. I have run Pop_OS! since around 2021 and I’ve had very few issues.

It’s basically a rolling release so that’s false

Ah very clear now

BoTh SiDeS tho

Pop_OS really gets less love than it deserves. imo it should replace Mint as the standard go-to recc.

What?

How many are on July 4?

What the fuck would I have to be proud of? The US has been on a downward trend for a long time and that’s accelerating

More like those completely legitimate social media accounts said he didn’t do it

He is guilty.

As much as one can take something like that back

Many modern web apps have different components that aren’t HTML

What do you mean by this? Web Components?

I am not sure I understand the second paragraph either. I get that if you’re doing things well, TW class names can be applied in a non-insane way. Still rubs me the wrong way as a concept though.

tailwind removes the abstraction that you don’t need, since many people in react tend towards one scoped css file per component with classes for each element anyway

What abstraction does it remove? In my view, it just adds slightly different abstractions. Instead of knowing an element has a clean block of rules with set meanings, you get a long (potentially grossly formatted/ordered) string of class names that mean the same thing as the CSS properties for the most part, but you’ve gotta learn a new set of aliases for them. If I am working on someone else’s component, one of these scenarios is way easier for me than the other. Even when I worked with TW for a while, I never could really remember a lot of those class names.

csszengarden is cool but I haven’t seen the html/css split help an end user, or really even me as a developer.

You may have never refactored or reskinned a site. I have several times. The hardest projects like that were when content and presentation were tightly coupled. Those felt like pulling teeth to get done. important! every time a dev buried a style tag somewhere deep in some (for all intents and purposes) unchangeable Java code… shudder When they were loosely coupled, it was fun and went much easier.

edit: respect for knowing csszengarden. That site honestly was the first time I learned this principal and saw it applied. I’ve themed several websites over the years so I’ve used the concept myself.

Yep. The syntax is slightly cleaner to read probably, but that’s about it.

I cannot tell if you’re saying tailwind is taking away from useful abstractions or adding to them. I think it’s taking away from them. A whole bunch of class names in the page is opposite to what we were taught and there was a good reason for the lesson: content and presentation should be defined separately. This lends flexibility, readability and accessibility. Tailwind doesn’t help with anything but preventing a breakage in another component/page. To me the reason to value this trade off is that you don’t want devs to “have to care about css” which is a bad sign to begin with. It says “we think the way the web is built is bullshit, so let’s just try to work around that with the latest attempt to make it better”. The web is not bullshit. CSS is beautiful. Embrace the challenge. (Sorry I’m only halfway directing this rant at you)

And they hated him because he was right.