Hey, that's not fair for ALGOL 68. It had sum types, pattern matching and everything-is-an-expression [1].

[1] https://dl.acm.org/citation.cfm?id=356671

I guess that's why Go is a subset :)

Although to be fair to Go, I don't think ALGOL 68 had a (slightly broken) implementation of CSP and HTTP/2.0 support in the standard library.

I see Javascript made it mainstream for all sort of clients and servers, Electron desktop apps made it to mainstream. So I remain skeptic to argument just because new features have been invented they are good or need to be implemented everywhere.

JavaScript enjoyed being the only option with regards to browser as platform.

Go is only inevitable for those that need to deal with Docker and Kubernetes, the NoSQL hype successors.

Been a fan of JS since before The Good Parts book. Used it server-side in Classic ASP, Netscape Server and a couple more obscure runtimes before Node.js.

Personally, I find Rust as more approachable and easier to wrap my head around opposed to Go. Though some of the syntax changes I don't like as much. Waiting on async/await to land in a couple months though.

No surprise there. Rust is most loved language in so many surveys. Most devs planning to learn in near future. Many say it will be polished and ready by next year. I personally feel it may be ready for general developers like linux desktop will be ready for general users next year.

I think it's already ready for a lot of use cases... though, I think baked in async/await will carry it across the line for many. It's good for low-level duties and even has some decent/good web server frameworks. The webassembly flow is better than a lot of tools as well. I think that there will be some work around nicer UI/UX tooling for graphical apps, but it's still very usable as it is.

I'm learning it now. The async / await stuff is great to have in the core, but isn't something that was otherwise holding me up from learning it.

I believe that after I fully integrate the Zen of Rust, that I will be writing multi-threaded programs with fewer bugs than I would in my alternative languages (C, C++, Go, Python, Lua).

The annoying things in Go that have accumulated in my mind over the last few years are all dealt with in a superior fashion in Rust today.

I'll still be using Go for some stuff at work, but I won't be starting personal projects in it, like I might have in the past.

I don't care about the features in the last 20 years if I'm able to do my job efficiently which Go as a language provides. Never wonder why those great academics languages with a ton of features are not adopted?

So now languages like Java, Swift, Kotlin are academic languages?

Java is like 25 years old, you know.

I know, but apparently it has too many academic features not worthy of Go's adoption.

If you don't care about literally decades of progress you're just a bad software developer.