irrlicht VS Lobster

The Irrlicht Engine seams like a better idea then. https://irrlicht.sourceforge.io/ it is supported and has a small community. Source: almost 2 years ago

I'd recommend Irrlicht Engine. It was very popular during mid-to-late 2000's , and it to my knowledge it still supports OpenGL 1.x as well as its' own software renderer. I once had a PC similar to your specs in 2008, and Irrlicht ran decently alongside ODE physics engine. Source: about 2 years ago

If we're going to list graphics libraries then bgfx and irrlicht are probably worth a mention as well. Source: over 2 years ago

The make or break moment for me was working on an indie game dev team when I was a teenager. I joined a team and was immediately mentored in a way that made programming and code make sense. We developed using open source engines like Irrlichtand Ogre3D, where my mentor was able to detail what came with the different available libraries, and how to utilize them to create a game. He would assign us to create... Source: over 2 years ago

Although primarily intended for games, Irrlicht is a relatively simple library (compared to a full game engine). https://irrlicht.sourceforge.io/. - Source: Hacker News / over 2 years ago

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 / 4 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: about 1 year ago