Feeds

Gaps blight JavaFX early promise

Sun repeats Swing mistakes

Internet Security Threat Report 2014

Many Will Groan

Many will groan, though, at the prospect of having to learn a whole new scripting language that isn't really based on anything. At least starting with the best bits of an existing language like JavaScript would have kept it familiar.

The quirkiness isn't just in the syntax. There are surprising side-effects to the declarative approach. For example, doing this:

var myScene = Scene {

    fill: myGradient

    content: bind stuff

}

 

Stage {

    title: "My Stage"

    width: 450

    height: 450

    scene: myScene

}

Is very different than doing this, which produces a blank window:

Stage {

    title: "My Stage"

    width: 450

    height: 450

    scene: myScene

}

 

var myScene = Scene {

    fill: myGradient

    content: bind stuff

}

This is compile time versus runtime: myScene is compiled in therefore available anywhere in the script, but at runtime, the script elements are executed from top to bottom, not when they're first referenced - except in the case of a timeline function or GUI event.

To me, this breaks the principle of least astonishment. It also raises some thorny questions about the order in which script elements are executed. For example, does the ordering of import statements matter? I can see this leading to insidious runtime issues in big projects where simply swapping two import statements around magically fixes (or further breaks) things.

Whither Swing?

With Sun's new golden child running around, the question is what's the future of Swing? Is it now legacy. Will Sun continue to prioritize it? Swing is highly pervasive, with millions of dollars of investment in projects inside banks and large organizations around the world.

For this important toolkit to be "mothballed" by Sun would be unthinkable (and yet there have been rumblings in that direction). While Sun hasn't categorically asserted that it will continue to develop Swing, your "legacy" Swing components will at least interoperate more or less seamlessly in your JavaFX scene graph.

And of course your Java classes can be called directly as well. JavaFX objects can implement Java interfaces, allowing you to reference them in your Java code - the code need not know that it has an alien entity in its midst.

For companies that decide to take the JavaFX route, this does at least mean that there's a fairly comfortable migration path. And the future of Swing seems fairly secure, at least for now.

Is JavaFX for you?

Regardless of who uses JavaFX, there is the worry that Sun has failed to recognize - or at least target - the real audience here. We're talking Visual Basic refugees and web developers who know a bit of JavaScript and who may be lured into trying JavaFX.

Another potential audience will be Swing refugees worried that their careers are about to hit a dead-end unless they move with the times. Also, there are developers who would like to use Java for a UI but are scared of Swing's complexity.

For any of these people, JavaFX will feel like a major step backwards until that mythical GUI editor is ready.

Then there are Adobe Flex and AIR developers. It's highly unlikely that this group will switch as long as they perceive Sun's offering as inferior. And currently, Flex offers a more compelling all-round platform and set of development tools. It could take a couple more releases for JavaFX to catch up.

The target audience may not be as technical as your standard Java developer. They'll expect a high level of integration, point and click development, and an easy way to download and install new UI components. Swing never had such a thing, and a third-party component market never emerged in the same way that it did for Visual Basic or Delphi.

Here's Sun's chance to get it right second time around: to create a searchable online marketplace with point-and-click install of third-party libraries and widgets. A component ecosystem. Once again, Sun is leaving this vital aspect of the product to pure chance, no doubt hoping that a charitable third-party somewhere will handle this for them.

For a 1.0 offering, there are some noticeable gaps. JavaFX for mobile is still nowhere in sight, there's still no GUI editor of course, and the Linux version isn't even appearing in the nightly builds yet.

But despite these concerns, the platform should have a bright future - as long as Sun can plug the gaps and bring the next update to market significantly faster than 1.0.

Matt Stephens co-authored Use Case Driven Object Modeling with UML: Theory and Practice, which illustrates how to create the ideal software design with Enterprise Architect, Spring Framework and JUnit.

Security for virtualized datacentres

More from The Register

next story
Microsoft WINDOWS 10: Seven ATE Nine. Or Eight did really
Windows NEIN skipped, tech preview due out on Wednesday
Business is back, baby! Hasta la VISTA, Win 8... Oh, yeah, Windows 9
Forget touchscreen millennials, Microsoft goes for mouse crowd
Apple: SO sorry for the iOS 8.0.1 UPDATE BUNGLE HORROR
Apple kills 'upgrade'. Hey, Microsoft. You sure you want to be like these guys?
ARM gives Internet of Things a piece of its mind – the Cortex-M7
32-bit core packs some DSP for VIP IoT CPU LOL
Microsoft on the Threshold of a new name for Windows next week
Rebranded OS reportedly set to be flung open by Redmond
Lotus Notes inventor Ozzie invents app to talk to people on your phone
Imagine that. Startup floats with voice collab app for Win iPhone
'Google is NOT the gatekeeper to the web, as some claim'
Plus: 'Pretty sure iOS 8.0.2 will just turn the iPhone into a fax machine'
prev story

Whitepapers

Forging a new future with identity relationship management
Learn about ForgeRock's next generation IRM platform and how it is designed to empower CEOS's and enterprises to engage with consumers.
Storage capacity and performance optimization at Mizuno USA
Mizuno USA turn to Tegile storage technology to solve both their SAN and backup issues.
The next step in data security
With recent increased privacy concerns and computers becoming more powerful, the chance of hackers being able to crack smaller-sized RSA keys increases.
Security for virtualized datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.
A strategic approach to identity relationship management
ForgeRock commissioned Forrester to evaluate companies’ IAM practices and requirements when it comes to customer-facing scenarios versus employee-facing ones.