disagree. Colocation seems great when authoring, but it comes at a big cost of downstream tech debt

there could be better ways to ease the burdon of naming things, while preserving cascade and the actual full features of CSS

Tailwind is a mirage, a shortcut to not having to do the important stuff by stacking wrappers on top of wrappers and redundancy

And the "fragile" part is exactly the same thing with tailwind, it all remains low specificity class names

Every line of CSS you write creates tech debt, it has nothing to do with tailwind.

I'll second that, this is extremely annoying and exhausting.

It feels like the slightest occurrence of a less-than-ubiquitous pattern or any word not regularly used by the majority of the population instantly spawns a sleuth of newfound linguists who'll pitch in to explain how this certain marker ought to be proof of AI origin.

This does nothing for the conservation, except helping the claim that AI will erode and dumb down our language become a self-fulfilling prophecy when people start feeling pressured to use the most dumbed down, simplistic and rhetorically bland way of expressing themselves to avoid any "suspicion"

Given the premise, one could also say we nerds are forever happy.

We've been running our services on Hetzner for 10 years, never experienced any significant outages.

That might be datacenter dependant of course, since our root servers and cloud services are all hosted in Europe, but I really never understood why Hetzner is said to be less reliable

Enforcement will be the issue here.

If I order physical goods from a foreign nation it's gonna have to somehow get into my hands, and can be withheld until i pay tariffs

If a irish subsidiary invoices me subscription prices for intangible services, there's no way in the current legal world to enforce a tax on my end

this is the way. Modern CSS brings most of the capabilities to the table that SASS & LESS used to provide, and in part even much more functionality that could never be adequately solved with preprocessors (runtime calc(), light-dark() and layers come to mind)

I'm still a fan of LESS, but quite specifically because it _does not_ try to force another languages syntax into my preprocessed stylesheets, rather keeps everything as css-like as possible. This makes it much easier to transition things to vanilla-only when possible, absolutely dreading "mostly js"-types of SASS frameworks

Hot take: CSS is actually type safe, just doesn't get compiled & fails gracefully ;P

Being from Germany our history classes in school went into great depth about the countries past - and I can't help but feel increasingly scared and left utterly speechless by all the parallels I'm seeing unfolding in the US ...

when technological advancements that actually would allow for BETTER privacy and security, and MORE local-only features are misappropriated for constructing bogus and dishonest justifications to rather erode the least-effort user-minded safeguards that already had been present, it's become plain obvious that the claim to create a product that serves the user has always been a lie. It's about capturing data and influence, and always has been

supposedly idealistically opposed parties doing something that is in the sense of the argument doesn't prove the argument. Walz might very well have been just as wrong