Vlang

https://github.com/vlang/vorum

https://github.com/vlang/v/tree/master/examples/tetris

https://github.com/vlang/v/blob/master/doc/docs.md

https://github.com/vlang/awesome-v

https://github.com/vlang/doom

memory management
http://aardappel.github.io/lobster/memory_management.html

compile times
https://www.reddit.com/r/vlang/comments/nnza5e/what_are_the_advantages_and_disadvantages_of_vlang/ I’m not satisfied with “compile times are ok as long as you do x y and z correctly”. Ive been working on massive elixir/Erlang projects the last 5 years and its really annoying to stop building features every few weeks to tune compile times. And with diminishing returns. Theres only so much you can do north of 200k lines. Youre going to be waiting 20s-60s after literary every change you make. Swift/rust are even worse than elixir at those sizes. Its hard to build a self sustaining company with a project that isn’t growing and adding features like that. So thats why i like vlang and go, you can keep delivering customer value, as a monolith, for years without slowing down your development feedback loop

links
Oop, Nim lang

https://odin-lang.org/docs/faq/#is-odin-an-objective-oriented-language