Coding for UWP (aka WinRT) is a pleasure compared with the Android chaos, specially having a common OS OO ABI for multiple languages and tools that don't feel permanently in alpha stage, regardless of the amount of PhDs able to game the hiring process.
I also have the latest Visual Studio Community Edition installed and it's "only" 1.25GB, but I don't have any extras installed, just the base plus some extensions.
On the other hand VS runs properly on a HDD with 8GB.
As for Android, since you only installed Studio for the first time, let me explain it how it goes:
- Data binding introduced at Google IO 2015, still doesn't work in all use cases;
- The new layout constraints introduced for Android N, are still work in progress. In some cases blueprints and actual UI get out of sync, crash or don't expose certain attributes;
- Between the Camera and Camera2 API, I am not sure which one is worse;
- During two years anyone using the NDK was left unsupported, only after InteliJ announced CLion, did Google announced it would add its plugins to Studio. It took two more years to finally have some decent support for the NDK;
- Which since the move to Gradle had only the ndk-build documented, with some information scattered around how to use the new unstable Gradle plugin, followed by another plugin on the stable Android. But actually the way forward is to use cmake;
- There is hardly a Support Library release that doesn't have regressions;
- The Java fork, that is increasingly causing friction with Java libraries;
- The Jack compiler still doesn't support all of the Android own tooling;
- Fragments and activities, oh well....
- Gradle execution speed measured in minutes;
- The deprecated API between releases;
- Hardware accelerated 2D actually depends on how the APIs are used;
Stopping here even though I could easy add a few additional ones, but any Android developer can happily add some more bullet points here.
Then there is the mess of manufacturer bugs, but that isn't strictly google's fault.
Android would be my preferred os, if it actually worked properly. Most lay people I know feel the same. A new Android device is a joy for the few months before it falls to pieces, then it's a necessary headache, much like windows was a decade ago.
If you dominate a market with a product no one loves, you better be a locked-in telecom. Otherwise, as Microsoft learned, your dominance may be surprisingly fragile.
>the problem is that the Android ecosystem is brutally fragmented.
Looks like Android now has company.
http://www.zdnet.com/article/ios-also-has-a-fragmentation-pr...