The tool is optimized for decompression.

LZ4 is symmetric: it compresses about as fast as it decompresses. That suits logs and swap, but not data that is shipped. A firmware image is compressed once on a build server and decompressed on every device that installs it, so time saved during compression helps nobody.

ZXC moves the work to the encoder. Match selection, optimal parsing and statistics tuning are done once, and the bitstream is laid out for the pipelines and branch predictors of modern processors. The decoder stays short, has few branches, and uses SIMD where it is available.

Additionally the "fix" fixes more than 40 separate issues in a single mega-commit touching 68 files which like. This is really beyond "you are trusting the slop machine too much". This is "the moment the slop machine got in your hands, a switch flipped in your head and you were like 'I never have to follow any engineering standards, any at all, ever again'". To repeat once again: "AI" is not a technology, it is a permission structure.

The good engineering practices are ignored by AI and the people seems to not care about it.

I find it completely overkill but maybe I am missing something. The use case for the posts is relevant, because it allows recursion (replies of replies). I don't see a potential widespread usage though.

The format is better than PNG and JPEG. As the browsers Edge, Firefox, and Safari supported the format respectively in 2018, in 2019 and in 2020. There is no reason to not use it.

Using icons as design tokens can be a great idea to switch icon names.

This site lets you rank the Interop 2027 proposals you care about, giving us (the Firefox team) data we can use when reviewing which proposals should be taken on.

Imaginez alors le coût du nucléaire avec la corruption en moins. Ce serait encore plus compétitif.

there is one place that gets less attention and yet has a colossal impact: building libraries for cross-platform applications.

Why would anybody want to go the "hard way" compiling Rust for multiple platforms?

1. Write once, run everywhere
2. Correctness
3. Security provided by Rust itself

The projects use two architecture:

• Either a cross-platform rust core with platform specific UI, state management and other dependencies
• Or platform specific user interface, state management and business logic that are bound together by many rust libraries

Des réflexions sur la stabilité de quelque chose développé par IA. L'exemple est celui de ArtCraft: https://shaarli.lyokolux.space/shaare/aaHWxg)

Un calendrier de prévision des jours Tempo (blanc, rouge, et bleu).

Le billet de blog décrit le fonctionnement des prévisions du calendrier

Le problème

Avec l’option Tempo, le prix de l’électricité dépend de la couleur du jour (bleu, blanc ou rouge), que RTE annonce la veille. Pour anticiper au-delà, il faut prévoir la tension sur le réseau, qui dépend surtout de la consommation, donc de la météo.
Les données ouvertes utilisées

• les données éCO2mix de RTE (consommation, production) ;
• les prévisions de consommation publiées par RTE ;
• les prévisions météo d’Open-Meteo. Les règles du dispositif (nombre de jours rouges et blancs par saison, jours où le rouge est exclu) ajoutent des contraintes que l’algorithme respecte.

The term "open" is misused by many companies or project.

The clones are not feature complete.

The project is active again. It's an alternative to Nextcloud: Etherpad to edit document, file storage with Davros, task and project management with Wekan and chat with Rocket.chat.
Sandstorm supports many other apps. It should be as easy as . The project sandboxes every document created in one of the app.

It's main difference is usability and designed for humans (as they describe it).