Structurally speaking, then, a paragraph is a group of related inline elements. In this case, inline words, but it could also include any of the items described as “phrasing content"

<hgroup> issu the tag to use for heading with multiple inline content.

• Google Web Blog https://web.dev/blog?hl=en
• Rachel Andrew https://bsky.app/profile/rachelandrew.bsky.social
• Jen Simmons https://webkit.org/blog/category/css/
• Firefox nighlty news https://blog.nightly.mozilla.org/
• Microsoft Edge's blog https://blogs.windows.com/msedgedev/
• CSS Tricks https://css-tricks.com/
• Smashing CSS https://www.smashingmagazine.com/category/css/
• Frontend Masters https://frontendmasters.com/blog/
• Piccalilli https://piccalil.li/
• CSS Tips https://css-tip.com/
• Frontend Dogma https://frontenddogma.com/
• Web Platform Features Explorer https://web-platform-dx.github.io/web-features-explorer/
• Web Platform Status Dashboard https://webstatus.dev/
• Chrome Platform Status Dashboard https://chromestatus.com/roadmap
• Polypane (provide a lot of developer tools) https://polypane.app/
• Kevin Powell on YouTube https://www.youtube.com/@KevinPowell and https://html-css-tip-of-the-week.netlify.app/
• CSS Working group (via the mailing list or RSS) https://www.w3.org/groups/wg/css/publications/#WD
• Browser Release notes
  • https://developer.chrome.com/release-notes
  • https://developer.apple.com/documentation/safari-release-notes
  • https://www.mozilla.org/en-US/firefox/releases/
• Questions AI
• BCD Watch displays changes to MDN'S browser-compat-data repo
• Can I Use news

The gap is handled differently between these three type of values.

Centered for auto and 1fr, but overflowing for 50%.

Auto overflows for text content.

The behavior is also different for an image: The sturdy 50% column remain in place, and the image overflows it. The auto column grows, but not only to contain the image but a bit wider. The column using fr units grows to contain the image.

Ok but why o_O

Still interesting, but I already have few use cases for container queries. Maybe because I am too dependent of design that uses screen sizes.

The naive Rust implémentation is 10 times faster than the python one.
It remains 6 times faster than the optimized one.

The Python has a collections.Counter class that is approximately as fast as the naive Rust version.

There are 3 error or exception handling: unchecked exceptions (JS), Checked Exceptions (Go) or an integrated type (Result in Rust) that handle one case or the other.

Explicit is always better.
One thing with an integrated type, is the normal case and the other case. That's a great type to handle more than errors: a lookup of a key in a map, opening a file with a name for which there is no file is normal business. Maybe I will find more.

And for quality software, its function must be so blatantly obvious that everybody thinks: wow, this is trivial code, even a monkey could've programmed this.

This is exactly what I think of a great design system color handling.

The heart is the mapping of semantic CSS colors to modifiers, and thethey can be slapped on every components.

There is always color definitions, then semantic colors such as --color-primary-muted, --color-primary-vivid and then css variables used by the components.

A generator is available as snippet on https://codepen.io/cferdinandi/pen/dPojzmN

All I see so far is this will need more computation or battery drain for this.

The library is available at https://github.com/Specy/liquid-glass

• Call Stack
• Primitive Types
• Value Types and Reference Types
• Explicit, Nominal, Structuring and Duck Typing },
• == vs === vs typeof
• Function Scope, Block Scope and Lexical Scope
• Expression vs Statement
• IIFE, Modules and Namespaces
• Message Queue and Event Loop
• setTimeout, setInterval and requestAnimationFrame
• JavaScript Engines
• Bitwise Operators, Type Arrays and Array Buffers
• DOM and Layout Trees
• Factories and Classes
• this, call, apply and bind
• new, Constructor, instanceof and Instances
• Prototype Inheritance and Prototype Chain
• Object.create and Object.assign
• map, reduce, filter
• Pure Functions, Side Effects, State Mutation and Event Propagation
• Closures
• High Order Functions
• Recursion
• Collections and Generators
• Promises
• async/await
• Data Structures
• Expensive Operation and Big O Notation
• Algorithms
• Inheritance, Polymorphism and Code Reuse
• Design Patterns
• Partial Applications, Currying, Compose and Pipe
• Clean Code

A demo of a vue component built with Liquid Glass Design (iOS 26)

It does not work on my Raspberry Pi yet for atuin
I get a:

atuin: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.39' not found (required by atuin)

A hello world binary works fine though.

1. rustup target add armv7-unknown-linux-gnueabihf
2. sudo apt-get install gcc-arm-linux-gnueabihf libgcc-13-dev-armhf-cross
3. In ~/.cargo/config.toml:

   [target.armv7-unknown-linux-gnueabihf]
   linker = "arm-linux-gnueabihf-gcc"

4. cargo build --target=-armv7-unknown-linux-gnueabihf --target-dir=$(pwd)
5. Upload the binary in armv7-unknown-linux-gnueabihf/debug directory to the raspberry pi and run it.

After a first successful installation, only 4. and 5. are required.

A valid minimal HTML page

1. avoid uneccessary default features
2. use specialized lighter crates

The migration schematics automate code changes between angular versions

I have the same idea for a node js backend serving a fancy UI :)

It would be better to split the UI and the server while developing to benefit from hot reloading.

Example: https://git.sr.ht/~pyrossh/rust-embed/tree/master/item/examples/axum-spa/main.rs

• relying on shared mutation
• treat the compiler as something trying to help
• ignoring proper module organization

You have to unlearn a few habits.

1. Writing Rust code like other languages
2. Neglecting the most important 20% of Rust. Trying to learn everything at once: you don't need to learn all at once. Focus on the 20% that gives the 80%.
3. Being a productive procrastinator: watch a video or read a blog post.
4. Thinking you can vibe code Rust like JS...

Hands on practice! The programmer has to internalize the concepts of Rust. Getting a grasp is not enough.