Daily Shaarli

All links of one day in a single page.

March 5, 2024

CSS Loaders: A collection of more than 600 loading animations
If They Told Me We Were Poor, I Would’ve Taken Out More Student Loans - McSweeney’s Internet Tendency

The author avoided debt, but was it worth it?

Childfree.txt | the library of alexandra
Postgres documentation explained

Everything is in it, but has to be found.

There are dedicated sections for SQL or DBA for example.

embassy-rs/embassy: Modern embedded framework, using Rust and async.

A framework for embedded systems

a11y is web accessibility – Eric Bailey
How hard upgrading a Rust JWT library could be? - Orhun's Blog

A great feedback

Internet gardening | James' Coffee Blog
Understanding String and &str in Rust - LogRocket Blog

Now I get it.

Nick F in Elk: "@pixelambacht I think you're right that offe..." | Elk

What's your favorite solution for not-quite-component components?

With those I mean components that are more boilerplates to be expanded upon, instead of actual ready-to-go components you just tweak a few details of. Components that would grow too complex if you'd need to account for all possible interaction and design versions through props or CSS custom properties.

I think often the alternative is composability: ie. what's the minimum functionality that the cookie consent component could have? Could it be a wrapper that provides cookie-setting functionality to whatever UI component it wraps? Could it be a little JS module different components could import to reuse?