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

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 576323
To read all comments associated with this story, please click here.
Dalvik, ART, ...
by Kochise on Thu 7th Nov 2013 10:15 UTC
Kochise
Member since:
2006-03-03

...it is *still* Java, though :/

Switching to Erlang would improve things, forcing everyone to message passing, concurrent processes with no semaphore/mutex, massive network parallelism, etc

Kochise

Reply Score: 1

RE: Dalvik, ART, ...
by ddc_ on Thu 7th Nov 2013 10:45 in reply to "Dalvik, ART, ..."
ddc_ Member since:
2006-12-05

Exactly. Still AOT compilation is a huge step forward.

Reply Parent Score: 3

RE[2]: Dalvik, ART, ...
by adkilla on Thu 7th Nov 2013 10:46 in reply to "RE: Dalvik, ART, ..."
adkilla Member since:
2005-07-07

AOT has been available for Java too. Check out the J9 and Jet JVMs.

Reply Parent Score: 3

RE: Dalvik, ART, ...
by adkilla on Thu 7th Nov 2013 10:45 in reply to "Dalvik, ART, ..."
adkilla Member since:
2005-07-07

I would rather use Scala.

Reply Parent Score: 2

RE[2]: Dalvik, ART, ...
by Shane on Thu 7th Nov 2013 12:04 in reply to "RE: Dalvik, ART, ..."
Shane Member since:
2005-07-06

+1 for Scala.

Reply Parent Score: 2

RE[2]: Dalvik, ART, ...
by moondevil on Thu 7th Nov 2013 17:13 in reply to "RE: Dalvik, ART, ..."
moondevil Member since:
2005-07-08

The problem is how to get the typical developer to use Scala, when they barely manage with more mainstream languages.

Reply Parent Score: 3

RE: Dalvik, ART, ...
by dragos.pop on Thu 7th Nov 2013 10:52 in reply to "Dalvik, ART, ..."
dragos.pop Member since:
2010-01-08

...it is *still* Java, though :/

Switching to Erlang would improve things, forcing everyone to message passing, concurrent processes with no semaphore/mutex, massive network parallelism, etc

Kochise



Well the programming language is still java, not the run-time.
Switching to Erlang would be disruptive and lower the number of developers.
Everybody has it's favorite programming language, and they have very good reasons to, but does it apply to others?
If I wore Google I would encourage people to develop alternative languages for there SDK.

Reply Parent Score: 5

RE: Dalvik, ART, ...
by BeamishBoy on Thu 7th Nov 2013 11:44 in reply to "Dalvik, ART, ..."
BeamishBoy Member since:
2010-10-27

...it is *still* Java, though :/

Switching to Erlang would improve things...


No it wouldn't. It would make things immeasurably worse.

Java's already got - in the form of Akka - all of the things you suggest Erlang brings to the table. You're equally free to develop Android apps in C#/F# if async is your thing.

Reply Parent Score: 4

RE: Dalvik, ART, ...
by mmrezaie on Thu 7th Nov 2013 14:09 in reply to "Dalvik, ART, ..."
mmrezaie Member since:
2006-05-09

Don't you think that's a little too early? I am not sure if developers are ready yet!

Reply Parent Score: 1

RE: Dalvik, ART, ...
by kristoph on Fri 8th Nov 2013 01:05 in reply to "Dalvik, ART, ..."
kristoph Member since:
2006-01-01

You need to remember that JVM/ART != Java the language. ART is AOT compiler that 'converts' bytecode into machine code. The bytecode can be generated by any compatible language.

Here is an Erlang implementation ...
https://github.com/trifork/erjang/wiki

Now go forth an built your Android apps in Erlang (or Smalltalk or Ruby or any number of other languages).

Reply Parent Score: 5

RE: Dalvik, ART, ...
by JAlexoid on Sun 10th Nov 2013 20:09 in reply to "Dalvik, ART, ..."
JAlexoid Member since:
2009-05-19

While Erlang and it's runtime have incredible design benefits, it's syntax is just plain auful.
I'd prefer Haskel.

Reply Parent Score: 3

RE[2]: Dalvik, ART, ...
by Dano on Sun 10th Nov 2013 23:52 in reply to "RE: Dalvik, ART, ..."
Dano Member since:
2006-01-22

I prefer interpreted Logo...really folks using weird languages as the backbone of a phone platform? I prefer .NET in reality.

Reply Parent Score: 2