Our great sponsors
-
carbon-lang
Carbon Language's main repository: documents, design, implementation, and related tools. (NOTE: Carbon Language is experimental; see README)
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
zig
General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
v
Simple, fast, safe, compiled language for developing maintainable software. Compiles itself in <1s with zero library dependencies. Supports automatic C => V translation. https://vlang.io
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
No, by using a language that's significantly more amenable to modern tooling (e.g. not a pain in the arse to parse) and has learnt from the mistakes of its predecessors. Read through the language design overview to get a better idea of what it does.
There are some Go alternative languages such as Vlang and Odin. So there are options to transition to and/or contribute as a developer on.
I love Erlang, but its strengths are concurrency and fault tolerance, not high performance compute. Unless you pair it with Rust of course ;)
Again, not really...? A lot of the proposed ABI changes (for C++ - I don't know what they're planning for Carbon) are trivial to automatically fix if you have source access. If you don't have source access, you "only" need to maintain the ABI at the boundaries between foreign code and your code, which is quite possible (especially after the success of autocxx and related projects in the Rust <-> C++ world)
Obligatory https://killedbygoogle.com/
I know it's not quite what you're asking for, but check out Vala, which is effectively writing C in C# https://vala.dev/
https://github.com/ksimka/go-is-not-good an entire repo dedicated to articles on the topic
Also check out Vale, https://vale.dev/. It's another serious PL experimenting with new ideas
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.
Worth noting that the long-time maintainer of Protobuf eventually left Google and made Cap'n Proto. It doesn't get as much development time but you have much closer communication with the developer.
Vlang, a Go alternative language, has had: generics, map, filter, and more for quite a long time (https://github.com/vlang/v/blob/master/doc/docs.md).
There are some Go alternative languages such as Vlang and Odin. So there are options to transition to and/or contribute as a developer on.