So, you want to make a game engine
lisyarus.github.io
lisyarus.github.io
For example looking at his video, the graphics is still in a really basic/alpha phase, a lot more lighting/shader work will be required just to get on par with for example Unity Built-In/URP.
Then your game might need a host of other things, what about character animation, high volumes of entities etc. It's something people don't mention when talking about Godot, Stride and all the other relatively newer engines. They forget how much work has gone into Unreal and Unity to get them where they are today.
"I think we can make major strides towards AGI this summer" in 1970 == "I think we can make major strides towards GUI this summer" in 2020s.
Making a UI lib might be harder than anything else on the list. Even physics is somewhat tractable if you stare into the XPBD paper long enough. UIs have been an unsolved problem for 50 years.
- GUI, something almost every single app has since 1980
But somehow the difficulties are comparable. I really like HN comment section.
Unless you have a really good reason, it's probably not a good way to make a game. It is fun though, and you learn a ton!
would it be a good idea to use a WASM runtime as the basis of your scripting engine?