Wednesday, September 11, 2013

XE5 Trial Download and Install Experience

I haven't received any SA emails, but XE5 is up and the trial is downloadable now, so go try it out folks.

I downloaded the trial and it installed and activated the trial flawlessly. The android stuff you need is all automatically installed, and even somewhat configured. (An emulator profile for XE5 is created, for example. Nice!)

A launch webinar is planned for Thursday September 12, go sign up now.

I haven't been able to test XE5 with my real Google Nexus 7 yet, because my wife is addicted to Scrabble, and I haven't got the heart to steal it from her. Tomorrow evening I will, however.

Tonight I just used the emulator, and I have to say, that the Android EMULATOR is a piece of crap, and that this is not Embarcadero's fault.  I have already long lamented the crappiness of the Android EMULATOR technology that comes in the Android SDK/NDK.   If you want to try this out, please please please save yourself some grief and just skip the damn emulator completely.

Also, the emulator appears not to properly implement OpenGL/ES, at least not on everybody's computers. It doesn't work at all on my windows 8 computer, which has a high end workstation graphics card.  That means I can't even launch a hello-world firemonkey-android app on my emulator.

I have the Android Studio (new Java toolset from google, based on IntelliJ IDEA), I have the classic Eclipse based Android stuff, and I have Delphi XE5 trial.  I have used the Android emulator with these two IDEs for a while now, and I find the speed absolutely atrocious, and I'm running on a quad-core Xeon box with a lot of RAM, and a very fast hard disk.    So, go get a real Android phone or tablet, before you even start playing with Android.  I recommend the Google Nexus 7.

Anyways, can I just say that I hate Java, and I hate the Android SDK and its intents and its intent filters, and its XML UI building system.

Am I ever excited that, without learning how to properly bean your proxy-factory-intent-filtered snicker-snacks and make them reverse-deionize in a co-variant fashion, while simultaneously generating your user interfaces in giant swaths of hand-coded, XML you could just .....

stick a damn button on a damn form, and run the damn thing. You know what I mean? Yeah.

Go Delphi.

Sorry if that makes me a troglodyte, but that's how I feel.


  1. You can have a look in the AVD manager, edit the profile Delphi created and add "GPU emulation" with value "yes" under hardware. Then you should have hardware acceleration.

    If you want an even faster emulation you should have a look at the Android simulator from Intel.

  2. Enable acceleration as jaenicke mentioned. Then the performance is not this bad at all. In general use a physical device agreed. That has never been very different since the early days. I developed some stuff in the emulator in order to investigate the programming model in Dalvik under Windows 32. Then the memory limits come in play.

    If you don't like Java, Android Dalvik is maybe not the best idea. Java is little strange especially concerning UI. That's true. Java's big advantage simply was the first alternative allowing to address Enterprise apps together with HTML. These days there was perl and PHP was far away from good and bad.

    It's about what you are used too. The XML based screen definition is comfortable for all those who are used to editors. Linux. Web developers also don't move away from what they are used to as well as certain threads I found - no way and no need for an Eclipse.

    It's your damned freedom to develop using whatever you like. Since there is no need to obey to any vendor in general ... Apple are Apple, Google are Google, Samsung are Samsung. They simply have to provide a path for everyone using their device. Apple will stay special. They are amazingly consistent at the moment, but when they shift they shift, whatever the cost maybe for the user or the developer.

    Question - Is the application deployed to the device performant.