mun VS lobster

Mun is a statically typed language that compiles to machine code with LLVM, designed to be hot-reloadable: https://mun-lang.org/.

Perhaps https://mun-lang.org? Might be a bit raw for your needs tho.

But that’s not all! In total, this release contains 111 pull requests made by 5 of our community contributors and our two Core Team members & Dependabot. Thanks for having our back! For a full list have a look at the changelog, but the main improvements are:

Whenever I read about Mun, I'm always really, really intrigued… Until I remember that it currently has no string type and support for one is not currently planned. That's a bit of a shame, IMHO, because otherwise, this looks great!

There's mun [1] which is statically typed and AOT compiled.

1: https://github.com/mun-lang/mun

From the reverse-dependencies of the salsa crate, the (archived) Lark compiler used it and the Mun compiler uses it.

I notice that there are projects like mun trying to achieve a similar goal, but I'm kind of curious why they are not getting much attention from the community.

Have you heard of https://mun-lang.org/ ?

It's an embeddable scripting language with the goal of being a Rust-like language that supports hot reloading of functions AND data. To achieve the latter, it uses GC'ed memory such that memory can easily be mapped when the memory's type changes.

It's still in early development but maybe one day will serve your needs :)

In terms of pure Rust engines/frameworks it seems the overall "problem" is lack of scripting, at least from my perspective. Mun seemed extremely interesting, but since even the project itself says "don't use it" I guess it's not a real option, and considering the amount of time we spent on the GDScript/Rust integration I'm a little worried that rolling something more custom would be even less efficient.

I think lobster does this.

"Compile time reference counting / lifetime analysis / borrow checker."[1]

"Reference Counting with cycle detection at exit, 95% of reference count ops removed at compile time thanks to lifetime analysis."[1]

[1] https://strlen.com/lobster/

There is another language, Lobster, that uses lifetime analysis like Rust, but IIUC infers lifetimes completely automatically. It looks like the idea is still experimental - I'm interested to see how it goes.

I think the ability to open a window and do graphical stuff is actually pretty underrated in core language functionality. There's a few game-oriented programming languages like Lobster that put windowing and graphics in the core language functionality, and I think it's pretty neat. The biggest downside is that it's a lot to bite off, because you'll probably want to have standardized API functionality for a whole host of things like font rendering, image loading, etc.

The actual game itself, yes. Based on this open source project though which provides the language its written in and core engine tech: https://github.com/aardappel/lobster

I'm keeping an eye on Lobster though. It fixes most of Python's problems. It's way faster, has proper static typing, the import system is sane, etc.

Lobster (https://strlen.com/lobster/) appears to at least do lifetime analysis to reduce refcounting. I'm not sure about automatic interior mutability. I feel like there's a keyword here that can help find other compilers with similar features.

Also, can I introduce you to https://strlen.com/lobster/, a garbage collected language made for game development by (and primarily for) the one and only Wouter "aardappel" van Oortmerssen?

I would like to make it work to some degree like Rust with a borrow checker, and have optional static typing (with type inference wherever it can). Other sources of inspiration, lobster lang, and dart. It is going to (eventually...) compile to several places like dart (browser, iOS, android, linux, etc.). After I've created the AST, I've gone straight to code generation, because that's the easy part IME. But now have to insert the "middle" and do typechecking/borrowchecking/inference/other checking. This is for an imperative-style language.

Over the ~12 years of Lobster (https://strlen.com/lobster/) 's existence, features that were removed (in this order): * Lexical scoping. * Icon style backtracking. * Small-talk like syntax. * Dynamic Typing. * Multimethods. * Frame based state (like FRP). * Co-routines.