Modern technology is abusive, but FOSS is certainly no silver bullet. [...] People have been trained to be abused by software and by hardware, to ignore their needs, to accept any change as inevitable

There are things avoidable: Internet-connected beds, AI browsers, unrepairable devices, requiring smartphones, NFTs, The Metaverse, update changes, ads, Meta-owned, Apple Vision pro, Copilot PCs

nothing sold by powerful grifters is "the future" no matter how much they wish that were true.

The driving factor is what constitutes a desirable future and which actions get us closer or further from that.

TL;DR; use a negative GRAD value

GRAD stands for "grade", and it's a variable font axis that allows us to adjust the perceived weight of a font without changing the glyph size.

GRAD stands for "grade", and it's a variable font axis that allows us to adjust the perceived weight of a font without changing the glyph size.

body {
  --GRAD: 0;
  font-variation-settings: "GRAD" var(--GRAD);
}

@media (prefers-contrast: more) { body { --GRAD: 700 } }
@media (prefers-contrast: less) { body { --GRAD: -50 } }

@media (prefers-color-scheme: dark)                              { body { --GRAD: -50 } }
@media (prefers-color-scheme: dark) and (prefers-contrast: more) { body { --GRAD: 150 } }
@media (prefers-color-scheme: dark) and (prefers-contrast: less) { body { --GRAD: -150 } }

Baseline in action is a collection of articles and demos showing you some of what's possible with features that are now Baseline.

The Firefox fox cutting its branch thanks to Mozilla and with the help of a chainsaw brought by the AI bird.

Enter the “rule of three” — the actually actionable, pragmatic principle that elegantly combines how you should be thinking about YAGNI, DRY and premature optimisation. The rule of three states that you should only refactor (or optimise) code once you’ve written the same code three times.

At the first time of writing the code, code that’s fast and optimized is great, but if it’s hard to read and reason about, it will slow us down in the long run. Here, I like to apply another principle: “Make it work, make it right, make it fast”

It works while iteration though. In some cases, you want to leverage engineering: make it right the first pass. It happens for API validation for example, or logging correctly in case of failure.

Gall's law: a complex system that works is invariably found to have evolved from a simple system that worked

Functions should be as idempotent as possible: all it really means is that a function always does the same thing when given the same arguments. Note idempotent functions are different from pure functions. pure functions are guaranteed to not have side effects.

Then there is this single responsibility principle. It avoid changes on the entire codebase. "A small trick to check for single responsibility is to describe what a function/module/class does in a single sentence. If you find yourself saying “and”, then it probably has multiple responsibilities and should be split up."

One efficient implementation is to operate on one level of abstraction. See a function implemented in three functions. I would still be critic on this one, because the tradeoff is not worth it from time to time.

These code principles are similar indeed. "All good code is alike; each bad code is bad in its own way."

Abstergo Industries for Assessin's Creed, ACME in Looney Toons,

More on Infos

Color palettes made from hydrant :)

Useful CSS utilities, elements, complete UI blocks and templates.

Convert solar weather into audio

Generic software design: It’s “designing to the problem”: the kind of advice you give when you have a reasonable understanding of the domain, but very little knowledge of the existing codebase. [...] When you’re doing real work, concrete factors dominate generic factors.

In large codebases:

• consistency is more important than "good design". Read Mistakes engineers make in large established codebases.
• Real codebases are typically full of complex, hard-to-predict consequences.
• Large shared codebases never reflect a single design, but are always in some intermediate state between different software designs. How the codebase will hang together after an individual change is thus way more important than the "north star"

The majority of software engineering work is done on systems that cannot be safely rewritten.

1. Generic software design advice is useful for building brand-new project
2. Generic software design advice is useful for tie-breaking concrete design decisions.
3. Generic software design principles can also guide company-wide architectural decisions.

La hausse de 73% du prix des Ouigo provient de la hausse du prix du kilomètre payé par passager de train Ouigo, avec 3.7 à 6.2 centimes (68%); l'offre a décrue de 1.6% par manque de compsation de l'offre TGV Inoui.

Un bilan d’autant plus déconcertant que, dans le même temps, le nombre de passagers de la grande vitesse en France sur les trains Inoui et Ouigo a augmenté de 13 % entre 2017 et 2023.

Lol links are broken because the response body is too small (6KB or 3KB)

So please can Django get it sorted and add some bloat to their home page, and to their framework, and can someone also send me tips on bloating my own sites, so that my profile links can be counted as real websites? Thanks!

Recherche sur YggTorrent

Wayyy to advanced for me currently

Ils font des jeux cool, comme https://popthewall.fr/fr

What Americans die from and the causes of death the US media reports on.

Causes of death in the US in 2023 compared to the media coverage of these causes of death in 2023 in The New York Times, The Washington Post and Fox News.

Au lieu de laisser faire le marché, il y a une aide jusqu'à 600€. Ce qui m'impressionne, c'est le nombre d'aide existante.
Je dis cela en ayant bien bénéficié du Dossier Social Étudiant (DSE) sans APL, puis avec mes deux dernières années d'études.
Je trouve cette aide si niche cependant!