Not logged in
Log in now
Create an account
Subscribe to LWN
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
PostgreSQL 9.3 beta: Federated databases and more
This isn't true at all.
> whatever its importance to the Android-app, corporate-drone, and web-framework markets. COBOL's public face is a model to emulate.
Might as well try to declare the same thing for Perl or C++ for all the accuracy of these statements.
I was missing one
Posted Oct 26, 2012 21:20 UTC (Fri) by man_ls (subscriber, #15091)
Actually, the worst bits of Java were corrected in Android: AWT, Swing and the stupid virtual machine with unbearable delays every few seconds. On Android Dalvik works under constrained memory resources (well, constrained for these days, but still) without noticeable delays (unless you do weird stuff) and with a nice sane graphical toolkit.
There is still the annoying verbosity:
Transmogrifier transmogrifier = new Transmogrifier();
At least Google doesn't insist on creating getters and setters for everything, or declaring all variables as final unless they are modified later on -- talk about doing compiler micro-optimizations by hand. The worst part is that companies may enforce these stupid recommendations believing they are doing themselves a favor.
As to the necessity of JVMs for ARM64, they are just that: a necessity for some situations. I am very unhappy with certain branches of the Spanish administration because they require Java for signing documents; when I install IcedTea it refuses to run on 64 bit JVMs. So I have to borrow my girlfriend's Windows XP netbook for a short while, which is embarrassing. Whew, I needed to vent that, thanks for being still there. Back to on-topic: any server which doesn't have a JVM will not be considered as "serious" to large segments of customers, so it is a hard requirement. Grandparent may not like it, but enterprise customers do like Java, and that has relevance for Free Software.
Posted Oct 26, 2012 22:31 UTC (Fri) by ncm (subscriber, #165)
On the other hand, I'm betting that when the first AArgh64 chips come out, if the code doesn't run right, the chips will be considered wrong, and they'll change the spec to match the code. That seems about equally likely to be good as bad. Probably the people doing the code generator should get in touch with any malcontents from the Aargh64 design team and see which of its choices ought to be overturned that way.
I do like that in the Dalvik execution model, your program must be prepared to be killed off at any moment, and to then jump up, Inspector Clouseau style, if anybody happens to look.
Posted Oct 27, 2012 10:45 UTC (Sat) by man_ls (subscriber, #15091)
I suppose that, if the JVM implementors have half a brain, they will just publish a preliminary version of the code pending a real processor; the JVM should get updated then and everyone will be happy. If that is not the case, well, you cannot blame the Java language for that.
Posted Nov 9, 2012 3:08 UTC (Fri) by HelloWorld (guest, #56129)
Posted Nov 9, 2012 11:13 UTC (Fri) by hummassa (subscriber, #307)
Posted Nov 9, 2012 22:20 UTC (Fri) by HelloWorld (guest, #56129)
Posted Oct 30, 2012 18:31 UTC (Tue) by gnu_andrew (subscriber, #49515)
Posted Oct 30, 2012 21:17 UTC (Tue) by man_ls (subscriber, #15091)
Posted Oct 30, 2012 21:37 UTC (Tue) by dlang (✭ supporter ✭, #313)
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds