Tango-D2 VS Beef

The standard library split was about API design, not GC. D1 Phobos (the official standard library) had a C standard library style API, and Tango was more like Java. And because Tango was a class-based API, it used GC more heavily than Phobos did. The split was resolved in 2007 as D2 was under development, when the common runtime was split out from the standard library. A D2-compatible version of Tango is usable today, though most D programmers these days Phobos.

Is it really a one man show? It looks like Beef Lang has excellent home page https://www.beeflang.org/ and I never heard about it until now.

Jai is dead, this is the year of Beef from the genius behind Plants vs. Zombies and Bookworm Adventures Deluxe.

On one hand, I feel there are so many similar languages out there {(Val, Vala, Vale, Corroded Iron, Beef, Zig, Carbon, cppfront, Jai)...}, that we don't need yet another, but also I encourage further thought because it may be inspiration for future improvements to C++ itself. The number one faux pas I see them make is trying to directly compete with C++ (inventing their own type system, their standard library, their build system, own package format...), whereas your (by its very nature as a transpiler) embraces C++.

This project is an exploration of two things. Firstly I wanted to dig into the exciting new language and IDE, Beef. If you're the low-level code oriented type I _highly_ recommend checking it out. Beef is a systems-level language (like C/C++) that borrows heavily from C# but ditches the garbage collector. It comes with a wonderful IDE and a great debugger and just an excellent work flow. Check it out at https://www.beeflang.org/.

That's why I love C#, Rust and Beef so much - no need to worry about pointers and segfaults and the code is generally nice to read unless you do something extremely crazy.