It seems you (as well as several other people) can only imagine a future with Haskell or Lisp syntax as if anything else is inferior. I find that to be foolish and immature.
Go was specifically designed to be a systems language, period. Lisp was never designed as so, and perhaps that is why its hardly used as a systems language today. Personally, I like Lisp, Haskell, and Python but I also know C is a great systems language even though its not perfect and its a bit passed its prime. Thus Go seems to be a good progression from the C/C++ family (I never really saw Java being a systems language but that's my opinion).
Anyway, I agree I think you're becoming a bit of a lisp snob. It might suit you to be a bit more open minded and objective. Even if you don't fully understand the design of Go, you should be able to understand that it was designed by people who have credible experience and skill in designing languages and systems. And sorry to spoil things for you, but the last thing I can imagine is Clojure being the next systems language.
Your post essentially is a brief comparison of a selection of fruits without much substance.
Lastly, here's a piece of advice:
"That's why I reserve the right to match the language to the problem, and even - often - to coordinate software written in several languages towards solving a single problem."
Well if it bothers you so much, you have the freedom/right to not use Python. Furthermore, I sense that the majority does not share your sickness. And I personally see your view a bit distorted, but that would be my view/opinion.
Yes, but when 100% uptime and fanatical support are key to your branding, even a little downtime undermines the expectations of current and prospective customers.
They set a high bar for themselves. By saying that they have the lowest downtime in the industry, more eyes are looking at them to see that they do as they say. That's what makes this such a nasty situation.
