> Kubernetes itself which for most users today still relies on Docker
Not anymore, over the past couple of years Kubernetes slowly stripped Docker most of its power to the point that Docker can be totally removed from k8s clusters. And this will be widely be the norm in a couple of years or so
Jim Simons and David E. Shaw are legends who should have some HBO series about them. Both were researchers who left academia to beat the scumbags of wall streets in their own game with no finance background and they made unbelievably so much money in a very short of time that they would have been jailed or killed if they weren't in the US.
ffs you are a CEO of a major public company and make 100s of millions per year. 99% of your job description is to be a thoughtful bulshitter yet that's the best you've got?
Thank you Alex Crichton, Niko Matsakis and all other core devs, Rust is by far the most well designed programming language I've ever dealt with. It's a masterpiece of software engineering IMO.
>transferring money to people who are unproductive
says the professional unproductive hedge fund manager. The parasite billionaire who spent his life capturing the profit made and value created by companies
He forgot the most important factor to Go's success: ignorance is bliss. Imagine releasing such a mediocre language only a decade ago an still be very popular
Golang has shortcomings a plenty, although that doesn't necessarily make it a poor language to use.
It's a fairly simple language, which makes it relatively easy to grasp and understand the majority of Go code. This is particularly useful for group development (i.e. in companies), where you want everyone to understand each others' work.
Anecdotally, although I prefer to write Rust, and consider it a better language in many ways, it took me a lot longer to learn the language, and longer still to write idiomatic Rust code. I was up to speed with Golang relatively quickly.
Not the OP, but I think a good contrast is with Rust. Both languages purportedly emphasise memory safety and concurrency. Rust achieves this within the type system at compile-time; no nil pointers (conditional destructuring is used instead), no garbage collection is required, and concurrency is safe by virtue of compile-time checks. In Golang nil pointers exist and can be dereferenced, you can make a mistake when using concurrency primatives, and clobber shared memory.
On the other hand, Golang is a much simpler language. It's relatively easy to learn and understand.
Some popular Rust projects include actix-web (HTTP serving), diesel (database ORM), Firecracker (micro VMs for serverless). Web APIs and virtualisation / cloud computing are also areas where Go is popular.
They're both statically typed compiled system programming languages; both trying to provide solutions for safe memory and concurrency.
Criticizing Golang here in HN will get me banned for causing flamewar. However, you can find lots of reasonable criticism on Golang just by googling. IMO Golang is one of the worst languages I've ever seen considering it was only started a decade ago.
Once I listed around 10 technical criticism points here a year ago without insulting and I got banned. I am just not going to waste a day trying to convince anybody with anything while most of the criticism has been stated a million times by a million people all over the internet.
Well, I haven't read it, nor have I seen much other criticism of Go. If you post here, it is up to you to make your argument, not for your readers to seek it out.
I have seen plenty... but not all that much substance. Much of it had the form of "How could they be so stupid to make those design choices!", as if the author's preferred approach was The Only Right Way. I've seen criticism that said "They couldn't have known anything about Modula 3 for them to make that choice!", when in fact Rob Pike talked about stealing an aspect of the object file format from Modula 3. Yeah, he knew it, and probably knew it in more detail than the critic did.
Apart from "They should have done it the way I like!", the main criticism I have seen is lack of generics. That's a pretty common complaint, from a lot of different people.
> Criticizing Golang here in HN will get me banned for causing flamewar
that's either reductive or a strawman, if not both. afaict golang doesn't lack for criticism on hn, but most people do so without being insulting or hostile.
If the rules are consistent and persistent, then you should be banned again as you have criticized Golang, but furthermore, provided zero substance to back your criticism.
Yours is not criticism, it's just ignorant bashing of a perfectly productive language that people adopted not because they're more stupid than you but because it made them more productive for whatever reason.
No one forces you to code in Go if you don't like it. Fine, but don't belittle others if you're not prepared to understand why it's got so popular. Ignorance is bliss.
Thanks for the swift response from the founder, I just don't understand those types of sneaky github issues that surprisingly get very rapidly to the HN frontpage as smear campaign against startups, when even setting the application name and version in the user agent header in a FOSS application that can be opted-out is considered spying, then everything can be spying
Not anymore, over the past couple of years Kubernetes slowly stripped Docker most of its power to the point that Docker can be totally removed from k8s clusters. And this will be widely be the norm in a couple of years or so