Codename One vs Xamarin and Gluon Mobile

[luiz...@gmail.com]

Good Morning! I would like to clarify some doubts about the future of codename one. I am following two projects, Xamarin is now open source and beyond ios and android supports windows phone also supports xml android and ios layout, however uses C # and I Particularly prefer java.

For that reason they the codename one and gluon mobile:
http://gluonhq.com/
arouse my interest, the problem is that neither the codename one gluon nor supports windows phone or the native layout.

you guys could take advantage of the Xamarin since now and open source?

[Shai Almog]

Gluon is dead as RoboVM is.
RoboVM never worked properly for FX and without it things will be worse as OpenJDK is an interpreter on iOS. Even discarding that FX has inherent unfixable problems on iOS, Adobe couldn't get Flash to work properly on iOS and those guys don't understand graphics/GPU nearly as well as Adobe did.

We do have a new Windows port, it's already open source although isn't in production yet: https://www.codenameone.com/blog/new-windows-port.html

Xamarin never supported Windows. That's visual studio. Their approach to mobile development is inherently flawed as it relies on a custom low level VM where they have to keep chasing the native platform rather than use its existing tools.

[Shai Almog]

https://forums.xamarin.com/discussion/55129/comparing-xamarin-to-other-cross-platfrom-frameworks-codename-one?

[imsp...@gmail.com]

Sorry but it dos not look like gluon is dead? Do you have any proof of your claim

[Shai Almog]

You took your time asking. Last time I expressed my opinion about Gluon a lunatic fanboy started harassing me and Codename One thru social media and became the only person I had to block everywhere. He even created an account with a fake name disparaging me on dzone just to post disparaging comments that are completely detached from reality.
I'd say he represents Gluon perfectly.

Dead doesn't mean everyone got the memo. Since the underlying technology is all but dead: https://www.codenameone.com/blog/should-oracle-spring-clean-javafx.html
There isn't much future.

RoboVM represented the peak of what's possible with the approach taken there. We explain here why it was inherently broken and why we chose not to use it when we had to replace our VM: https://github.com/codenameone/CodenameOne/tree/master/vm

When RoboVM died gluon had several options for VM and it picked the worse possible: build their own. That's a tower of babel of bad decisions...