nbb VS VisualFSharp

The SCI/babashka clojure interpreter might be a good fit, if you're ok with a lisp.

It's mature and fully sandboxed.

https://github.com/babashka/nbb

To try it out, run npx create-helix-app in your terminal. It is powered by Nbb, Ink, and Helix itself!

Thanks for building! May also want to share in #extension-news in discord to reach more users. Fwiw, you might be able to write the whole script without the need for compilation with https://github.com/babashka/nbb. You may also be interested in https://github.com/logseq/nbb-logseq as a fair amount of logseq core is scriptable

I wish there was something elaborated for scripts that run on Node. I've been using nbb[1] for scripting, and although it all runs through Node.js, it is fast and quick to prototype scripts. The best part is in CI I can simply `npx nbb path/to/script.cljs`. Things get clunky if I want to use anything about of the Node stdlib though, since then you need the dreaded node_modules folder around.

[1] https://github.com/babashka/nbb

For clojure I just found for babashka it seems someone natively compiled jsoup with graalvm and exposed (minimal functionality from it) as a babashka pod, or a possibility would be use nbb like babashka for node. But if racket has the libraries you need and you don't need js/jvm ecosystem than I'm sure it'll be great also

There are some folks using nbb on the backend as well: https://github.com/babashka/nbb, e.g. in AWS Lambdas or via the sitefox framework: https://github.com/chr15m/sitefox. Don't expect stellar performance from nbb since it's interpreted CLJS rather than compiled (as you have with shadow-cljs) but for small scoped projects and fast prototyping it might be ok.

https://github.com/babashka/nbb (babashka for nodejs)

I tried reproducing this example from the nbb documentation.

If you don't want to deal with the tooling but want to practice the language, have a look at https://github.com/babashka/nbb

There's docs about how the compiler generally does optimizations here: https://github.com/dotnet/fsharp/blob/main/docs/optimizations.md

You should add your +1 to https://github.com/dotnet/fsharp/issues/8764, which would add a syntax like #r: project ... to FSI.

So when people are mad about MS and F#, one can see here that: https://github.com/dotnet/fsharp/graphs/contributors MS does a lot more for F# then people being all pessimistic in reddit.

F# AOT feature tracking

Can't speak to the others, but I'm pretty sure the F# team just doubled or tripled in size (it's still small though). Also the GitHub repo is very active: https://github.com/dotnet/fsharp .

Have you tried the workaround listed here? https://github.com/dotnet/fsharp/issues/12239