I’m not saying you’re wrong, but there is real value in having one blessed package / dependency management system that everyone in an ecosystem uses. That’s one of my biggest complaints with the JavaScript community, there are 10 different tools to solve every problem and they change regularly.

I feel like the OP is a significantly better read than your reply.

One is a comment, the other is a blog article. I feel like the Financial Times is a significantly better read than your reply but making that comparison would be absurd.

You assert that it’s all been said before, but then later say that the post makes surprising and novel claims.

Of the valid criticisms of Go in the post (package management, lack of generics), there are literally thousands of well written and well informed articles describing the issues and possible solutions, the vast majority of them are better reads and more informative. These are very well known issues to anyone who has ever read about Go.

The complaint about code formatting is made regularly and dismissed by the vast majority of people, “Go can’t do X because it lacks inheritance” is wrong and occurs frequently enough to have a section in the official Go FAQ. Perhaps I should have written “Of the things the article doesn’t get entirely wrong, it says nothing which hasn’t been said a thousands times before”?

You decry subjective measures, but your entire reply has no meaningful backup for any of its arguments.

I’m not going to re-write what has been written thousands of times before on matters that have been discussed to death and which I can add nothing original. I could tear into almost everything written in the post, but I have better things to do (unlike you, perhaps?)

You state that there’s objectively wrong claims

The post claims: “Go forces me to maintain the same code in three different places.” because it lacks inheritance. This is objectively wrong. The author doesn’t seem to know about type composition, which as I said, would likely solve the issue he was describing.

The post claims: “The Go compiler is repressively enforcing a mix of Google’s C++ and Python style guidelines.” and proceeded to give examples of syntax errors which occur because the compiler has rules about where you put newlines. You can style Go however you want: you can can have (brackets) around if statements, you can end lines with semicolons, but it doesn’t need either of these things. You can do whatever you want if you follow the syntax, which isn’t that strict:

package main

func main() {
        if(1 + 1 == 2) { println("hello");
        } else if 1+5 == 6 {
                println("goodbye")
        } else {
                println("string" +
               "concatenation") }
}

That’s valid Go code. You’ll note, for example, the new line between concatenated strings, something the post claims isn’t allowed.

Most editors will run go fmt because it provides a consistent format for all Go code and is required by most Go projects before they will accept code. To claim that the compiler “repressively enforces” Google’s C++ and Python style guide because it uses newlines as part of the language syntax is wrong.

Frankly, your post is awful.

I’m glad you enjoyed it, but frankly I couldn’t care less what you thought of it. Perhaps you could trying adding to the discussion next time rather than simply criticising my response? There are a million ways you could have made the same points without framing it as an attack on my post, yet that’s all you did. Frankly, I find your attitude to be awful, but I wouldn’t have wasted time on it if it hadn’t been aimed at me.

I used SLED (SuSE Linux Enterprise Distribution) at a previous job, and it was pretty miserable. The system was slow, YaST was pretty buggy, etc… I haven’t tried OpenSuSE in years, though.

Lately, I’ve just been just been using Ubuntu server where I use Linux, installing my preferred window manager that way, and using ksplice to avoid rebooting on most kernel upgrades. Of course, I’m mostly on Thinkpads, which tend to be well supported. Of note, the past few kernels don’t boot on my C720 Chromebook, which runs Ubuntu natively and has no ChromeOS on it anymore. I’ve been running Fedora on a test machine at work, and it’s still throws me off (and yum is as slow as ever). I should also note that all of my machines have integrated graphics and don’t use the NVidia cards.

Ubuntu (gnome) has been very stable for me on my all-intel laptop - I’m not sure I’ve ever had it crash or fail to boot on me. The flip side to that is my desktop, which gets killed EVERY Kernel upgrade thanks to the nVidia drivers.