You could do something similar with a Java+C++ application on Android. The Java parts interface with the application apis via dalvik, while the native parts do the heavy lifting.
The Dalvik virtual machine that Android uses is just now starting to get JIT compilation features. It will be a lot more competitive with statically compiled code once JIT is in regular use and starts to mature.
Compare HotSpot to natively compiled code. Today it's very competitive in most cases and you can develop much faster in Java and produce cleaner, more error free applications in less time.
Right, that's why in python land there's one library to do something (if you're lucky).
But in Java land there's usually at least 5.
That's because there's only one way to do anything in Java. And Java is the only language you can use on the JVM. There are no python, ruby, implementations available for that platform
It can't be that large (hello python, no threads, no JIT, etc) and if you're running into all kinds of Java portability problems, you're doing something really, really wrong.
Would you mind posting some of the "portability" issues you're having?
Pros: Built on a mature, polished platform (Java) Nice language syntax Functionalish constructs are available Great parallel framework (actors) along with the functional aspects
Cons: No native AOT support IDE support is still newish
lol, sounds like someone who's never used any of them in production.
Prohint: There's a reason why Java is the most popular platform and language for huge, cross platform enterprise software. And it does involve portability.
So you're saying instead of playing on a platform where DRM is present, but not ubiquitous, you'd rather play where DRM is a fact of life because it's easier.
Slashdot Mirror
You could do something similar with a Java+C++ application on Android. The Java parts interface with the application apis via dalvik, while the native parts do the heavy lifting.
The Dalvik virtual machine that Android uses is just now starting to get JIT compilation features. It will be a lot more competitive with statically compiled code once JIT is in regular use and starts to mature.
Compare HotSpot to natively compiled code. Today it's very competitive in most cases and you can develop much faster in Java and produce cleaner, more error free applications in less time.
It works for these guys: http://www.google.com/
Maybe they'll hit it big someday and create a competitor to Android.
Well, this is Slashdot.
It's 99% retard.
Wow, you must be a really good programmer if you don't know the difference between search and replace and refactoring...
In Democratic People's Republic of Korea, computer back door removes you!
I love that Frank Zappa song!
J2ME was gimped, it isn't optimized well (which especially hurts games).
yeah but they don't work, GIL.
Now you just sound educated stupid.
In short: make your time.
Right, that's why in python land there's one library to do something (if you're lucky).
But in Java land there's usually at least 5.
That's because there's only one way to do anything in Java. And Java is the only language you can use on the JVM. There are no python, ruby, implementations available for that platform
Some of the functional nut jobs claim Scala isn't functional because it supports mutable objects, OO and other non functional features.
In any event, it's more of a compromise.
You're reallying use a dynamically typed, interpreted language with no multiprocessor support to run "huge massively-parallel scientific codes"?
You sir are a badass, a moron or a sadist. I'm not sure which.
oh right, I'm astroturfing.
Astroturfing for one open source development platform that I like, against another open source development platform that I like.
Good job pointing that out, you get a gold star.
It can't be that large (hello python, no threads, no JIT, etc) and if you're running into all kinds of Java portability problems, you're doing something really, really wrong.
Would you mind posting some of the "portability" issues you're having?
You keep telling yourself that.
Scala.
Pros:
Built on a mature, polished platform (Java)
Nice language syntax
Functionalish constructs are available
Great parallel framework (actors) along with the functional aspects
Cons:
No native AOT support
IDE support is still newish
D has proprietary dependencies?
lol, sounds like someone who's never used any of them in production.
Prohint: There's a reason why Java is the most popular platform and language for huge, cross platform enterprise software. And it does involve portability.
No doubt. And if you don't actively attempt to defend your trademarks... you can lose them.
So basically these fan devs picked a fight with Activision and put Activision's back up against a wall.
Very, very stupid on the developers part. I can't blame Activision at all.
He's probably Amish.
So you're saying instead of playing on a platform where DRM is present, but not ubiquitous, you'd rather play where DRM is a fact of life because it's easier.
God I hope you live in a 3rd world country.
Oh I think he's gonna have a tough time with that one.
Well Apple is calling it "MAGICAL."
I'd say glorified is an apt description.
A glorified ereader... without the epaper.