window.navigator.languages[0] gets the first language (locale) preferred by the browser; works well with toLocaleDateString 😀

Such as : aRandomDate.toLocaleDateString(window.navigator.languages[0])

A guide to use and understand the context managers from the ground

TL;DR the caracteristics of a language is not so relevant, because more time only is needed to write in the worst case. However the most important is the runtime, which can not be changed.

Languages generally become popular when they bring innovative runtime, or when they have runtime exclusivity. The quality of the language itself is secondary.

This way we know all how to give a proper version to a software 😄
Clear, efficient and provided with tools (parser, regex, etc...) 👍

(shared by Arthur HOARO's links)

Well-explained ! It takes some times to read it, but some concepts are clear at the end 💡

if you have Foo and FooBuilder, consider adding a builder method to Foo

that returns the Builder of course

About impl Trait

Rule: If a type parameter only appears in one location, strongly reconsider if you actually need it.

Feedback on using both languages :)

A nice code snippet here :

.checkbox__input {
  display: grid;
  grid-template-areas: "checkbox";

  > * {
    grid-area: checkbox;
  }
}

This will put all children in the same area; and will behave as a position: absolute, but with the power of Grid

Ok 👍 Cool to know !