hack-game VS Vale

I found it

Also since it's file based it's easy to back up. Just drop the top folder in google drive or whatever. I have one dedicated to a side project I'm working on, so I committed the entire vault to github. Since they are markdown files some of them look ok, but there's a lot of syntax that will look wrong outside of obsidian.

I'm probably misusing the name, but to me it means this. I don't have a solid idea for a client yet for my game server. I haven't tested too much by hand - instead I used integration tests for everything.

Actually the project idea came to me 8-10 years ago! While directly the answer is no, I am still working on a variety of side projects that cover pieces that I need to assemble the overall game. My github has also been pruned a bit, but here's the last for the main game effort. .hack is a big inspiration for me and the chaos gate will be a crucial point for the main game.

What language would you use to build a server? I've been using go for a while and have enjoyed using the different emerging frameworks and even just the standard packages.

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.