When JS tools are written in other programming languages, it increases the barrier to contribute in these tools. The contributors need to know a second language.

A rewrite in another language is already a rewrite, which means things will be better built.

Node performance is often slow, but it works without cache... Let's try export NODE_COMPILE_CACHE=1 first.

Moreover JS is easily debuggable.

Eval scoped into a function has a default global scope: wtf.

and a lot of things

Another JS bundler

An alternative to NPM. It looks interesting because it does more than NPM for authors.

Compared to NPM, JSR has native typescript support, ESM Syntax, and some better contraints for interoperability.

More on https://jsr.io/docs/why

Starting with raw HTML, then provides more features with JS

What whis means is that it is possible to open arbitrary applications on your system through a bookmarklet while sending data extracted and preprocessed from the current page by custom JavaScript to that application with the click of a button.

How to create a new URL scheme (such as org-protocol://)

what is really neat here is that with a .desktop file and a bookmarklet, you can send Web data directly from the browser to any local application!

How do we get to a world where our GUIs are as powerful and extensible as our CLIs? When I click Open in Emacs on my bookmark toolbar, and Emacs opens to the code I had open in my browser, I feel like I get a little glimpse of that world that could be.

• know your audience
• careful with breaking changes
• document your way to features when the feature is out of scope of the project
• follow the tag on StackOverflow
• Micro-optimizations can matter

an interactive tutorial series on building realtime collaborative applications using the Yjs CRDT library.

+1

Using other languages to build javascript tools add a barrier to the language.

La nouvelle API Temporal, successeur de Date pour la manipulation de date.

Let the trademark be free

gov.uk does not use jQuery anymore.

L'utilisation incessante JavaScript de pointe a contribué à rendre le web moins accessible, en affectant de manière disproportionnée les utilisateurs dont les appareils et les conditions de réseau sont incapables de télécharger les énormes charges utiles associées à ces frameworks et (2) de gérer la mémoire requise pour exécuter le code du framework dans le navigateur. L'accent mis sur la création d'applications hautement interactives entraîne une coupure d'accès au Web de certains internautes.

Pire encore, les personnes qui ont tendance à posséder des appareils moins puissants et celles qui vivent dans des zones où la connexion à l'internet est plus lente sont souvent celles qui pourraient bénéficier le plus d'un accès bien soutenu au web (par exemple, pour accéder aux services gouvernementaux).