go-server-core VS hylo

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.

That's true - there are totally unrelated projects all running under this 1 system. I suppose I could launch a series of these servers that only include pieces they need. That's easy enough here.

Oh cool, that is the case, yes. There are a lot of other issues with what I'm doing, but at least that isn't one of them. You can look at it here if you're curious but honestly I don't know how much longer I'm going to build it up before that joke from ~2018 is put down and I adopt whatever go server framework is popular now.

Here is the main server, here is the router I made with some project specifics in mind, and here is a monster repository that is holding several sub projects that are all reachable from the gateway. Files contains various files served by the sub applications, src contains the go code that gets compiled into plugins.

Y-yea, me too... it's totally obvious that tomato is a restful router, right?

Well, we are on reddit. I'll take validation where I can get it. Want to criticize my shitty golang router?

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)