Linked by Thom Holwerda on Thu 7th Nov 2013 10:11 UTC, submitted by nej_simon

It's fair to say that Android went through some chaotic years in the beginning. The pace of development was frantic as the operating system grew at an unprecedented rate. An as-yet undetermined future led to decisions that were made to conform to existing hardware and architectures, the available development tools, and the basic need to ship working code on tight deadlines. Now that the OS has matured, the Android team has been giving more attention to some of the components that haven't aged quite as well. One of the oldest pieces of the Android puzzle is the Dalvik runtime, the software responsible for making most of your apps run. That's why Google's developers have been working for over 2 years on ART, a replacement for Dalvik that promises faster and more efficient execution, better battery life, and a more fluid experience.

This will be one of the defining changes in Android over the coming years. Android 5.0, perhaps?

Thread beginning with comment 576448
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Dalvik, ART, ...
by Shane on Fri 8th Nov 2013 02:12 UTC in reply to "RE[2]: Dalvik, ART, ..."
Member since:

Scala's main strength is that you can grow into it. Start with OOP, then move on to a more functional reactive style.

Reply Parent Score: 2

RE[4]: Dalvik, ART, ...
by moondevil on Fri 8th Nov 2013 07:54 in reply to "RE[3]: Dalvik, ART, ..."
moondevil Member since:

That is all fine and good when you have good developers on team.

I happen to have met a lot of them that still write code as if 48K BASIC was bleeding edge programming.

Reply Parent Score: 2

RE[4]: Dalvik, ART, ...
by snowbender on Fri 8th Nov 2013 08:02 in reply to "RE[3]: Dalvik, ART, ..."
snowbender Member since:

If you work on your own, that is a possibility. In most cases however, one will have to work with code that is written by other (possibly more advanced) people, and then the "typical developer" will get into trouble. Not to mention that I have my doubts about the "typical developer" growing into it.

It is my impression that the "typical developer" already has a lot of trouble with really understanding lambda expressions, C# LINQ and writing correctly working parallel code. Yes, 95% of C# developers actually use LINQ-to-objects all over their code. In my experience however, only a small percentage correctly knows/understands the semantics.

Now that I think about it... a lot of programmers do understand and "get" OOP, but only few can make a good OOP design and can apply good OOP principles to their code when they have to create something from scratch.

Edited 2013-11-08 08:05 UTC

Reply Parent Score: 4