News for hackers. Stuff that matters.
Re:Erlang Garbage Collection Details and Why It Matters (2015) by brudgers on Tuesday March 23, 2021 @11:00AM (#26555829)
Google is an enterprise. Go is an enterprise language. For the usual enterprise reasons: bean counting, internal politics, and cubicles.

It is a great language because it solves Google's problems. That's true of all Google tools and services. To the degree a person has the same problems as Google, their tools are great. Most people and organizations don't have Google's problems to a significant degree.

Re:Erlang Garbage Collection Details and Why It Matters (2015) by pjmlp on Tuesday March 23, 2021 @12:25PM (#26556857)
Python, TypeScript, COBOL, VB.NET, Java and C# are all enterprise languages, yet all of them are PhD level as per Go advocacy.
Re:Erlang Garbage Collection Details and Why It Matters (2015) by brudgers on Tuesday March 23, 2021 @12:40PM (#26557032)
Python is one of the problems Go addresses.

Three of the other languages are for Microsoft's Enterprise needs which significantly predate are distinct from Google's.

COBOL solves a problem Google doesn't have: producing code that a non-technical person can learn to read and understand. The general. The CEO.

Re:Erlang Garbage Collection Details and Why It Matters (2015) by pjmlp on Tuesday March 23, 2021 @01:32PM (#26557691)
Yet the majority of Google's problems are solved with Python, Java, Kotlin, and C++, not Go.

Go doesn't address any Python issue, besides AOT compilation, easily solved if PyPy had more community love.

Re:Erlang Garbage Collection Details and Why It Matters (2015) by throwaway894345 on Tuesday March 23, 2021 @04:21PM (#26559934)
> Yet the majority of Google's problems are solved with Python, Java, Kotlin, and C++, not Go.

That's not very informative... Google had millions of lines of code in Python, Java, and C++ before Go hit 1.0 (to the extent that Kotlin enjoys wide adoption inside Google, it could be explained by compatibility with existing Java code, especially the Android niche). It would be more interesting to look at Greenfield projects which don't depend on existing Google libraries, although even then Go would have to be quite a lot better than the competition in order to get a team with a long history of proficiency in Java to migrate to a new, relatively unproven language.

> Go doesn't address any Python issue, besides AOT compilation, easily solved if PyPy had more community love.

Are you suggesting that if PyPy had more investment it would become an AOT compiler rather than a JIT compiler? Anyway, "if only the community invested in it more" is like the whole problem with the Python ecosystem. If the community invested in solving package management, Python wouldn't have such an abysmal package management story. If the community invested in a smaller C extension interface, PyPy could be fast and compatible and CPython would be freer to optimize without worrying about breaking compatibility.

I've been working with Python professionally for ~15 years now and I'm pulling for it, but come on... The idea that Go is only better with respect to AOT (ignoring that AOT is not an end to itself) is out of touch with reality. Go is 2-3 orders of magnitude more performant than Python, it's statically typed (yes, mypy exists but it's still alpha quality and I'm happy to back up that assertion if necessary), it has a sane package management story (yes there are warts, but that's still far better than the Python package management story), documentation is much better in every respect (the tooling, the centralization, the readability, the accuracy, etc), etc. These aren't small things--I've seen projects fail for poor performance, and I've spent weeks trying to find a way to get fast, reproducible builds (before giving up).

There are certainly areas where Python bests Go (e.g., data science ecosystem, web frameworks, etc), but the idea that Go only has AOT over Python is absurd.

Re:Erlang Garbage Collection Details and Why It Matters (2015) by pjmlp on Tuesday March 23, 2021 @05:06PM (#26560406)
Had Docker not happened, and the Kubernetes team not gotten some new members that pushed for the Go rewrite from the original Java prototype, most likely we wouldn't be even talking about Go.
Re:Erlang Garbage Collection Details and Why It Matters (2015) by throwaway894345 on Tuesday March 23, 2021 @06:23PM (#26561090)
No doubt those are prominent applications in the Go ecosystem, and thus I can understand why people with little Go experience (or little experience circa 2012-2015) have this perception, Go was gaining momentum in the devops and network-services spaces before those apps came to fruition.

Personally, I started using it because it was the only language at the time that made it easy to build and deploy static binaries--I didn't have to learn a DSL to download and wire together a bunch of dependencies (nor run a flaky daemon in the background because the performance of the CLI is so poor) or cargo cult the incantation to package them into an archive or figure out how to make sure that my targets have compatible versions of the target runtime or etc. Similarly I didn't have to figure out how to wire together a third party testing library and integrate it into the build system. Similarly I didn't need to worry about packaging and hosting my libraries or documentation. I also didn't need to operate an external web server like uwsgi or jetty--Go's standard library has a production-quality HTTP server builtin (and its concurrency features made it fast and scalable). The language features were also a pretty big boon: it had value types, first class functions, type inference, "duck typed" interfaces, goroutines, etc and best of all: an ecosystem free from the pitfalls of OOP (inheritance, banana-gorilla-jungle architecture, etc).

Frankly, it's just an amazing little language. I do wish I could take its runtime, tooling, familiar syntax, etc and plug in a different type system, mostly one with rust-like enums and generics; however, the particulars of a static type system are relatively minor factors in the outcome of a given project.

Re:Erlang Garbage Collection Details and Why It Matters (2015) by pjmlp on Wednesday March 24, 2021 @06:54AM (#26565599)
Static binaries were invented when Fortran happened.
Re:Erlang Garbage Collection Details and Why It Matters (2015) by blacktriangle on Wednesday March 24, 2021 @12:07PM (#26569059)
At the time Go was getting started most software was either Java which had to coordinate with the JVM installation or scripting languages which required you to manage a bunch of packages. Static binaries was virtually a feature unique to go from the point of view of popular languages in the domain of web dev and dev ops.
Re:Erlang Garbage Collection Details and Why It Matters (2015) by throwaway894345 on Wednesday March 24, 2021 @08:57AM (#26566558)
Cool, but I don’t know what that has to do with anything.
Re:Erlang Garbage Collection Details and Why It Matters (2015) by pjmlp on Wednesday March 24, 2021 @10:57AM (#26568034)
> I started using it because it was the only language at the time that made it easy to build and deploy static binaries
Re:Erlang Garbage Collection Details and Why It Matters (2015) by throwaway894345 on Wednesday March 24, 2021 @12:24PM (#26569309)
"made it easy" != "invented". Anyway, it looks like this thread has devolved into banality, so I'll be ducking out.
Re:Erlang Garbage Collection Details and Why It Matters (2015) by pjmlp on Wednesday March 24, 2021 @05:14PM (#26573024)

   cc -static hello.c -o hello
So hard.
Re:Erlang Garbage Collection Details and Why It Matters (2015) by bsaul on Tuesday March 23, 2021 @11:47AM (#26556426)
"Most people and organizations don't have Google's problems to a significant degree"

Except in this particular case, i believe the average junior Googler is far more capable of handling advanced language as the average junior employee of any regular corp.

Which means go's tradeoff toward "simplicity" is probably the wisest for them as well.

Re:Erlang Garbage Collection Details and Why It Matters (2015) by waynesonfire on Tuesday March 23, 2021 @12:07PM (#26556655)
No, I'd argue that both are incapable, you can't teach experience. Junior Googlers are just more "dangerous" as they probably start their career on bigger problems and share with the average a similar set of "unknown unknowns".

Enterprise languages, like Java and Go (in contrast to Scala or Perl) are designed to keep people on rails. This can be accomplished by for example, limiting the number of ways a problem can be solved by the primitives of the language.

This is why the "most fast and break things" paradigm at Facebook didn't align with me. They basically announced that they're not concerned about these rails. Not to say it's a bad approach, FB is a very successful software company, just one that doesn't align with _my_ values. I think they've since moved away from this.

Re:Erlang Garbage Collection Details and Why It Matters (2015) by pjmlp on Tuesday March 23, 2021 @12:29PM (#26556894)
Except Go in 2021 is like Java in 2000, so a bit hard to put both on the same level.
Re:Erlang Garbage Collection Details and Why It Matters (2015) by throwaway894345 on Tuesday March 23, 2021 @04:32PM (#26560044)
I get that Go doesn't have generics and is generally in the C-family of languages, but beyond that there's not much to compare--I'm shocked that anyone would even make the assertion. Go has first class functions, value types, generic slice/hashmap/channels/etc, goroutines, and type inference, and it lacks inheritance and constructors. Those different feature sets predictably breed very different programming paradigms. Notably, I recall early Java was all about inheritance and distributing your object graph arbitrarily among constructors.
Re:Erlang Garbage Collection Details and Why It Matters (2015) by blacktriangle on Tuesday March 23, 2021 @11:54AM (#26556500)
Honestly I'd argue that that is more of a Google/large corporate problem. The thing about junior devs is that in order to hire a bunch of them and get anything productive out of them, you need a ton of people above them. You need to spend more time on design to give them more clear requirements, you need more senior devs to provide mentorship, you need more management.

Smaller dev shops don't have that, they can only bring on 1-2 juniors at a time and hope for the best.

Re:Erlang Garbage Collection Details and Why It Matters (2015) by brudgers on Tuesday March 23, 2021 @12:42PM (#26557057)
To a first approximation comparing junior developers broadly is analogous to comparing +0, 0, and -0.
Re:Erlang Garbage Collection Details and Why It Matters (2015) by warmwaffles on Tuesday March 23, 2021 @01:34PM (#26557720)
For very large values of 0