I would call it an esoteric programming language. The syntax is funny thought.

Josh Comeau writes excellent blog posts about programming topic. This one is also great!

About the level 3 and level 4 of CSS grid

Awesome slides

Implementations of UUIDv7 in Python, Javascript, SQL (+PostgreSQL), Shell, Java, C#, C++, C, PHP, Go, Rust, Kotlin, Ruby, Lua, Dart, Swift, R, Elixir and Zig.

It is funny to get these rights.

1. Add display in the keyframes to set display none at the end of the keyframe
2. transition-behavior: allow-discrete (but it does only work on chromium at the moment https://caniuse.com/?search=allow-discrete)

1. There are many cases.
2. It is dynamic.
3. There is this handling of extra seconds... leap seconds: google hacks it by adding an extra ms to each second or minute to avoid it.

but limited to the amalgamation

How to build a basic modern webring. An example of Web components.

How to implement fluid typography and layout with a simple example. That's great :)

Media queries can be nested in css classes and that's awesome!

OTP fields (one character per field) from a single input? Yes it seems great because it has all features builtin: copy/paste, typing in the previous or next fields...

A language that compiles to bash

[Following https://shaarli.lyokolux.space/shaare/pkpvPQ]
Ok ok another use case for container queries:

Notice that the horizontal style became too condensed, this is because we used a media query. When using a media query, the browser doesn’t care about what will happen to the components if the available space isn’t enough. [...] As you’ve seen using a media query to change the card style isn’t logical in this case. The number of cards can increase or decrease and that will affect the card’s content.

new CSS features limitations are our brain:

• feature fatigue
• browser support (well is 90% for the container queries enough?)
• invisible improvements: a big chunk of the new features today are “invisible” though - they focus more on code composition and architecture.
• I don't know where I would even use the feature
• break the habit
• keep one step at a time
• find inspiration

The part on re-thinking established patterns is awesome to understand how to use the cascade, @layer and @container ! https://mxb.dev/blog/old-dogs-new-css-tricks/#h-re-thinking-established-patterns

Why we should avoid it? Because it can go wrong in so many way. The post describes different cases.