proposal-hashbang VS babashka

Before ECMAScript 2023 (ES14), executing a JavaScript file directly from the command line required manually specifying the interpreter path in the first line of the module. This process could vary depending on the operating system and Node.js installation.ES14 standardizes the use of hashbangs (#!) in JavaScript modules, enabling direct execution without the need for explicit interpreter invocation. The hashbang syntax is a simple convention that indicates the interpreter to be used for executing a module. It consists of a shebang (#!) followed by the path to the interpreter and optionally any arguments. For a JavaScript file, the hashbang line typically includes the path to the Node.js executable.

https://github.com/tc39/proposal-hashbang has some details.

Hashbang Grammar

Hashbang Grammar: match de-facto usage in some CLI JS hosts that allow for #! Shebangs / Hashbang.

But if you just wanted to execute it directly then you could use a shebang because everything after the bang is interpreted and not the bang its self. Most js engines allow this in some form. Here is a proposal to standardize it. https://github.com/tc39/proposal-hashbang

It also gives you access to Babashka if you want Clojure for other use-cases where start-up time is an issue

https://babashka.org/

I've tried researching this myself and can't find too much. There's this project metaes which is an mci for JS, and there's the SCI module of the Clojure babashka project, but that's about it. I also saw Triska's video on mci but it was pretty theoretical.

Created by the same guy who created babashka which is a way to write bash scripts, node scripts, and even apple scripts using Clojure. A very proficient and influential developer in the Clojure community. This is how borkduke's neil helps us:

Not what you asked for but there is Babashka for scripting in Clojure.

https://github.com/babashka/babashka

Clojure's lazy sequences by default are wonderful ergonomically, but it provides many ways to use strict evaluation if you want to. They aren't really a hassle either. I've been doing Clojure for the last few years and have a few grievances, but overall it's the most coherent, well thought out language I've used and I can't recommend it enough.

There is the issue of startup time with the JVM, but you can also do AOT compilation now so that really isn't a problem. Here are some other cool projects to look at if you're interested:

Malli: https://github.com/metosin/malli

Babashka: https://github.com/babashka/babashka

Clerk: https://github.com/nextjournal/clerk

Being a Clojure addict, I guess I have to leave the obligatory link to Babashka too then: https://github.com/babashka/babashka (Native, fast starting Clojure interpreter for scripting)

which is now on hiatus. babashka: https://babashka.org

I've enjoyed babashka for scripting; which is close enough to clojure to allow using some/many libraries; but (probably) not for embedding.