It made them a subscription model:
▫️ Lust → Tinder
▫️ Gluttony → Uber Eats
▫️ Greed → Amazon
▫️ Sloth → Netflix
▫️ Wrath → X
▫️ Envy → Instagram
▫️ Pride → LinkedIn

The ui design comes from Solo Leveling. Funny

How to handle CSS color with the new CSS color functions instead of SASS?

The best seems to be color().
There is also rgba(), hsla() and color-mix()

• color()

It’s evident that there is a growing array of new CSS capabilities that can handle many tasks we previously relied on Sass for.

Yes indeed. Also I agree: it's a per project decision to make.

Un registre de traitement des données. Par exemple ici pour la signature et collecte des mandats

I like the menu at the bottom, and the simple yet clear introduction.

A website full of design resources.

It’s a pretty broad range of topics but always through a common lens of design and creative thinking.
All resources and links are shared purely because I think they are cool, interesting or helpful.

It makes HTML accessible

En périodes cani­cu­laires, la nuit ne rafraîchit pas, ou pas assez. On gagne donc de la chaleur chaque jour, sans rien pouvoir y faire.

La climatisation va devenir une norme.

Bloom filters are excellent data structures to check if an element can be in a set.

Examples can be found on Wikipedia

I also tried a Client Side Reader and got into the same issue: CORS blocks requests for other websites.

I now build my personalized feed as a part of this blog’s build process

The author got it working at https://matklad.github.io/blogroll.html; and mark the most important one on https://matklad.github.io/links.html

It is kept simple.

Having a public blogroll also means the followed blogs get page rank back!

Instead of an OPML file, the author use a list of links. https://github.com/matklad/matklad.github.io/blob/ea7bc5161d7b2bc12a7a004408caaefb509b9f92/content/blogroll.txt

The code used is a snippet.

A typical medium-sized Rust service packaged this way weights between 20 and 40 MB before compression and between 8 and 15 MB after compression. Not bad!

A way to integrate a search in a static project.

How to build a mansory layout that works. 66 lines of JS.

C’est la part des richesses appor­tée à chacun qu’il faut sauve­gar­der, pas le travail.

Le problème n’est pas que l’au­to­ma­ti­sa­tion retire du travail, ni même qu’on manque de richesses. Le problème c’est que l’au­to­ma­ti­sa­tion du travail modi­fie la répar­ti­tion des richesses (vers une plus grande concen­tra­tion).

Le problème n’est pas que l’au­to­ma­ti­sa­tion retire du travail, ni même qu’on manque de richesses. Le problème c’est que l’au­to­ma­ti­sa­tion du travail modi­fie la répar­ti­tion des richesses (vers une plus grande concen­tra­tion).

La société actuelle tend rester elle-même au lieu de s'adapter à cette automatisation des tâches qui libère du travail.