How should a website change with the seasons? Could a website be different as time passes? Could a website adapt to night time so that readers have an easier experience perusing information?

• Different category leads to different themes
• Emojis change with the seasons
• How can I make my website evoke feelings associated with a season?

94 % de sites non accessibles

Raisons? Stéphane Deschamps (via https://piaille.fr/@notabene/113327840519217866) dénonce que l'accessibilité soit hautement technique; alors que la technique de base ne l'est déjà pas.

Cependant le top 3 des problèmes constatés concernent des contrastes insuffisant, des intitulés de liens et noms accessible d'images manquants. Ces erreurs sont techniquement facilement corrigeable!

1. Avoid alliteration. Always.
2. Prepositions are not words to end sentences with.
3. Avoid clichés like the plague. (They're old hat.)
4. Eschew ampersands & abbreviations, etc.
5. One should never generalize.
6. Comparisons are as bad as clichés.
7. Be more or less specific.
8. Sentence fragments? Eliminate.
9. Exaggeration is a billion times worse than understatement.
10. Parenthetical remarks (however relevant) are unnecessary.
11. Who needs rhetorical questions?

A minimal table editor :)

Martinique Vie chère
Gladys Roger du RPPAC
La leçon ! (et la ligne de chemises cravate en face)
via Caisses de grève

Display train/bus stops on a Kindle 😄

The author goes really in-depth 👍

RSS is a way to avoid enshittification

1.

In HTML5,

content “must be quoted from another source”

Heydon rightly makes the distinction between block quotes, which (supposedly) quote another source, and pull-quotes, which highlight excerpts from the article you’re reading.

2. No <cite> in <blockquote>

Heydon suggests using a <figure> and <figcaption> to invoke this grouping, which seems the most sensible option.

The <blockquote> cite attribute is generally useless since it’s invisible and most screen readers also ignore it

3. For inline (or “text-level”) quotations, there is <q> instead.

4. HTML is hard

But the developers have no consequences on that.

Les quatres manières de lire:

• indexation
• skimming
• analyse
• sémiologique

Concernant le code:

• Ne pas attribuer à la malveillance ce que la bêtise peut expliquer ;
• Ne pas attribuer à la stupidité ce qui est expliqué par le manque d'attention ;
• Ne pas attribuer au manque d'attention ce qui peut être expliqué par un contexte non dit ;
• Ne pas attribuer à un contexte non dit ce que le système autour de la personne peut expliquer ;

Similar to https://shaarli.lyokolux.space/shaare/xwiTHQ

Bit operators are the fastest, then static array, then dynamic arrays.

Objects are heavy in comparison.

PRAGMA journal_mode = WAL;
PRAGMA synchronous = NORMAL;
PRAGMA busy_timeout = 5000;
PRAGMA cache_size = -20000;
PRAGMA foreign_keys = ON;
PRAGMA auto_vacuum = INCREMENTAL;
PRAGMA temp_store = MEMORY;
PRAGMA mmap_size = 2147483648;
PRAGMA page_size = 8192;

Mais certains experts en sécurité ont exprimé récemment de fortes inquiétudes quant au fait que le ME [Management Engine des processeurs] pourrait cacher une porte dérobée, car il fonctionne indépendamment du système d’exploitation et a accès à la mémoire, au réseau et au matériel.

Korben revient sur l'historique de securité de Intel, avec plusieurs failles démontrées...

En plus des problèmes de sécurité, la CSAC critique la fiabilité des produits Intel et son attitude face aux plaintes des utilisateurs.

À suivre car la CSAC n'a encore publié aucune preuve, et qu'Intel n'a pas encore répondu.

TL;DR use fluid typography and now uses fluid sizes :)

All the most-impactful projects in the data engineering world are now written in Rust. More than the classics fast, safe and high-level language and C interop. The author provides highlight on:

The TL;DR is that most organizations don't even have that much [big] data, a few hundreds GB to single-digit TB for the 98%

One server is enough. [The industry] is instead focusing on simpler solutions.

Rust provides reusability! "For example, Arroyo, Ballista, delta-rs, InfluxDB and many more all use the Apache DataFusion query engine."

This is a massive piece of engineering that they don't have to re-invent themselves and can instead benefit from a software package built and continuously improved by many organizations that have a vested and shared interest in making it great.

A incredible performance optimisation for WebAssembly in Firefox!

(via https://korben.info/firefox-accelere-execution-webassembly-75-fois.html)

For example, the compilation time of the WebAssembly module used by Adobe Photoshop online was reduced from 4 minutes to just 14 seconds. Similarly, a test module for the JetStream 2 benchmark saw its compilation time reduced from 2.8 seconds to 0.2 seconds.

OpenAI promises return on investment in 2029...

A company "that has no path to profitability,"

As I've said before, I believe there's also a subprime AI crisis brewing because OpenAI's API services — which lets people integrate its various models into external products — is currently priced at a loss, and increasing prices will likely make this product unsustainable for many businesses currently relying on these discounted rates.

As I've said before, OpenAI is unprofitable, unsustainable and untenable in its current form.

The author explains it in few points. See their breakdown on the revenue estimates.

POV

And, if we're honest, it still isn't obvious why anyone should use ChatGPT in the first place, other than the fact everybody is talking about it.

This heavily-suggests that generative AI, as a technology, doesn’t necessarily have a product-market fit.

SQLite simplifies the overall architecture. That's why you would pick it with Rails.

This is because Rails, with 2 decades of battle-tested solutions extracted from production applications, provides unparalleled conceptual compression, while SQLite, with its single file database and embedded executable, provides truly unique operational compression.