I’m not sure, the whole point of this language, standard libraries and runtime is built around GC. Nobody from C# world is educated or prepared to manually manage memory. This is just bare metal C++ with a lot of it stripped away and just nicer/cleaner syntax that does not inherit so much from C and POSIX archeology.
Nice POC, especially on MS-DOS but nothing truly relevant in the long run, I’m afraid
GC is not surrendering control. That seems to be HN's #1 bug bear. The sensation that someone or something is taking control away from you. The proper way to frame this is that you can actually focus on the original problem you set out to solve. Risking memory leaks is crazy when it's not something the customer is demanding. Even in gaming I think the GC is fine. There are ways to spread the impact across frames and bound the amount of time spent collecting.
If your clever scheme wouldn't work with a GC-managed heap, it probably won't work with one managed by hand either.
I’m not sure, the whole point of this language, standard libraries and runtime is built around GC. Nobody from C# world is educated or prepared to manually manage memory. This is just bare metal C++ with a lot of it stripped away and just nicer/cleaner syntax that does not inherit so much from C and POSIX archeology.
Nice POC, especially on MS-DOS but nothing truly relevant in the long run, I’m afraid
The GC is a feature. Not a bug to be eliminated.
GC is not surrendering control. That seems to be HN's #1 bug bear. The sensation that someone or something is taking control away from you. The proper way to frame this is that you can actually focus on the original problem you set out to solve. Risking memory leaks is crazy when it's not something the customer is demanding. Even in gaming I think the GC is fine. There are ways to spread the impact across frames and bound the amount of time spent collecting.
If your clever scheme wouldn't work with a GC-managed heap, it probably won't work with one managed by hand either.
I like arena allocators, but some how i fel like reference counting would have been a better match for C# philosophy, like swift.
The "without any GC" part has me worrying. Is this advocating to just accumulate your garbage and throw it out only once every blue moon?
Also, does it ship with GUI libraries?
“Memory comes from arenas you free all at once”
Reminds me of Beef: http://www.beeflang.org/
Finally, C--
Don't you mean C♭?