Wrapping every string to a newtype ensure the string can be extended as wished and at least differenciated from normal strings without meaning

::selection ans ::backdrop does not inherit from root. So :root does not guarantee the CSS variable. The html selector does not solve this.

There is currently no global context in CSS, but root is the best workaround currently.

This is going to catch a lot of people off-guard because I, like many others, expect CSS Custom properties defined on :root to just be available everywhere.

The following discussion is there https://github.com/w3c/csswg-drafts/issues/6641

To prevent a custom behavior on Safari Mobile

Another well written guide for Zod.

These four ways are footguns, but they can be easily spotted in the codebase.

getsong make sense and so many useful scripts.

• copy and pasta
• mkcd
• tempe
• trash
• mksh
• serveit starts a static file server
• getsong
• getpod to download something from a podcast player
• getsubs
• wifi off, wifi on and wifi toggle
• url "my_url" parses a URL into its parts.
• markdownquote to add > before every line
• u+ 2025 to get the unicode caracter associated
• snippets to run some snippets
• some REPL launchers for Clojure, Deno, Php, Python and SQLite
• hoy prints the current date in ISO format
• timer
• ocr to extract text from an image
• removeexif to delete EXIF data from images
• emoji fuzzy finder helper https://codeberg.org/EvanHahn/dotfiles/src/commit/843b9ee13d949d346a4a73ccee2a99351aed285b/home/bin/bin/emoji

and more Process management scripts

The heap is a performance killer in Rust. One woraround is to swap to a more efficient memory allocator such as jemalloc.

In Cargo.toml:

[dependencies]
mimalloc = "0.1"

In main.rs:

#[global_allocator]
static GLOBAL: mimalloc::MiMalloc = mimalloc::MiMalloc;

The best performance optimisation is to avoid the heap. There is the heapless create for that. "The only thing to know is that the size of heapless types and collections needs to be known at compile-time."

Lifetime annotations are needed to tell the compiler that we are manipulating some kind of long-lived reference and let it assert that we are not going to screw ourselves

The only downside is that smart pointers, in Rust, are a little bit verbose (but still way less ugly than lifetime annotations). [They add some runtime overhead.]

When to use lifetimes annotations?

When performance really matters or when your code will be used in no_std environments.

I don't know. It seems to be overkill for the use. Instead of words, some functions get a capital letter.

It is currently experimental, but could be amazing because it parse a string of HTML safely and then insert it into the DOM

It uses GSAP

For MacOS only
-webkit-font-smoothing: antialiased;

A great CSS reset

A work to use rust build as PHP extension

It's not available in Firefox yet.

It marks the function as never returning.

In comparison, the unit type () returns at least a value.

The author creates an extension for 3 uuid functions in Rust.

Tradeoffs: big extension size (330KB for simple uuids)

About using SQLite:

As mentioned in an earlier post the two biggest pain points are the "slow" schema changes on 10M+ rows tables locking the entire database for 10+ seconds, and the difficulty to implement automated failover. But it rocks for services that don't need 99.999 % of availability.

assert!() use in const expression are a great way to ensure safe type casting