Lobster VS Stride Game Engine

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/. - Source: Hacker News / 5 months ago

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... Source: about 1 year ago

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. Source: about 1 year ago

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. Source: about 1 year ago

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. Source: over 1 year ago

I leave this little thing: https://stride3d.net. Source: almost 2 years ago

You can have a look at Stride - you also write games in C#, and it's open-source entirely. Its documentation has also some nice comparison of Stride to Unity, including some guidance about porting Unity code to Stride: https://doc.stride3d.net/latest/en/manual/stride-for-unity-developers/index.html. Source: almost 2 years ago