gomacro VS Quasar

gomacro added macros and generics several years before generics reached release.

I use https://github.com/cosmos72/gomacro when I want to quickly try some code.

Officially, it's not much scripting friendly, but there are unofficial support to make it a proper scripting option like the gomacro.

If it's a simple program I guess you could use gomacro:https://github.com/cosmos72/gomacro

Thanks to gomacro we can import no standard libraries on the notebook :P

For our use (debugging and running small scripts to update data), gomacro should work well enough, despite being an "almost complete" Go interpreter. This isn't the same as the Python REPL which uses entirely the same code to run, but it should be up to the task.

I keep meaning to play with https://github.com/cosmos72/gomacro

Java 21 doesn't retrofit green threads though. Quasar [0] is a library that implemented fibers for Java and the main developer pron has joined the OpenJDK development team. All that was necessary for first party support is to make the JDK libraries yield when blocking.

Adopting async isn't impossible at all, there is very little demand for it.

[0] https://docs.paralleluniverse.co/quasar/

Third party options have been around for nearly a decade now: https://docs.paralleluniverse.co/quasar/

Quasar Fiber (https://docs.paralleluniverse.co/quasar/) is the equivalent implementation of goroutine in Java.

Even Loom architect Ron Pressler had something else in mind with his earlier prototype Quasar, with a spaceship demo.

I'd say because of Erlang. Loom's architect was building a bytecode-modifying (with a javaagent) lib named Quasar before he joined Oracle. The project page mentions a news titled "Introductory blog post: Erlang (and Go) in Clojure (and Java), Lightweight Threads, Channels and Actors for the JVM." in May 2, 2013.