> ll applications we all use on the client side are C/C++/ObjectC/web apps.
Not every company is the same.
Since when does Apple have server frameworks for Objective-C?
WebObjects was re-written in Java.
My current customer uses everything native, with web apps just for small CRUD maintenance tasks of a few DB systems.
> Visual Studio is C++
Visual Studio is a mix of C++ and .NET code, its UI infrastructure was completely rewritten in VS 2010.
> Even the Win10 startmenu is still a C++ application for performance reasons.
Have you seen the code? How sure are you that it isn't .NET Native?
> Even the Win8/10 calculator app has a loading splash screen,
Anyone that knows WP dev, knows those splash screens are optional.
> the FirefoxOS calc app starts faster.
Which is behind WP and BlackBerry in sales.
Speaking of Go, it's appearently commonly used for server side services/apps. Well the same can be said for Java and C#/F#/VBNet.
All applications we all use on the client side are C/C++/ObjectC/web apps. (exceptions are maybe Eclipse/IntelliJ, mind that Visual Studio is C++). Java on Android is an exception for legacy reasons (Google bought the Android company; and we pay the price buy using 2x-4x as powerful hardware (CPU cores & memory) comparing to iPhone to get similar UX & latency). Even the Win10 startmenu is still a C++ application for performance reasons. AOT is helpful for certain execution paths like JIT and isn't magic. Even the Win8/10 calculator app has a loading splash screen, the FirefoxOS calc app starts faster. XML based UI languages work, but aren't that great (e.g. resizing the Win10 startmenu isn't what I would call responsive design in comparision what we known from HTML5&CSS3).
Beside that you wrote a good comment above: https://news.ycombinator.com/item?id=10568915