Re:If Java Is Dying, It Sure Looks Awfully Healthy
by RivieraKid on Thursday October 10, 2013 @06:16AM
(#6526650)
> The development experience may not be as great as when using Java
Exactly. I'm pretty sure that switching to something like Scala wouldn't improve my productivity.
Re:If Java Is Dying, It Sure Looks Awfully Healthy
by bad_user on Thursday October 10, 2013 @08:20AM
(#6527016)
We've got a parable in our country about a lazy bastard, that couldn't do anything out of laziness to the point of dying from hunger. One day a woman offers to help him, to give him shelter and food. To which the lazy man asks in response ... will you soak my bread? (sounds much better in Romanian)
Fuck dude. You're a developer. If you want productivity, make shit happen.
Re:If Java Is Dying, It Sure Looks Awfully Healthy
by RivieraKid on Thursday October 10, 2013 @06:55PM
(#6530533)
wtf?
Re:If Java Is Dying, It Sure Looks Awfully Healthy
by James_Duval on Friday October 11, 2013 @07:43AM
(#6532468)
I think that they are saying that Scala is the proverbial bread being offered to you, and your concerns about productivity are akin to insisting that your bread be soaked so that it's easy to eat.
If that is what they're saying, I disagree with them.
iOS doesn't force you to use Objective-C either. For example many top games or apps have been built in C#, by means of Unity or MonoTouch. The problem with iOS is Apple's developer agreement, as they first didn't allow apps written in anything else than Obj-C, after which they changed that to not allowing apps doing JIT compilation, but now they only enforce this rule when banning apps that download and execute code on the fly. For this reason, when embedding a WebView inside an app, Javascript will not have the same performance as Safari's Javascript engine, which is kind of stupid. So many devs prefer native compilation to avoid any problems. There's nothing wrong with iOS as a platform, what's wrong is with Apple's restrictive policies.