Different loading hints:

• async resource is loaded when the browser can
• defer resource is loaded when the DOM is parsed (less priority than async)
• rel=preload load the resource before the parsing and everything else
• fetchpriority with value high, low and auto. They are hints.
• rel=preconnect indicates that a connexion has to be established ASAP.
• rel=dns-prefetch resolves the domain name without fetching the resource.
• loading attribute determine when an image is loaded depending of its value:
  • eager: the image is loaded immediately
  • lazy: the loading is delayed until the user scroll to it.

A curated list of algorithms sorted in two categories: Beginner and Advanced

Specific questions on the JS language

A crash course with further resources

JavaScript Repository of TheAlgorithms, which implements various algorithms and data structures in JavaScript.

For education only

Ils sont magnifiques et c'est si beau

La solution, la seule, permettant de traiter le mal plutôt que ses symptômes est pourtant connue. Elle consiste, je vous en ai déjà parlé, à créer un index indépendant du web. C'est à dire à réinstaller durablement dans l'espace public une "ressource", un "bien commun" dont l'exploitation par des acteurs privés à fini par installer des usages essentiellement privatifs, là où pourtant l'ensemble des caractéristiques techniques (son architecture) et des usages (ces 'contenus' qui 'font' le web) de ce "bien" relèvent, par nature, de la sphère publique commune.

Aussi, développé dans l'article:

Il n'y a pas de barrière technique ou juridique au déploiement de cet index indépendant.

Avec de bons débuts d'aggrégation de données: Hathi Trust pour les livres, Internet Archive pour les sites webs.
Les technologies open-source sont aussi présentes, de même que la recherche au niveau européen. Les services quotidiens ont tous ou presque un équivalent open-source.

A project to use a Result type. This particular type contains a result or an error.

The whole point of #100DaysToOffload is to challenge you to publish 100 posts on your personal blog in a year.

1. OpenStreetMap
2. Wikipedia
3. Observation.org
4. Wardriving with the tool Wigle
5. folding@home
6. Blog posts

Tiens tiens

You got some points

Madeline a eu le bon réflexe de nous contacter pour demander l’autorisation de garder une licorne chez elle. Nous voulions absolument lui répondre et encourager ce type de comportements

Straight white male privilege (from the far right) is this: To be able to stand 50 people in front of a school in military uniform with automatic weapons in hand and not be bothered by the police.

(from https://sebsauvage.net/links)

1. Due to color vision deficiencies, it’s a good idea to always complement error messages with an icon
   • Additionally, it might be a good idea to guide users towards specific issues of the form with an error summary.
2. Never cover user inputs
   • First of all, we avoid tooltips that open on hover and display the tooltip only once tapped or clicked.
3. Error message position:
   • they should be placed above input for various reasons, but it costs layout shifts. In doubt, a collapsible accordion instead might be a better idea there.
   • they should be placed inline in tables. One of the simpler patterns is to display the error message in the same row where the content lives.
4. Avoid toast error messages
5. Establish stop-words for your error messages: they should never be used. See Error messages
6. Provide Examples Of Correct Input or guide the user to the expected input. For example, "IBAN starts with the country code. For example, DE or AT.
7. Display Error Summary on the top
   • Additionally, you might want to adjust the favicon and the title of the document if errors do appear,

Using the tool gitfive.

Legit