jgrant27

Plenty of rationalization of how java (the language) is "subjective for developers" in terms of productivity and happiness. From a non-engineer view though, let's be real : nobody ever got fired for picking java. This was just a decision made in favor of managers over the poor engineers that will have to deal with maintaining a large Java code base over time.

If you have used Rust in any real world capacity on actual projects you know that there are no "Little Books" when its comes to using Rust. An overly complex and unproductive language as much as C++.

    Most applications I tend to see don’t even use concurrency because they are so small and simple that they don’t need it.

Sorry but I just can't take your opinion of any language seriously or that you have much practical experience at all because of statements like this.

    Have you debugged.it ?

Debugging seems to be the author's coding philosophy which says it all.

    While I had over a decade of experience in other languages, such as Python, PHP, Java, etc. 
    I found it extremely difficult to wrap my head around Go.

This could be because the author's introduction to programming and most of their experience has been with some very problematic languages.

Maybe it's not Go that is a terrible language but just that the author is not a systems programmer who has worked with large code bases ?

Maybe, however the author has over 20 years of professional Lisp experience, there are interesting points made for anyone in that category. To be fair though, did you read the post ? The intended audience is much wider than you're assuming.

The irony of this is next level, after all Microsoft has been threatening innovation for decades.

This sounds more like their typical corporate propaganda to get workers back onto their campuses and under the whip of their middle-management class.

After using Rust for a few years professionally it's my take that people that really want to use it haven't had much experience with it on real world projects. It just doesn't live up to the hype that surrounds it.

The memory and CPU savings are negligible between Go and Rust in practice no matter what people might claim in theory. However, the side effects of making your team less productive by using Rust is a much higher price to pay than just running you Go service on more powerful hardware.

There are many other non-obvious problems with going to Rust that I won't get into here but they can be quite costly and invisible at first and impossible to fix later.

Simple is better. Stay with Go.