9 ms·
I've only slightly dabbled in Android development: installing the SDK, IDE, build a "hello world", and run in an emulator. I've done a bit of old-school mobile
by wvenable 12y ago
I've only slightly dabbled in Android development: installing the SDK, IDE, build a "hello world", and run in an emulator. I've done a bit of old-school mobile development (Symbian, WinMobile) and I was very surprised how poor the emulation experience was for Android.
It looks like Microsoft might have a better Android emulation workflow than Google. What strange times!
- blinkingled 12y ago>It looks like Microsoft might have a better Android emulation workflow than Google. What strange times! Sure but keep in mind that Google has to produce an emulator that emulates ARM, MIPS and x86 and all of that has to work on Windows, Linux and Mac. Significantly different and tougher challenge!
- bravo22 12y agoAndroid apps are Java based. Google does not need to do what you just said.
- myko 12y agoAndroid's NDK supports much more than just Java
- bravo22 12y agoTrue but the vast majority of Android developers don't need to use NDK. Additionally the native part can run as x86 code. It doesn't need to be emulated.
- eropple 12y agoThis isn't true, as anybody who sees bugs on the iPhone that don't show up on the Simulator will be happy to tell you. You test on an emulator when you have the option because it's the hardware you're actually deploying against. And, again, Android does not run Java and characterizing it as such is ignorance of the environment involved.
- bravo22 12y ago... and the hardware can vary greatly from chipset to chipset and from phone to phone. There are a number of drivers that work directly with the underlying chip and hardware. You can never emulate that. The actual CPU (ARM, x86) is a small part of the overall emulation equation and almost inconsequential to uncovering these bugs you talk about. There will be bugs that will exist solely on the hardware. You can't replicate it unless you are fully replicating that hardware, with those system level drivers. IMHO, In the context of the app development what Apple did is the better way in this case.
- lnanek2 12y agoYes it does. Android includes the NDK as well as the SDK for writing native code (C, C++, etc.) which gives you ARM, etc. specific libraries you package in your app. Although it is pretty popular for people to drop Intel's lib houdini into faster x86 emulators like Genymotion to let them still use ARM games and Google Play Services.
- SixSigma 12y agoSounds like qemu
- blinkingled 12y agoThe Android emulator is qemu based - and it is hard to get qemu to emulate fast without acceleration on all OSes.
- SixSigma 12y agoI can't think of reasons for not accelerating it for development purposes.
- angersock 12y agoMicrosoft has, consistently, supported developers better than almost any other ecosystem. It's a walled garden, but it's well-kempt.
- bad_user 12y agoYeah, you know, if they wanted to support developers better, they would have turned Windows into a Unix, they would have made Visual Studio cross-platform, or at the very least they would have fixed that goddamn cmd.exe, which is like the worst CLI ever and they would have cared about web standards. I also find Visual Studio to be worse than IntelliJ IDEA (at least without IntelliJ Resharper that is) and in the past every time I did anything with .NET I was baffled to find out that I do not have access to source with one click, or that .NET doesn't have anything like Maven. At least now they are open-sourcing the CLR, the core library, ASP.NET, are making .NET cross-platform and made progress on the tooling, like with NuGet (still not close to what Maven does, but it's something). So I'm ready to forgive and forget, but lets not go overboard - only 2 years ago .NET and Windows felt like going back to 1998 ;-)
- angersock 12y agoSo, if you're still using cmd instead of PowerShell (which we are, sigh...), you deserve the misery. Why would turning Windows into a Unix have helped anyone? Pike and Plan9 tried to save Unix better then ten years ago, and nobody gave a shit. Also, why do you even want something like Maven? That's like bitching that Windows doesn't have autotools--or was that next on your list of complaints? Tell me about how the MSDN is less helpful than man pages. Tell me about how the Windows API is worse documented and more poorly designed than POSIX (lol). Tell me about how executables compiled on one Windows machine don't transport to other Windows machines easily. I'll stand by my statement, thank you very much.
- bad_user 12y ago> if you're still using cmd instead of PowerShell PowerShell is a shell, not a CLI, one starts PowerShell inside cmd.exe. > Why would turning Windows into a Unix have helped anyone? It helped OS X ;-) > Also, why do you even want something like Maven? Because you have to rely on Visual Studio for automating your build, testing and deployment process, it it's not doing a good job and again, is like going back to the nineties. > Tell me about how the MSDN is less helpful than man pages. Well, MSDN isn't competing with man pages, but with readily available source-code at the click of a button and with libraries documented like this one is - http://akka.io/ http://akka.io/ > Tell me about how executables compiled on one Windows machine don't transport to other Windows machines easily. Never had a problem with OS X. And on Linux, people automate the shit out of the build process so it isn't much of a problem, hence the need for tools ;-)
- rogerbinns 12y agoYou should realise that Android apps aren't like traditional apps. Regular apps including those for iOS have a single entry point (main or similar). An Android application is closer to a mashup. There is no main. Your manifest declares the various components provided, and a normal Android app combines both them and external ones together to provide whatever it is you intend for the user. For iOS Apple provides a simulator where your app is compiled against substantially similar APIs provided by the Mac host. That provides quick startup, debugging etc as iOS apps are islands. For Android a majority of the system has to be provided because your code could be inter-operating with numerous other components, hence the emulator approach they took.
- nailer 12y agoThere's nothing stopping Google from making HAXE work properly (it allegedly does now, but it practically does not) or just shipping genymotion, asides from they don't care enough to do so.
- cageface 12y agoRunning under ARM emulation the Android emulator is unusable, IMO. However, if you run x86 images and enable Intel's hardware extensions and CPU acceleration it's perfectly usable. Still not as nice as the iOS emulator but it's good enough to get the job done.