TL;DR

To be more specific, there’s actually two things to screen for:

1. they give a shit about X, and
2. they give a shit about their work in general.

Comment reconnaître un paquet perdu et quels sont les protocoles pour éviter, détecter et réparer ce genre de problème ?

Example of a scientist turning into Rust.
Some arguments in favor of Rust:

• Microsoft use it too to rewrite parts of Windows because 70% of their bug fixes each year are related to memory safety. Something that can not happen in Rust.
• the engine Servo of Firefox is written in Rust
• It is the fastest growing language according to Github
• the compiler produce high informative error messages
• a well complete and high-quality ecosystem: tooling (cargo, clippy, , community, IDE integration, Rust playground

BUT the learning curve is steep.

Idea to learn Rust : RIIR scientific algorithm :stuck_out_tongue_closed_eyes:

Apple 11 Big Sur is not privacy compliant. The company reacted and has published some patches for it.
Anyway Apple can still block any program of their choice.

Construire un makefile pas à pas.

hello-world: init
    @ echo "Hello, world"

Un Makefile est une collection de règles, chacune étant composée d'une cible, de pré-requis (ou pas) et d'une recette. Dans notre exemple précédent, hello-world est la cible et @ echo "Hello, world" est la recette de la règle. Elle spécifie un pré-requis: init .