News for hackers. Stuff that matters.
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.