News for hackers. Stuff that matters.
Re:Why people in Google hate Go? by jjgreen on Friday November 03, 2023 @06:48AM (#38126816)
Go puzzles me. It's slower than C/C++/Rust and GCed, so not really suited for performance critical stuff. No OO so not really suited for larger complex applications. So for smaller not-performance-critical programs, why not Python, Typescript etc? It seems that its popularity exceeds its scope, or am I missing something?
Re:Why people in Google hate Go? by vcryan on Friday November 03, 2023 @06:59AM (#38126902)
Not seeing how OO makes a language more suited for complex use cases. If you said OO approaches add complexity to any use case, I would agree to that.
Re:Why people in Google hate Go? by vimsee on Friday November 03, 2023 @07:03AM (#38126930)
Why does it need to be the best in one single metric when it can be great in many?

It is an order of magnitude faster than Python. So it is well suited for performance in many cases.

It is a lot easier to pick up than C/C++. So it is well suited for smaller programs.

I can see Go as a very good middle-ground.

Re:Why people in Google hate Go? by benterix on Friday November 03, 2023 @07:29AM (#38127175)
> It is a lot easier to pick up than C/C++.

I would say, "it is a lot easier to pick up than C++" as the language specification is much smaller. I wouldn't be so sure about the comparison to C, though.

Re:Why people in Google hate Go? by usrbinbash on Friday November 03, 2023 @07:48AM (#38127320)
The fact that Go doesn't have C's macros alone already makes it a lot simpler.

And please don't get me started on writing concurrent code in C.

Re:Why people in Google hate Go? by EnergyAmy on Friday November 03, 2023 @09:41AM (#38128619)
`//go:generate` is far worse than C's macros
Re:Why people in Google hate Go? by saturn_vk on Friday November 03, 2023 @10:29AM (#38129330)
That's just a glorified make rule. There's nothing inherently hidden or complex that it generates, unlike macros
Re:Why people in Google hate Go? by majewsky on Friday November 03, 2023 @10:59AM (#38129801)
I have written Go professionally for close to 10 years. The only time I encountered go:generate is in yacc parsers deep within libraries. A regular Go developer might go for years without realizing that it even exists. Compare this to C macros.
Re:Why people in Google hate Go? by shrimp_emoji on Friday November 03, 2023 @12:35PM (#38131159)
> It is a lot easier to pick up than C/C++.

That's why corporations like Google invent "middle-ground" languages.

Go from Google

Java from Oracle

C# from Microsoft

These companies need some performance, but they can't hire enough C/C++/Rust devs (not enough exist). They're flush with JS/Python devs, but those languages are too slow.

So they invent these abominable "middle-level" languages, with their insane bloat.

For myself, I'm not interested in mediocrity to serve corporate interests, so I don't touch them. :p Extremes only: Python and C; Ruby and Rust; JS and C++.

Re:Why people in Google hate Go? by hobos_delight on Friday November 03, 2023 @04:17PM (#38134430)
> Java from Oracle

Oracle acquired Java with Sun Microsystems, it was originally designed for embedded systems and the dream of “write once, run everywhere”.

The idea of a “hardware JVM” always fascinated me, I seem to recall some parallax microcontrollers that could run a subset of jvm bytecode back in the 90s, but never actually got to play with them.

Re:Why people in Google hate Go? by madeofpalk on Friday November 03, 2023 @06:56AM (#38126869)
And still has null pointer exceptions. I could see a role for it in between like rust and python if it had a sane type system.
Re:Why people in Google hate Go? by Cwizard on Friday November 03, 2023 @06:58AM (#38126889)
I really like Go but the type system is just a bit too weak in my opinion. It is the biggest issue I have with the language ( and the fact that errors are basically untyped, you can type them but no one does…)
Re:Why people in Google hate Go? by rplnt on Friday November 03, 2023 @07:09AM (#38126998)
It's fast enough for most applications. Python and Typescript are unmaintanable. Everything around them breaks as the time goes by. I'd argue Python is not suitable for anything that spans more than one file or one week. I don't have enough experience wtih Typescript to hate it as much, but I know I spend most of my time fighting with the tooling. Again, unless you are writing a fresh application that is fine to throw away after a year, Typescript is not it.

Go excels in that it is so simple. As the saying goes, you mostly read code, not write it. Go is very easy to understand and review. Which is what you do mostly when working on complex systems in teams. It's extremely easy (and fast) to build and deploy unlike the languages above. That's why companies use go. Not for personal projects, not for drivers, and also probably not for corporate monoliths that require a suit and a tie to contribute.

Re:Why people in Google hate Go? by jjgreen on Friday November 03, 2023 @07:31AM (#38127181)
Heh, my brother-in-law is a Java suit-and-tie dev, he was telling me that he'd been working on a project for 18 months, the specifications were almost complete and he'd be starting on the coding soon. Being in the startup space I was slack jawed, it's a half-day planning and then start hacking up the MVP for me. Worth noting that he drives a BMW.
Re:Why people in Google hate Go? by EnergyAmy on Friday November 03, 2023 @10:29AM (#38129332)
Go is easy to understand like Brainfuck is. One singular piece is easier to read, but you've just spread the complexity around, making it hard to see the bigger picture.
Re:Why people in Google hate Go? by Cwizard on Friday November 03, 2023 @07:02AM (#38126920)
It compiles down to a single binary and is relatively easy to write. I think that is the reason it is such a popular language for CLI tools.

You will never have an issue with missing dependencies or outdated runtime.

Re:Why people in Google hate Go? by scumola on Friday November 03, 2023 @11:04AM (#38129886)
Nothing is stopping anyone from compiling C or C++ code into a single static binary too. This argument is bull$%!#.
Re:Why people in Google hate Go? by dontlaugh on Friday November 03, 2023 @07:05AM (#38126966)
OOP is generally a bad idea, so lacking it is not a downside.

The bigger problem is the weak and inexpressive type system, which is no better for C or Python.

Re:Why people in Google hate Go? by amelius on Friday November 03, 2023 @06:55AM (#38126858)
The same can be said about Rust: its popularity exceeds its scope, because 99% of applications I see that are written in Rust are better off written in a GCed language.
Re:Why people in Google hate Go? by brigadier132 on Friday November 03, 2023 @06:56AM (#38126867)
Except when you suddenly do need performance and predictable latency but all your software is written in python. Its always funny how these performance requirements just creep up on you like that.
Re:Why people in Google hate Go? by ycuser2 on Friday November 03, 2023 @06:59AM (#38126901)
C# is GCed but has 'unsafe' blocks.
Re:Why people in Google hate Go? by neonsunset on Friday November 03, 2023 @07:15AM (#38127059)
Yup, and (monomorphized) struct generics, first-class SIMD vectors and ability to transparently work with memory ranges because Span<T> can also wrap T* + Length from unmanaged code, which lets you directly plug whatever data you got from C/C++ dependency into most CoreLib APIs.

In this regard, Go is far inferior as a systems programming language.

Re:Why people in Google hate Go? by pjmlp on Friday November 03, 2023 @07:08AM (#38126989)
Alonside value types, manual memory allocation if needed.

Not all GC based languages are made alike.

Re:Why people in Google hate Go? by amelius on Friday November 03, 2023 @07:12AM (#38127028)
Yeah what we really need is a GCed language that allows you to implement parts in no-GC mode. And ideally where you can iteratively migrate GCed parts to no-GC parts when required.
Re:Why people in Google hate Go? by jiripospisil on Friday November 03, 2023 @07:11AM (#38127021)
Except when you actually enjoy things being fast. For example, HTTPie easily adds 0.5-1s delay to every request because it's written in Python, especially on the first invocation. xh (https://github.com/ducaale/xh), on the other hand, starts immediately because it's written in Rust. I very much like this trend.
Re:Why people in Google hate Go? by benterix on Friday November 03, 2023 @07:36AM (#38127229)
Yeah, I agree on that. In the nineties, basically the only general purpose language was C, with C++ growing in pains (and then extending uncontrollably) and Java promising to get better but having its own issues at that time. So people who needed to get their job done (efficiently) just used C, like Torvalds.

At that time, this new Python language was a curiosity. It was nice that you could easily replace dozens of C code with one line of Python but everybody was aware it's too slow. However, this window shifted with time. The perceptions of "fast" and "slow" changed for various reasons such as network delays so Python became acceptable in many areas it would be dismissed otherwise. To the point it became the no. 1 language now.

But we are not in the 2000s anymore. We do have powerful, batteries-included languages that are faster than Python. So I expect with time, large parts will be rewritten. However, the area related to scientific computing will stay with Python, just like Fortran programs continue to be used today.

Re:Why people in Google hate Go? by jkbr on Friday November 03, 2023 @07:35AM (#38127217)
I don’t know when you last tested the start-up time, but we significantly improved it in HTTPie CLI 3.0 [0]. Now it’s still slower by ~0.1s.

    $ time http --version
    3.2.2

    real 0m0.113s
    user 0m0.087s
    sys 0m0.020s



    $ time xh --version
    xh 0.18.0
    -native-tls +rustls

    real 0m0.007s
    user 0m0.002s
    sys 0m0.002s

[0] https://httpie.io/blog/httpie-3.0.0#speed-ups
Re:Why people in Google hate Go? by jiripospisil on Friday November 03, 2023 @08:11AM (#38127537)
> Now it’s still slower by ~0.1s

Not for me. Printing HTTPie's version takes longer than to finish a real http request with xh. I suspect it's because I'm testing it on a relatively old server where the differences are even more pronounced.

https://gist.github.com/jiripospisil/d0de1355d534a19af2334de...

I'm using HTTPie 3.2.1 because Arch doesn't have the latest version available but based on the release notes that shouldn't make a difference.

Re:Why people in Google hate Go? by jkbr on Friday November 03, 2023 @09:51AM (#38128756)
Gotcha. Would you mind checking if you happen to have PyOpenSSL installed inside the Python environment HTTPie runs from?
Re:Why people in Google hate Go? by jiripospisil on Friday November 03, 2023 @10:23AM (#38129190)
I did not have it installed. Installing it did not make a difference. If it's of any help, here's a profile generated using cProfile. https://gist.github.com/jiripospisil/d492f67453d4aa8723432aa...
Re:Why people in Google hate Go? by jkbr on Friday November 03, 2023 @10:24AM (#38129228)
Thanks!
Re:Why people in Google hate Go? by amelius on Friday November 03, 2023 @08:28AM (#38127710)
Python is not a good comparison. It's improving but its runtime system is very slow compared to a modern concurrent GCed system.
Re:Why people in Google hate Go? by jjgreen on Friday November 03, 2023 @07:03AM (#38126933)
As fast as C but with correctness, Rust kind-of owns that space (not a big fan personally).
Re:Why people in Google hate Go? by narinxas on Friday November 03, 2023 @07:07AM (#38126984)
what about Zig?

I think they're a strong contender... it's somehow simpler than Rust

then again the correctness guarantee may be weaker??

Re:Why people in Google hate Go? by pjmlp on Friday November 03, 2023 @07:08AM (#38126995)
Still no story for UAF, and the community is against shipping binary libraries.
Re:Why people in Google hate Go? by fallat on Friday November 03, 2023 @08:52AM (#38127957)
zig has less memory usage correctness guarantees but its type system is good too.
Re:Why people in Google hate Go? by usrbinbash on Friday November 03, 2023 @07:17AM (#38127077)
> Rust kind-of owns that space

True. But it's a pretty small space to be in. And there are good reasons for that:

a) The only correctness Rust can, mostly, guarantee, is that there won't be unexpected data races or memory bugs. While this is proudly announced often and loudly, it also isn't the most common problem in code...logic bugs...against which the rust compiler can do as little as any other language.

b) Rust can only give these guarantees because it is ALOT more complex than C. That means harder to read, harder to write, harder to learn. And developer time matters. Alot. If I can already ship features, while my competition is still stuck in onboarding, it won't matter if my code has the odd memory bugs...those can be fixed...I will already have the market to myself.

Re:Why people in Google hate Go? by rapsey on Friday November 03, 2023 @07:23AM (#38127120)
> a) The only correctness Rust can, mostly, guarantee, is that there won't be unexpected data races or memory bugs. While this is proudly announced often and loudly, it also isn't the most common problem in code...logic bugs...against which the rust compiler can do as little as any other language.

A powerful type system helps quite a lot with logic bugs actually.

Re:Why people in Google hate Go? by usrbinbash on Friday November 03, 2023 @07:25AM (#38127139)
> A strong type system helps quite a lot with logic bugs actually.

A static type system does, and all the languages that Rust has to compete with in its space, have one.

Re:Why people in Google hate Go? by rapsey on Friday November 03, 2023 @07:29AM (#38127165)
Go's type system is much less expressive and it has null pointers. An entire giant class of bugs.
Re:Why people in Google hate Go? by usrbinbash on Friday November 03, 2023 @07:45AM (#38127299)
> Go's type system is much less expressive

Please, do explain: what does "much less expressive" mean, in technical terms? What specific data modeling can I not do in Go, and what specific bugs can be caused by that?

> and it has null pointers

Yes, so? De-Referencing a null pointer in Go crashes the program, making the bug very obvious. Go made the choice to have null pointers (which do exist in silica), and avoid the complexity of languages who pretend that null pointers don't exist.

It's a tradeoff, and a very good one at that.

Re:Why people in Google hate Go? by rapsey on Friday November 03, 2023 @08:25AM (#38127681)
> Please, do explain: what does "much less expressive" mean, in technical terms? What specific data modeling can I not do in Go, and what specific bugs can be caused by that?

> Yes, so? De-Referencing a null pointer in Go crashes the program, making the bug very obvious.

At runtime. i.e. production. You think that is just as good as solving the problem at compile time? I certainly don't.

Re:Why people in Google hate Go? by usrbinbash on Friday November 03, 2023 @09:29AM (#38128435)
> At runtime. i.e. production.

At runtime, i.e. initial testing, pre-commit-checks, integration-testing, QA and then production, yes.

So there are a lot of checkpoints where the system can crash before it ever goes live.

> You think that is just as good as solving the problem at compile time?

No, I don't, and I never wrote that I do.

I do think that it's a lot better than not crashing when dereferencing a null pointer, and instead doing god-knows-what, which is a problem in older languages, and a source of hard to track bugs.

And I rather fail early and with a clear signal in production, than have a language be much more complicated by "virtue" of pretending that void pointers don't exist. Because the former will sometimes crash in testing, and maybe maybe maybe in production here and there. The latter will always incur a higher cost in developer time.

Re:Why people in Google hate Go? by rapsey on Friday November 03, 2023 @11:32AM (#38130343)
The higher cost in developer time is a myth. Because the type checking seriously helps you out when you are changing existing code and it results in much fewer bugs out of the gate.

Sure the language in its totality is more complex. At least compared to Go or C. But nothing is forcing you to use every feature of it.

Re:Why people in Google hate Go? by usrbinbash on Friday November 03, 2023 @12:26PM (#38131029)
> The higher cost in developer time is a myth.

And yet, Go is a huge success in the industry, and one of the main reasons often given for chosing Go over a competing language, is how easy it is to get things started, how easy it makes the onboarding process, and how accessible and maintainable the code is.

> the type checking seriously helps you out when you are changing existing code

If you have Algebraic Datatypes in your codebase, which is not a given. Having a simple, easy to read language helps me out ALL THE TIME.

> But nothing is forcing you to use every feature of it.

And nothing forces C developers to use so many macros that their libraries resemble a completely different language where everything I thought I learned about C flies out the window. Nothing forces Python devs to use nested dictionary-comprehensions, that are, ironically, completely incomprehensible. Nothing forces C++ developers to use generics everywhere, regardless of whether they are actually needed or not.

And yet, that is, unfortunately, what is often happening in the wild.

The point here is; If a language offers X, then X will be used. And it will be used in smart ways, it will be used in unnecessary ways, and it will be used in not-so-smart ways. It will be used when it makes sense, and when it absolutely doesn't.

The thing the developers of Go figured out, and which, in hindsight, is surprisingly obvious, is that there is exactly one, and only one, foolproof way to prevent that from happening: By not having X in the language.

Re:Why people in Google hate Go? by biorach on Friday November 03, 2023 @01:11PM (#38131768)
You're a zealot and your comment is a polemic, not any kind of reasoned discussion of the advantages and disadvantages of one language as against another.
Re:Why people in Google hate Go? by usrbinbash on Saturday November 04, 2023 @11:14AM (#38141791)
This isn't a discussion about the advantages or disadvantages of languages.

This is a discussion about whether Go "misses" things, or "lacks" things, or if it's designed to not have these things, and if there is a reason why that is.

I have demonstrated, and provided arguments, for why the latter is the case. Aka. the exact opposite of "polemic".

Re:Why people in Google hate Go? by rapsey on Friday November 03, 2023 @02:56PM (#38133304)
> And yet, Go is a huge success in the industry

Success of a technology is more often than not dependent on who is behind it. Anything by google will likely see a lot of uptake.

Every language has a story. Some of it is bull some not. Best to try and be objective and not drink every drop of the koolaid.

Re:Why people in Google hate Go? by usrbinbash on Saturday November 04, 2023 @11:13AM (#38141780)
> Anything by google will likely see a lot of uptake

Disagree.

https://www.failory.com/blog/google-failed-products

Re:Why people in Google hate Go? by biorach on Friday November 03, 2023 @08:00AM (#38127424)
> what does "much less expressive" mean, in technical terms? What specific data modeling can I not do in Go, and what specific bugs can be caused by that?

This is a good illustration of how to model data using Rust's type system in a way that gives you compile-time guarantees of correct behavior:

https://docs.rust-embedded.org/book/static-guarantees/state-...

> Because we are enforcing our design constraints entirely at compile time, this incurs no runtime cost. It is impossible to set an output mode when you have a pin in an input mode. Instead, you must walk through the states by converting it to an output pin, and then setting the output mode. Because of this, there is no runtime penalty due to checking the current state before executing a function.

> Also, because these states are enforced by the type system, there is no longer room for errors by consumers of this interface. If they try to perform an illegal state transition, the code will not compile!

Re:Why people in Google hate Go? by herbstein on Friday November 03, 2023 @07:50AM (#38127342)
> What specific data modeling can I not do in Go

You're getting into the Turing tar-pit. There's nothing you can do in Rust you can't also do in Go, technically. Hell, you can do it all in Brainfuck too, if you so desire.

The big thing, though, is ADTs. Being able to say "the value is one of 3 possible values" is a lot easier than saying "here are three values, you should use the non-zero one".

Re:Why people in Google hate Go? by usrbinbash on Friday November 03, 2023 @07:58AM (#38127402)
> You're getting into the Turing tar-pit.

I am fully aware of that. My question is, what specific technical problems are caused by Go not having {feature_goes_here}.

> The big thing, though, is ADTs

Except it isn't a big thing, because for the few use cases where an ADT is actually, really, really, REALLY required, they can be expressed in Go using existing language features.

https://go.dev/doc/faq#variant_types

https://eli.thegreenplace.net/2018/go-and-algebraic-data-typ...

Quote: "It seems that Go can do just fine without adding variant types, due to the challenges mentioned in the beginning of the post and the ease with which the major use-cases can be implemented using existing language features." End Quote

On the one hand, yes, this is more verbose. On the other hand, these use cases are simply not frequent enough to justify making the languages syntax and type system more complex.

Again: Yes, Go lacks many features of other languages. That is on purpose. The language is made to be simple, as in "easy to learn, easy to read, easy to refactor, easy to generate, easy to maintain large bodies of code".

Re:Why people in Google hate Go? by EnergyAmy on Friday November 03, 2023 @10:24AM (#38129222)
That link shows the Go type system's lack of expressiveness. You have to manually include things like the default case. Rust's compiler will do exhaustiveness checking for you, and you can't just forget about it.

Also, it's not about ADT's being required. They're preferred, and Go's type system suffers for their lack. Go is a living, breathing example of the blub paradox in action.

Re:Why people in Google hate Go? by usrbinbash on Friday November 03, 2023 @11:00AM (#38129813)
> That link shows the Go type system's lack of expressiveness.

And I ask again what that is supposed to mean in technical terms, and what specific problems would be prevented if Go's type system was "more expressive".

> They're preferred

I am fully aware that for every given language feature, there are people who prefer that feature. And many languages reacted to that by including everything and the kitchen sink. That made many languages very "expressive", but that expressiveness comes at a cost: It also made the languages themselves become bigger and more complex.

Go isn't about having as many features as possible though. Quite the opposite, it's about having as many features as necessary, and as few as possible. Why? Because it keeps the language small and easy to learn and the code easy to read and maintain.

And to me (and judging by the sucess of Go I am not alone in this), that is a lot more important than a bit more "expressiveness" in things that one may come across every now and then.

Re:Why people in Google hate Go? by EnergyAmy on Friday November 03, 2023 @11:14AM (#38130040)
What it means in technical terms is what I just told you: Rust's compiler will not let you forget to handle an enum variant. Go's compiler can't do that because the type system can't handle it.
Re:Why people in Google hate Go? by usrbinbash on Friday November 03, 2023 @12:12PM (#38130838)
> Go's compiler can't do that because the type system can't handle it

Correct. And that isn't a disdvantage.

The fact that Go's type system "cannot handle that" directly in it's type system (functionally, the language itself can handle that easily enough, as shown by the article I linked above) is a choice, which results in a simpler language.

And I still haven't seen any specific problems that would be prevented if Go included this feature directly in the type system. I have, however, seen a lot of extra syntax that Go doesn't need to support in its compiler, Go students don't have to learn, and Go devs don't have to worry about.

Re:Why people in Google hate Go? by EnergyAmy on Friday November 03, 2023 @01:17PM (#38131861)
> specific problems that would be prevented if Go included this feature directly in the type system

I keep telling you the specific problem that would be prevented. You can't forget to handle an enum variant. That is a specific problem that is prevented in Rust, but not Go. And no, the language doesn't "handle that easily enough".

Update an enum in Rust with a new variant? Your code won't compile until you've updated everywhere that matches against it. Do something similar using the technique you linked in Go? Good luck, hope you don't introduce any bugs by forgetting to handle it somewhere.

Re:Why people in Google hate Go? by usrbinbash on Friday November 03, 2023 @02:11PM (#38132653)
> And no, the language doesn't "handle that easily enough".

Yes, the language handles it easily enough. ADTs, despite being the single most used example of "what Go doesn't have" since the language got generics, are not very common outside of the ML-derived-language world.

If they occur at all, they are usually used in a few very specific places. An example are AST types that are used in exactly the part of the parser handling that type.

Re:Why people in Google hate Go? by EnergyAmy on Friday November 03, 2023 @05:00PM (#38134942)
They're used all over the place where they're available. More languages are incorporating them exactly because of how useful they are.

I expect much like generics, we'll get some new version of Go eventually that half-asses ADTs, with much fanfare celebrating how they were totally always going to do it, they just needed to perfect it.

Re:Why people in Google hate Go? by usrbinbash on Saturday November 04, 2023 @04:07AM (#38139035)
> More languages are incorporating them exactly because of how useful they are

No, more languages are incorporating them, because most languages operate under the assumption that "more-is-better" is a good design maxime, also known as the "everything-and-the-kitchen-sink" method.

Resulting in exactly the opposite of what Go is, with extreme success, doing.

Fun fact: That methodology in other langages is what made Go's success possible in the first place.

> I expect much like generics, we'll get some new version of Go eventually

I expect the exact opposite, precisely because of generics. Because it has been some time now since they were implemented, and lo and behold: They are rarely used in most codebases, because as it turns out, the people saying "Outside of some collection-types, generics are almost never required" were right in the first place.

Re:Why people in Google hate Go? by derekperkins on Saturday November 04, 2023 @12:15AM (#38138079)
Easily handled by adding a linter. Like you pointed out, that's an easy place to make mistakes, and this regularly catches them for us https://github.com/nishanths/exhaustive
Re:Why people in Google hate Go? by rapsey on Friday November 03, 2023 @07:11AM (#38127019)
I went from Erlang to Rust and frankly I would not say Erlang is more productive, despite being a very high level language. When building a non-trivial system one should think about total cost of ownership.

A Rust program is by default going to be CPU and memory efficient. It is not likely to negatively surprise you in production with weird bottlenecks and unexpected behavior.

The time invested in producing a solution which is statically typed, pays of in spades when it is time to refactor or change something (which is pretty damn often if it is your product). Refactoring a Python/Erlang/Elixir/C/PHP solution is a major PITA and fraught with new bugs.

The time spent optimizing solutions in high level languages when they are falling on their face in production is generally ignored and extremely common. You do not have to be github to face performance problems in Ruby.

Re:Why people in Google hate Go? by ignoramous on Friday November 03, 2023 @06:54AM (#38126849)
This talk by Rob Pike answers some of your questions: https://go.dev/talks/2012/splash.article
Re:Why people in Google hate Go? by usrbinbash on Friday November 03, 2023 @07:08AM (#38126990)
> so not really suited for performance critical stuff.

What "stuff" is that exactly? Because Go is designed primarily for backend services and microservices. Considering how much backend software is powered by Python, Java, or *retching sounds* PHP, I highly doubt that is a major consideration in that area.

And even when performance actually does matter to an extend where it becomes a more pressing issue than network latency, Go code performs incredibly well and is more than a match for most requirements.

> No OO

How do you figure? I can write in a completely object oriented style in Go. Also, OO is not a prerequisite for large complex systems, and quite often strict adherence to it can make code much harder to maintain than it needs to be. Maintaining large complex systems requires, first and foremost, code that is easy to grok and maintain. And regarding that particular area, Go runs circles around any major contemporary language, including Python.

> It seems that its popularity exceeds its scope

Considering how widespread it is by now, I highly doubt that.

Re:Why people in Google hate Go? by lm28469 on Friday November 03, 2023 @07:14AM (#38127052)
It's really nice to use though, I never liked python and its environment, coming from C go feels like home to me, it's simple and it just works. I never had headaches to setup and run things like I had with python and js.

Performance is good enough for most jobs, we're not all working on the bleeding edge, a lot of jobs are more akin to code monkeying basic CRUD

Re:Why people in Google hate Go? by pjmlp on Friday November 03, 2023 @07:07AM (#38126980)
Docker (originally written in Java until Go advocates took over), and k8s are what made it popular.

Now it is kind of unavoidable in DevOps space for some cenarios.

My only complaint is their approach to language design.

Inferno with Limbo, Android, Windows Phone, show that there is GC hate, and shipping products to millions of users.

Re:Why people in Google hate Go? by elp on Friday November 03, 2023 @08:35AM (#38127807)
If Docker was in Java it would have been still born / Java universe only.

I don't get the GC hate. If its done properly (like Go) its invisible for 99% of applications and dramatically simplifies things like business logic that don't need to be that complicated or fast.

The real culprit is usually Java's slow startup and memory bloat from the JVM.

Re:Why people in Google hate Go? by pjmlp on Friday November 03, 2023 @10:11AM (#38129014)
Nah, that is what anti-Java folks wish for.

Java is so bad that Kubernetes + WASM containers is basically redoing application servers 20 years later.

Re:Why people in Google hate Go? by k__ on Friday November 03, 2023 @06:53AM (#38126843)
K8s is it's lifeline.
Re:Why people in Google hate Go? by cultavix on Friday November 03, 2023 @07:01AM (#38126912)
Exactly. This is exactly my thought, my only reason for learning Go Lang at all, was/is because of Kubernetes and much of the tooling around it.
Re:Why people in Google hate Go? by jjgreen on Friday November 03, 2023 @07:05AM (#38126953)
Interesting -- thanks for that
Re:Why people in Google hate Go? by ecmascript on Friday November 03, 2023 @06:54AM (#38126847)
I don't use Go since it's from Google but I wouldn't say that Go / Java can't be used for performance critical stuff?

There are a lot of values that goes into "performance critical stuff". For me, it can mean a chat app / money transfers etc that is performance critical but is is of course not as critical as in flight software or other system control software where GC could mean deaths.

Re:Why people in Google hate Go? by jjgreen on Friday November 03, 2023 @06:59AM (#38126898)
I meant speed-critical by that, sorry if that was unclear. I see opinions like "1/3 the speed of C" bandied around, not bad but means a big model run takes three days rather than one.
Re:Why people in Google hate Go? by pjmlp on Friday November 03, 2023 @07:09AM (#38127003)
Are weapon targeting systems and battleships speed critical enough?

https://www.ptc.com/en/products/developer-tools/perc

Re:Why people in Google hate Go? by dagw on Friday November 03, 2023 @08:14AM (#38127559)
"1/3 the speed of C"

Of course C can be is 1/3 of the speed of C, if the C is written by two different people. An average Go programmer might very well produce faster code than an average C programmer, if Go has better tools for doing normal things fast in an easy and obvious way

Re:Why people in Google hate Go? by dirteater_ on Friday November 03, 2023 @06:56AM (#38126865)
No OO?
Re:Why people in Google hate Go? by usrnm on Friday November 03, 2023 @07:02AM (#38126927)
Go is basically a very specialized language for writing small network services that are supposed to run on Linux. If this isn't your use case, then don't use go, but if it is, then golang is nice. Mostly the runtime and tools, not the language itself, though
Re:Why people in Google hate Go? by mauvia on Friday November 03, 2023 @08:20AM (#38127625)
IME people recommended it for being more batteries-included in terms of webservice stuff and some multithreading/scaling stuff, as well as having multiplatform support and libraries being compiled into the executable.

The language also seems to be built for the kind of people who think C has no downsides and everyone should write everything as explicitly as possible, which are an audience that normally doesn't get aimed at.

Re:Why people in Google hate Go? by bitshiftfaced on Friday November 03, 2023 @10:03AM (#38128918)
> No OO

Are you referring to Object Oriented programming? And if so, why not?

Re:Why people in Google hate Go? by ryandvm on Friday November 03, 2023 @10:24AM (#38129223)
Go is:

* Easier/safer than C

* Less dangerous than Javascript (statically typed and a good standard library)

* Much faster than Python

I think it's an excellent middle ground, compromise language. It's the centrist candidate of programming languages. Not the best at anything, but on average better than most.

Re:Why people in Google hate Go? by scruple on Friday November 03, 2023 @10:36AM (#38129457)
I'd add that it also ships with an incredible toolset alongside the installation, has a fully featured standard library, cross compiling is typically painless, and you get a single binary executable out the other side.
Re:Why people in Google hate Go? by Fire-Dragon-DoL on Friday November 03, 2023 @11:09AM (#38129954)
You just cited C, how's not having oop a requirement for big apps?

Also, unless inheritance is what you mean by oop, it supports the other usecases of oop

Re:Why people in Google hate Go? by conor- on Friday November 03, 2023 @12:30PM (#38131082)
> So for smaller not-performance-critical programs, why not Python, Typescript etc?

I can compile my go application down to a single, static binary that can run in a distroless container. The packaging/deployment simplicity of Golang appeals to me much more than Python, TypeScript, etc.

Also the developer tooling is first class and sustained backwards compatibility is top-notch. I can pretty much always upgrade the version of Go 1.x I target and have 0 worries in the world. Meanwhile in Python and JS land, the dependency management problems are a nightmare.