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.

A playlist of rust video about rust.

🎯

Tout abus d'@YLeBolloch peut nuire gravement à la santé d'une machine à propagande, même bien huilée.

On remarque les journalistes qui veulent tous le temps pousser à la phrase de trop au lieu d'avoir une clarté dans le discors. L'interviewé impose son rythme, c'est remarquable.

If you have some notes, you can have a melody

La prouesse technique d'avoir du Wifi à bord des TGV, et pourquoi c'est si compliqué !

Good points! I have use cases where a frontend database approach will work perfectly!

Numbers:
const formatter = Intl.NumberFormat(LOCALE, { notation: 'compact' })

Currency:

Intl.NumberFormat(LOCALE, {
  notation: 'compact',
  style: 'currency',
  currency: 'ZWD'
})

• Extraction: make the nested code a function or its own piece of logic.
• Inversion: use guards to remove nested code. These guards will stop the function before the end of the function body. They act as gates.

La vidéo appuyé par Elon Musk n'a donc pas été tournée proche d'un aéroport, comme il le prétend

TL;DR $attrs defines every attribute that is not listed in the props.

Use cases:

• apply $attrs on a specific node
• tell Vue to apply $attrs on a node of a multiple root-node components
• using prop validations (in dev only for example)

Ils sont magnifiques et c'est si beau

Ducks and drum kit

Macron disant que c'est hypocrite de décaler l'âge de la retrait. C'était il y a peu années.

computedEager utility has optimizations over computed in some cases.

when you have a simple operation, with a rarely changing return value – often a boolean.

Stick to computed

when you have a complex calculation going on, which can actually profit from caching and lazy evaluation and should only be (re-)calculated if really necessary.

See https://vueuse.org/shared/computedeager/

display: contents is underrated: it removes the box layout of the element!

grid-row or grid-column only works on explicit layout: workaround at 18:55

TL;DR;
apply every hover effect on devices that can not support the hover effect (smartphones, ...).

Use the @media (hover: hover) media query to target devices that have the :hover effect available, or @media (hover: none).