The "C" (Cascade) in CSS doesn't suck, the education about it sucks.
People don't know how it works, then things go wrong so they learn to work around it.
That's what led to things like div + class soup that you get with the BEM naming convention or Tailwind.
The cascade is actually awesome, super powerful and if you know how to use it, it can greatly simplify your code.
Education is the problem and the solution.
---
To anyone outside the CSS space, this is the closest analogy I can find:
In the American education system, there was a recent-ish change where children are "taught" to read using a method of just learning the shape of every word (e.g. "thermally" has a th at the start and ly at the end, so it must be the word "thermally", despite other similar looking words like thematically).
The method was disproven but the American education system still uses it.
Now illiteracy rates are climbing where almost 1/4 Americans (USA) can't read.
It's basically the same thing with CSS, where developers don't know what the code they're reading/writing is actually going to do.
It has nothing to do with education, software development is not learnt in a centralized way so you could hardly claim anything based on that.
Cascading simply fails to scale/work with web applications, especially when multiple people work in parallel.
HTML both describes content AND layout, so you simply can't separate the two. This was a nice dream when the internet was "markdown encoded in html", but the moment you write a nested <div> for layout purposes you lost. So HTML has to be written together with CSS, so we get no separation. Now what is it that you could meaningfully cascade? (If anything, variables are all that we needed)
Add to it that people are using third-party components as well, and now many "widgets" starts by resetting outside styling rules.
I don't think anyone in this thread is arguing that inheritance or specificity is hard to understand.
My issue with cascading style sheets is mainly that namespace pollution (as every selector is defined in the same global namespace) means that short selectors (.separator, .highlight, .button) are likely to collide with completely unrelated parts of the application. BEM and tailwind are popular because they localize styles to specific components, preventing namespace issues. Today, most web frameworks deal with components, so it makes a lot of sense to localize the styles to the components. Scoped css in vue/svelte allows you to write short selectors, and have them only apply to the component they are written in, without needing to prefix them with a component name.
Reading word shapes comes from a place of good, studied intent. Reading word shapes is how people who read quickly read. It is in many ways an advanced way of reading. Trying to jump to it was a hope that you could shortcut some of the literacy curve. Unfortunately, trying and sometimes failing to read word shapes is also how some neurodivergent brains work naturally (the family of dyslexias as the big complex elephant in the room). If your brain jumps directly to word shape, and somewhat often gets it wrong, being forced to slow down, break words apart and start from smaller basic building blocks can be helpful.
It's a reminder that different people learn at different paces.
I think overall the additional details expand and perhaps better the metaphor: a lot of people want to jump directly to the advanced CSS stuff and skip the fundamentals. For some people that works and may be a shortcut. Other people need to spend more time breaking their teeth on the fundamentals, getting them wrong, learning from their mistakes, and getting rock solid on the slower building blocks before trying to do anything advanced.
Instead of assuming that everyone who has a different preference than you is ignorant, it might be helpful to look at the problems that each technology solves and the requirements they fulfill.
The cascade is a huge issue for teams need to be able to safely modify one area of a site without accidentally impacting others. Tailwind solves organizational problems by colocating the styles with the elements - allowing changes to be surgical, declarative, and predictable. Editing and removing styles is as easy as modifying the content of the page.
Yes, the cascade is super powerful, but it needs to be contained somewhat to scale to many developers and large codebases.
> 1/4 Americans (USA) can't read
Also even though your analogy has nothing to do with CSS, I have to point out that this absolutely isn't true (which in the context of your argument about education is pretty ironic)
> That's what led to things like div + class soup that you get with the BEM naming convention or Tailwind.
You could try and think why people end up with BEM or Tailwind. And the answer isn't "because people are not educated about cascade". Both BEM and Tailwind came form people who are very much aware of the cascade.
The problem is that cascade is very much a hindrance in quite a few cases. Especially when you deal with components and design systems.
> To anyone outside the CSS space, this is the closest analogy I can find
All analogies are bullshit.
The truth is that CSS is designed for documents, and for a few decades people have been trying to use it to design/build components: https://x.com/simonswiss/status/1664736786671869952 Cascade is good for the former, and is death for the latter.
And browser vendors have been surprisingly stubborn when it comes to making any improvements to the DX in this area. That's why instead of locally scoped CSS, CSS nesting, CSS mixins (and a bunch of other improvements from SASS and various JS Frameworks) we first got 15 000 JS-only specs around web components, of which 14 999 can be covered by improvements to CSS.
> where developers don't know what the code they're reading/writing is actually going to do.
Lol. Tailwind has made people more aware of what CSS does, with better documentation, than decades of bullshit articles and millions of words of existing docs.
I call it cargo cult developing. People develop bags of spells and tricks that they attempt to apply to a situation to solve a problem. Usually they can arrive at a solution by trying a number of these incantations, but not always. And never actually ask them what the incantation does
It's not just css either. At a job I've worked, we had a VPN client that would get into a weird state, where it needed to be killed to restart. An incantation that made use of ps, grep, awk, and xargs was provided, instead of just using pkill
The Aztecs in particular were kind of uniquely terrible, both for their own citizens and for every oppressed pseudo-vassal-state around them. It's one of those weird accidents of history that Spanish colonizers were able to step into the power vacuum after the fall of Tenochtitlan and have at least some people genuinely think 'yes, this is better than the last boss'.
Cortez came to Tenochtitlan as an 'ambassador' at the head of an army of 200,000 angry neighbors of the Aztecs, who had realized pretty fast that even a few of these 'gun' things would be really useful for cracking the city's structural resistance to sieges.
Would be interesting how you'd steal it, it's on the moment you have it, emitting its location... maybe you put a blindfold over the camera/walk into a faraday cage then power it down/wipe the flash.
From the beginning they know who you are
Would be interesting people start hijacking humanoid robots, little microwave EMP device (not sure if that would work) and then grab it/reprogram it.
The problem with US cities is that they're not dense enough. Most of the US has spent the past half-centry actively making new high-density construction illegal or incredibly expensive, so everything is operating within the bounds of 1970s-80s construction being reused over and over again because it was grandfathered in.
People being forced by economic forces to move into uncomfortable and unaffordable dense cities. This in turn creates disadvantaged underclass with no hopes for a better future. And even European social safety nets can only do so much.
While just hours away from dense cities, the apartments are often literally free. With copious space and easy access to basic services.
This results in rising crime. The downward trend that started in 90-s had been reversed. And the crimes of despair, mainly drug-related crimes, are rising faster than violent crimes.
That ad gave me a visceral shudder of revulsion, not so much for the specific functionality on display as for the timing, which absolutely could not have been accidental. They might as well have just put 'and we're working on automatic alerts for ICE!' in the ad.
"Administrative subpoenas" have always been bullshit that mostly rely on there being no penalty for companies that hand over user information to anyone with a badge and then justify it with a five-hundred-page TOS document.
Google, among most other tech companies, deny portions of administrative warrants. Here's a story about someone who was stressed out about their notification by Google (spoiler, Google decided to deny the government's request)
edit: It appears that this outcome is an outlier and most admin warrants are honored. It is unfortunate to see the Washington Post decline in reliability like this.
Google does not provide those products (not in the US, as far as I am aware), but they are a money transmitter in the same vein as Square/Block, Stripe, and Venmo [0]. They won't be directly subject to the Bank Secrecy Act, but they partner with the major payment networks (who have their own rules and their own partner programs with banks) as part of Google Pay and customer payment profiles.
But I don't think this matters much for this case, as DHS is not investigating financial crimes. This is about what discretion Google has to comply with administrative warrants, which is not settled law and isn't clearly spelled out in their own policy.
I just looked it up, and money transmitters are included in the Banking Secrecy Act as "Money Services Businesses". So yes, they have KYC obligations in the sense that they know where you are moving your money and are obligated to tell investigators.
Unfortunately, KYC is used for much more than just financial crimes, and the precedent to comply is much more firmly established.
There is a case to be made that administrative subpoenas can be good. They save taxpayers money, they speed up investigations, and they free up the court for more important matters.
As with all things though, these agencies should not be self-regulated without civilian and judicial oversight.
I'm a little sad that they talk about counterfactuals in the simulations, but then don't show any examples of even a single sharknado or giant loop-de-loop.
Also manages to sustain itself on it's own weird brand of whales, a handful of disgruntled users with enough money to just keep buying accounts using random characters as a username just to get immediately banned after their first post. Some taking a dump in the middle of your living room isn't so bad if they are paying your rent and you can just kick them back out.
Complicated-enough LLMs also are aboslutely doing a lot more than "just trying to predict the next word", as Anthropic's papers investigating the internals of trained models show - there's a lot more decision-making going on than that.
> Complicated-enough LLMs also are aboslutely doing a lot more than "just trying to predict the next word", as Anthropic's papers investigating the internals of trained models show - there's a lot more decision-making going on than that.
Are there newer changes that are actually doing prediction of tokens out of order or such, or are this a case of immense internal model state tracking but still using it to drive the prediction of a next token, one at a time?
(Wrapped in a variety of tooling/prompts/meta-prompts to further shape what sorts of paragraphs are produced compared to ye olden days of the gpt3 chat completion api.)
reply