Announcing .NET Core 2.0
I wish I had a better sense of where cross-platform desktop app platforms stood these days: Electron, Java, .NET, QT. All I hear are &quot;Eww, Electron is ridiculous, slow, heavy Web junk for desktop&quot;, &quot;Eww Java is blub, insecure, and half-abandoned by Oracle&quot;, &quot;Eww, .NET is Microsoft and unreliable for anything serious on non-MS OSes&quot;, &quot;Eww, by the time you pay the license, learn QT, learn the odd variant of C++, and manually deal with different bugs on every platform, you discover you would have been better off using the OS makers&#x27; preferred tech on each,&quot; and so on.<p>It&#x27;s hard to tell how much of this emotional reaction is due to current reality, how much is leftover from old experiences that are no longer relevant, how much is just language preference (not platform quality), etc.<p>I could just try them all, but my experience years ago was that the cross-platform tech, when it worked, made things easy at first, but that final 5% of your code was always trying to find hacks to do what no one had ever tried before--very time consuming and risky (no guarantee of success). So &quot;trying them all&quot; won&#x27;t really give me a true sense of where the technologies are in reality.<p>There&#x27;s no rush in my case, but I do wish I had a more realistic sense of what the various desktop dev technologies were like these days in case I ever go back to it.