v-mode VS Vale

Fingers crossed for vlang[0]. It's like golang with better types and more syntactic sugar. Feels like a proper upgrade from Python.

I really hope they succeed.

[0]: https://vlang.io/

And again a No true Scotsman. If that's the kind of attitude you have towards languages, you'll appreciate V infinitely more than you might be appreciating Rust. After all, it offers better solutions than Rust, like autofree, they just aren't there yet :)

I discovered VLang today. It's an interesting project.

According to their own benchmarks, Seed7 can run faster than C (it compiles to C, but it's entirely possible the emited code is better optimized than a human could write directly in C)... it doesn't have a GC BUT manages memory automatically (I didn't really follow the explanation in the FAQ, something about automatically freeing variables that go out of scope and keeping only one reference around?)... that's like a current pipe dream for language designers! From https://vale.dev/ to https://vlang.io/, no one has pulled that off yet, to my knowledge... has Seed7 done that all those years ago?!

Help V programming language to gain more popularity and show to game development community that this is a good language for game development

Try http://vlang.io

Not to be confused with Vale[0].

[0] https://vale.dev/

The article says they created a deterministic hypervisor that runs all pseudorandom behavior from a starting seed to enable perfect re-playability.

But that's all we know so far. I'm assuming there'll be some sort of fuzz testing, and static analysis or some defining actions that your software can perform.

Honestly it sounds a lot like it has a lot of crossover with what the Vale language is trying to solve: https://vale.dev/, but focused on trying to get existing software to that state instead of creating a new language to make new software already be at that state by default.

Why go through all the trouble when you can do this: https://www.hylo-lang.org/ and not spend a second thinking of lifetimes? No, copies will not be issued unless necessary.

Or why not keep exploring this idea as well? More research-oriented than the first one right now, though, so take it with a grain of salt: https://vale.dev/

Another relevant language might be Vale (https://vale.dev), which is aiming for "perfect replayability": https://verdagon.dev/blog/perfect-replayability-prototyped

Interesting. Very low level though and C(++) centric. She there any thoughts on combining the hardware and OS features with rust or https://vale.dev ?

Use a runtime memory management solution that's cheaper than garbage collection (see Vale)

This seems like a tool I'll be using, and this is an almost meaningless criticism, but why the name?

There's already the Vale programming language (https://vale.dev/), but moreover, I don't get the meaning of "vale". You could call it something like Englint which actually hints its purpose.