system-ui is a good typography because it falls back on the system font (that is readable). It means 0 bandwidth cost.

Why emails is a mess? Because there are a lot of email service providers that does not follow the standard...

It explains the Writer monad and the Option monad.

This pattern is used for future or promise by the way.

Dav1d is a new AV1 cross-platform decoder, open-source, and focused on speed, size and correctness.

It uses software instead of hardware to be compatible.

A great way to use CSS properties is to make "private" properties for a class and then create variants based on other CSS class modifiers that sets these variables.

Basic advices, so nothing new at the end.

1. Use programming standards
2. Use programming design principles
3. Use patterns
4. Use proper names
5. Use tests
6. Manage time, as time estimation often fails. Double or triple the estimated time
7. Use appropriate speed

Vous avez demandé un effet Streisand?

Let's see in some month how the Foundry VTT integration went 😉

Elle est drôle cette publicité quand même, car les fruits de qualité deviennent rares.

La même structure: un sommaire, différentes rubriques et une info-box avec des chiffres et des images.

Le contenu provient de sources secondaires, qui sont consultables dans sa rubrique dédié.

La qualité de l'article reflète celle de ses sources.

Chaque article possède aussi sa page de discussion.

Les articles ont deux types de liens: les bleus indiquant un lien vers un autre article et les rouges indiquant qu'un article n'existe pas encore.

These robots become so much more performant. They can find the exit of the maze in no time.

1. cargo build --release

2. set strip = true to profile.release in cargo.toml

3. set opt-level = "s" to optimize for size instead of runtime speed

4. set lto = true to enable link-time optimization

5. set codegen-units = 1 to maximize size reduction but it results in slow builds

6. use cargo bloat to understand which dependencies are taking up space

A hacky way to store data as video. The proof of concept uses youtube.

a new #project #idea is to build the whole thing, but not only for youtube, but for any possible API endpoint :D

Here is separation of the responsibility of such a program:

• the image processing layer takes the file and converts it into an image or video
• the compression layer reduces the size of the data as much as possible
• the encryption layer guarantees the confidentiality of the data until the algorithm is broken, since the data is shared with a third party anyway. It can intervene
• the network layer allows data to be uploaded and downloaded to different providers (why limit it to youtube?)
• the data layer: it is responsible for storing information about the videos/images (video metadata: at provider X, accessible from such and such a URL, last modification date, etc.). It inserts metadata into the files through the image processing layer in order to decode them correctly (type of compression, etc.).
• the application layer: it allows to use everything with a UI/CLI. In short, an interface for the user.

Kafka has a good throughput with sequential Writes and Reads.

Kafka can move a lot of data because of the zero copy read principle:
Before:

1. Disc to OS buffer
2. Write the content of the OS buffer to the RAM
3. Copy the data to the application Buffer
4. Copy the data back to the socket buffer
5. Copy the data from the socket to the Network Interface Chip buffer and send it

With zero-copy read principle:

1. Read from the disc and load it into the OS Buffer
2. Directly copy to the NIC Buffer (the CPU is not involved)

Transition a CSS grid row from 0 to 1fr to get an accordion working :D
An Advantage is the text is already rendered for screen readers.

Afin de favoriser la sobriété:

1. Répondre à nos besoins fondamentaux
   • l'autonomie
   • la compétence
   • l'appartenance sociale
2. Développer les nudges (coups de pouce)

with material: https://web.stanford.edu/class/cs253/

Broad videos on the subject.