Golang in 15 years will likely converge and embrace many of the missing features of mature languages (its happening now already), especially if it wants to reach broader adoption.
A reference like "Go is a get shit done language." very much reflects overall immaturity of the language that I see day to day.
Go is 10 years old already and picking new features at an extremely low rate, with no hints at a pace change.
I think error management and generics should be the only major changes to expect within the next 5 years. C# is more complex by an order of magnitude... And thus its evolution was and is still way faster.
I bet a G2EE variant isn't too far away.
Yep, they aren't pure C#, still way more relevant to the world IT infrastructure than anything Go.
The core sql server rdbms engine is hosting the .net runtime for a few things - but there its maginal compared to C++.
Modern stacks are seldom pure blood language X, thus if 5% of it is written in Y, the product is written in a mix of X and Y.
Which I also mentioned on my comment, "Yep, they aren't pure C#", naturally overseen when one intends to champion its language as "Year of Desktop Linux" on IT infrastructures.
The Linux kernel is 0.2% of shell scripts, yet no one would say it's written in shell. Same for windows or sql server. .Net is marginal there.
Btw I do code in Go, but I mostly use go apps and enjoys their small memory footprint and ease of deployment.
I must not be the only one as I see go apps pretty much everywhere in ops teams.
Fortune 500 prefer to care about actual delivered business value.
Go talk to some SRE team in F100 and F500 and ask them what they think about C# infra side lol.
The fact that C# was running on Windows only until 2 years ago explains why.
Plenty them do run production servers on Windows.
You forgot there are 498 left to check.
What infrastructure, those riding the consulting and conference Docker and K8s 2019 wave fad?!?
All of this in a conservative big bank. My friends in the banking sector tell the same story.
True there are lots of c# enterprisey web apps.
However given the amount of boilerplate you describe, I cannot understand how such useful and reliable tools can be delivered in Go.
A hint:just because a language is not to your liking, it does not mean that it is not useful, performant and reliable.
AWS, Azure, actual hardware racks, plain old VMs, JEE containers, .NET packages, Ansible, Puppet, Chef, whatever scripting stack, but surely not one line of Go related code.
I don't follow your logic. Multitudes of useful and reliable tools were built with assembly languages - is that evidence that assembly code doesn't have a lot of boilerplate (relative to modern languages)?
Honestly I think that's pretty wrong. Go is designed to let you get coding quickly. It's not designed to make your ultimate solution well designed are easily refactorable. In a few years there's going to be a ton of Go code that becomes almost as bad as C where it becomes untouchable because people quickly threw something together and didn't think about long term design.