hack-game VS hylo

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.

Or Val[0], now called Hylo (for a good reason), or V[1].

[0] https://www.hylo-lang.org

The evolution of C++ has been a multi-decade history of dealing with difficult reality.

I have great hope that Herb can create with his cppfront project “The Very Best of C++” to carry that tremendous legacy forward.

If I was to throw my hat into a “C++ successor”, it would be https://www.hylo-lang.org/ with its “all the safeties” and “tell you when you’re doing it sub-optimal” approach.

Paper: https://2023.splashcon.org/details/iwaco-2023-papers/5/Borro...

> Hylo is a language for high-level systems programming that promises safety without loss of efficiency. It is based on mutable value semantics, a discipline that emphasizes the independence of values to support local reasoning. The result—in contrast with approaches based on sophisticated aliasing restrictions—is an efficient, expressive language with a simple type system and no need for lifetime annotations.

> Safety guarantees in Hylo programs are verified by an abstract interpreter processing an intermediate representation, Hylo IR, that models lifetime properties with ghost instructions. Further, lifetime constraints are used to eliminate unnecessary memory allocations predictably.

https://www.hylo-lang.org/

https://github.com/Hylo-lang/Hylo

A model without lifetimes is also being explored in other languages, e.g. in Hylo. It sacrifices expressiveness, but on the other hand you don't have to deal with explicit lifetimes!

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/

Get rid of references at the cost of some expressivity (see Hylo, formerly Val)