Richard Bucker

A Golang Warning

Posted at — Aug 8, 2024

In lite of Ross Cox stepping down from Gloang… it bares repeating… Golang is dead long live golang.

First there was Golang. It was defined as a system programming language. Meaning a language that was quick, performant, agile, easy, solved complex tasks and so on; and suited for developing tools. It was also basically done. Meaning language changes were bug fixes, non-braking, and did not change the language. Then came generics.

golang is dead

Java programmers decided that they had enough of all the Java cruft so they started to adopt Golang… but then common sense got the better of them and they thought that Golang was meant to solve all the problems and to do that you needed generics. Of course that was just wrong on so many level but some how they managed to convince the people the matter. I suppose there might have been a concern about forking… and yes that would be worse.

ugh GENERICS

So now what? The next question is will we ever see a golang verion 2. In the golang rules a version 2 is allowed to break the rules… but then just look at python 3. It’s a mess. Perl 9 is even worse.

So now what? I’m still undecided. I mean Golang robustly supports multiple platforms and I can just ignore generics. Any my mission is to write my interpreter in golang so that I do not have to write C any more and I can avoid rust at all cost.

Now I’m waiting for something new.