But really I just see Go as another hype just like React!
Really, lemme just write what I don't like about Go already:
The syntax is funky (comparing to Python).
Co-routine pattern for asynchronous programming never ticked for me... It's just weird. Aside from that, I think the only programming language that got async right is C#.
I see people saying it provides great features like references (and that's what C# and Java provided long ago).
Its frameworks/libraries are not mature... Cuz hey, it's a relatively new lang, and yeah no StackOverflow discussions when you get stuck!
From all those, I just ask myself again and again: what does Go bring new into the table? Not simplicity nor new features, so what?
TBH, I just hate to see people use a specific tech just because a big X company built it... Again, like React and Go 🤭
When people tell me it's for building high performance websites. Well, like: Google?!
While the 99.99 percent of websites they're building is never like Google needs 🙄
The only valid use case that I see is just building tools like Docker and Kuber in an easier lang than C/C++.
I wouldn't be that harsh. As I said I like Go for what it is, it's just that I think it could be a bit better. We can find issues in almost every programming language. The real takeaway from the article should be that we use the right tools for the right job.
Google has a serious case of “Not Invented Here” syndrome. Sometimes that works out, sometimes it doesn’t. I’ve not written any Go, but I’ve read enough of the Terraform codebase and of several k8s controllers to not be impressed. If they add generics I might take it for a spin, but I can’t yet see a usecase for Go where I wouldn’t just use Rust, Elixir, or F# instead.
I never used Go before... it's on my list to try.
But really I just see Go as another hype just like React!
Really, lemme just write what I don't like about Go already:
The syntax is funky (comparing to Python).
Co-routine pattern for asynchronous programming never ticked for me... It's just weird. Aside from that, I think the only programming language that got async right is C#.
I see people saying it provides great features like references (and that's what C# and Java provided long ago).
Its frameworks/libraries are not mature... Cuz hey, it's a relatively new lang, and yeah no StackOverflow discussions when you get stuck!
From all those, I just ask myself again and again: what does Go bring new into the table? Not simplicity nor new features, so what?
TBH, I just hate to see people use a specific tech just because a big X company built it... Again, like React and Go 🤭
When people tell me it's for building high performance websites. Well, like: Google?!
While the 99.99 percent of websites they're building is never like Google needs 🙄
The only valid use case that I see is just building tools like Docker and Kuber in an easier lang than C/C++.
I wouldn't be that harsh. As I said I like Go for what it is, it's just that I think it could be a bit better. We can find issues in almost every programming language. The real takeaway from the article should be that we use the right tools for the right job.
Google has a serious case of “Not Invented Here” syndrome. Sometimes that works out, sometimes it doesn’t. I’ve not written any Go, but I’ve read enough of the Terraform codebase and of several k8s controllers to not be impressed. If they add generics I might take it for a spin, but I can’t yet see a usecase for Go where I wouldn’t just use Rust, Elixir, or F# instead.
Yeah exactly... I really can't understand what people think when they use the tools you mentioned just "cuz it's Google tool" 🤯