|
Authored by: songmaster on Saturday, April 21 2012 @ 10:08 PM EDT |
Apparently (from a comment to an earlier post) the Dalvik converter dx will only
work properly with the original Sun Java Compiler (javac). It's something to do
with the specific streams of byte-code instructions that it emits which mean
that the output from other compilers won't necessarily convert properly.[ Reply to This | Parent | # ]
|
|
Authored by: scav on Sunday, April 22 2012 @ 06:28 AM EDT |
3) Not necessarily. You can use Scala instead, which is an
arguably superior language having full interoperability with
Java (or Harmony, or Android) classes but first-class
functions, value pattern matching, tuples, and type
inference. (If you know what these are, you know the extent
to which Java sucks for lacking them).
There are also other alternative Android development
languages.
You cannot imagine how delighted I was to find this out.
IMO, it's only inertia that is keeping Java relevant :D
---
The emperor, undaunted by overwhelming evidence that he had no clothes,
redoubled his siege of Antarctica to extort tribute from the penguins.[ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Sunday, April 22 2012 @ 09:37 AM EDT |
If the only involvement of Oracle's Java is that the javac compiler compiles
some x.java files into bytecode on a PC that has the JDK via the regular
licensed installation, then what can Oracle possibly claim Dalvik development
violates?
Oracle can't claim copyright to the bytecode files emitted by javac. They're a
translation, or at worst a derivative, of the source files the application
programmer wrote. What Google does with the bytecode files is up to Google.[ Reply to This | Parent | # ]
|
|
|
|
|