3 ms·

Given your animosity towards Android and all things Google I'm really not surprised. I recently installed Android Studio on my Mac and was pleasantly surprised

Given your animosity towards Android and all things Google I'm really not surprised. I recently installed Android Studio on my Mac and was pleasantly surprised how well the IDE and emulator performed. This was in stark contrast to the pig that is Visual Studio that I installed on my PC that sprayed 30GB of data all over my SSD.

Nition 10y ago
Visual Studio is an old and bloated beast that predates Staya Nadella, but since he took the helm the Visual Studio Code[1] project has been underway, and it's worth checking out if you haven't. It's cross-platform and closer to Notepad++ or Sublime Text than Visual Studio, but with full IntelliSense. 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. [1] https://code.visualstudio.com https://code.visualstudio.com
pjmlp 10y ago
Not everyone has nice employers giving SSDs and I bet most likely 16GB. 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.
- fjrieiekd 10y ago
  The support library regresssions, oh god, this +1000000. It appears that the prevailing attitude is release first, then maybe fix based on developer complaints. Then there is the mess of manufacturer bugs, but that isn't strictly google's fault.

Nition 10y ago

Visual Studio is an old and bloated beast that predates Staya Nadella, but since he took the helm the Visual Studio Code[1] project has been underway, and it's worth checking out if you haven't. It's cross-platform and closer to Notepad++ or Sublime Text than Visual Studio, but with full IntelliSense. 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. [1] https://code.visualstudio.com https://code.visualstudio.com

pjmlp 10y ago

Not everyone has nice employers giving SSDs and I bet most likely 16GB. 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.

fjrieiekd 10y ago
The support library regresssions, oh god, this +1000000. It appears that the prevailing attitude is release first, then maybe fix based on developer complaints. Then there is the mess of manufacturer bugs, but that isn't strictly google's fault.