The Final Nail in the Coffin for Go
Published at 16:47 on 25 June 2024
The same Go program I had to fight with for two days to get to the point where it was still unfinished, but:
- I had satisfied my curiosity that it was, indeed, possible to do the particular thing I was struggling with in Go, and
- It had been painful enough to prove to me that I should not consider Go a language of choice.
… Has now been coded to the same stage of completion in C++. It took half the time, half the effort, and under half the lines of code that it did in Go.
And that is as an absolute novice C++ programmer, writing his second C++ program ever. I had been experimenting with Go for about a year before I recently gave up on it.
It’s not that C++ is good, mind you. It’s a total cruft fest that should have been put out of business by something more modern at least 15 years ago. But it’s still possible to do things in C++ without the language and/or standard library persistently getting in your way like they do in Go.
Go is so bad it is literally worse than C++.