VisualFSharp VS rune

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

A Lisp, a weird dialect of Lisp, is not better than Lua. Why use Rune [0]?!

[0]: https://rune-rs.github.io/

This is what I based my comment on - https://github.com/rune-rs/rune/issues/444

Late start today as well. I really thought today would be the day that I'd have to abandon my goal of no heap allocations. But, luckily I had an arena allocator available that I could fairly easily adapt to store data on the stack. And with some tweaks we have today's solution:

I'd have given you bonus points for using a rust styled scripting language like rune but that's pretty neat still

As note about using rust syntax for scripting: https://rune-rs.github.io/

I know you said you don’t want to embed another language but IMO Rune is worth a consideration here. It can be a pretty thin abstraction over rust by passing native structs to scripts and calling methods on them. The syntax and semantics are very close to rust so it feels natural. https://github.com/rune-rs/rune

The biggest technical difference I'd say is that Rune uses a stack-based machine which makes adding deep C support somewhat obvious while Rhai performs AST walking to execute scripts.