I love these projects so much. It must be exhilarating to work on them and I'm very tempted to work on one myself as a side project/self learning experience.
That Lua debugger/editor with ImGui looks awesome! I’ve been wanting to do a similar project since Lua makes the API for creating breakpoints and stuff pretty easy. Styling ImGui to look like a normal code editor must have been no easy task though.
I have been contemplating lately if we need something like either the early days of computer games or the heyday of the Demo Scene, where people make amusements that are meant to run on embedded computers.<p>I'm not quite sure what that should look like, but in particular making physical puzzles driven by say an STM32 chip could be cool. Especially if you can have it change the rules of the game once you've solved one puzzle.<p>Anyway, teeny tiny game engines brings that whole line of thinking back up for me.
> around 10MB with an empty project<p>I wonder if one could fit the active parts of a entire game inside an X3D CPU's 96MB of L3.<p>Think of the performance!
I played around with Construct2 a lot once upon a time, but never followed them to 3 because the product got a bit too expensive for me has a hobbyist.<p>How does this compare to that, besides the obviously nicer cost?
Silly question from a web dev who has never written a line of Lua before (or delved into game development). What is it about the language that make it such a good fit for game development? Seems like every time I come across these engines, or read stuff about game development in general, Lua is always the language of choice. Can anyone explain it in a nutshell for me? Thanks
I know I'm going to bring down the mood, but that kind of engine should support android as a priority.<p>Godot does it, and it's an awesome alternative to Android Studio.<p>EDIT: although it supports WASM, and I'm curious how well does WASM works on mobile...