GNU/Linux is a huge mess itself. You have thousands of different minds with different ideas (most of them being hobbyists) all developing/contributing to an OS. The advantage M$, Apple and Berkeley all have over Linux/Linus is that they all have a group of engineers that accomplish things with a unified goal by goal basis.
This makes GNU/Linus very messy, not necessarily worse, just messy.
I some what agree with him (and yes, I have done/working on a few apps for personal use for my self). One of the problems is that Android deviates quite a lot from standard Java ME and Java SE. The lack good examples and documentation in the official Android API don't help either.
[citation][nom]kyeana[/nom]To my understanding, it is natively java (with an android specific api), but i have heard rumor that it does support compiling and running C(++). Don't hold me to that though.[/citation]
What you are talking about is probably the Android NDK which can create native ARM executables. The NDK does use of SOME C++ libraries,headers,etc.
I agree with him. I'm all for Android for the sole purpose of beating Apple's iOS to the ground and pissing all over it. But the GUI is FUUUUGLY. I never realized how unintuitive and sloppy and gets in some areas. HTC's Sense UI is a step in the right direction, much prettier, easier on the eyes and consistent for the most part. The stock camera app however is atrocious, the disgusting black liner around the viewing window is just so ugly. And the music app is hardly anything to be proud of. Andriod's UI needs an overhaul. Want to see a beautiful GUI, WebOS, that's where the shits at.
[citation][nom]bsbsbsbs[/nom]Less time crying, more time creating good apps Joe. You sound like me when I CBF working.[/citation]
he complains, they fix it, the next 10,000 awesome android apps are created twice as fast because its a nice platform.
shit dev platforms mean apps take longer to make. simple as that.
for instance: porting iphone to another c++ mobile platform, including Android once you've figured out the quirks, can take a matter of days. porting to windows phone 7 because they force you to use c#, takes literally months. its just stupid.
>> reminds me of Windows...as in, it's really flexible, agnostic, and developer-friendly, but also really sloppily designed."
Apple , as in:
it's really inflexible
Not Agnostic - defines that that god is knowable. and that is SJobs.
Not friendly to developers - use mac only. no mac - no developers.
Really beautifully designed - Apple standards only, no flash or other 3rd party tools allowed.
Android use's a customized version of Java VM for running its apps. It takes a hit on performance but the apps are device agnostic supposedly because the JVM does all the hardware interaction. Its usually a good idea to do this for the majority of apps, their not usually resource heavy. Now if your making an app that requires quite a bit of resources you might want to use the NDK which is kinda sorta C++, but that thing is horrendous and lacking many library's and functions that the dev community is used to. Google already said they've been trying to clean up the NDK and add more functionality to it. The show stopper there is the different phone manufactures tend to use different hardware so getting a unified driver / library base is a PITA.
I have to agree with him to an extent on this one. I installed the android sdk a couple months ago and took a stab at writing a basic app. I didn't care for it at all. I thought maybe it was just my dislike for java programming, but now that I think about it... it was just the way the sdk was set up, the documentation, the organization of the libraries. It was not that easy to work with and it did feel sloppy at times.
Compared to C# and the XNA framework (which is what I have been doing most of my programming in lately), XNA is leaps and bounds over the android sdk. Since WP7 will be utlizing XNA for app development, I'd have to say that developers may find it much easier working with WP7 than either android or apple.
What? No doubt the OS is a work in progress, and it definitely has it's quirks, but is he seriously implying that X Code is better than Eclipse for development??? I've worked with both, and X Code is a nightmare. Terrible.
Developing for Android is a lot, lot easier than for the iOS.
[citation][nom]Stryter[/nom]Compared to C# and the XNA framework, XNA is leaps and bounds over the android sdk. Since WP7 will be utlizing XNA for app development, I'd have to say that developers may find it much easier working with WP7 than either android or apple.[/citation]
this is very true, if you are starting from scratch, but not if you are porting. though, for performance critical things (like games) it remains to be seen if you can really get the level of performance that you can with native code. there are some very worrying things in the documentation about the lack of optimization. but as a dev platform, as you would expect from MS, WP7 is the nicest.
[citation][nom]rhangman[/nom]Maybe he should switch to Samsung's Bada OS? Android isn't the only Apple competitor.[/citation]
+1 on this. Bada is simple, just c/c++, no horrible java or objective C getting in the way. nice integrated eclipse IDE and simulator, definitely a go for your c++ coding needs. also, webOS looks promising on this front too. it should say something that Angry birds has been ported to WebOS before being ported to android.
Why does Android even need to use Java when all the devices use ARM anyway? Couldn't they just create a native code marketplace where each app would be a container with multiple binaries for each CPU platform? They could easily handle this in build tools (make all the necessary binaries on release build and package them).
It already works this way for Linux repositories (x86/x64/PPC/etc. branches).