- We design and build extraordinary applications for companies looking to make the next great idea a reality.
- learn more
JavaFX - Another Ajax Killer
Everyone is trying to kill Ajax. Apollo, Project Flair, Silverlight, on and on and on...but..Ajax...just...won't...die. Sun is giving it another try with it's JavaFX.
JavaFX Script takes advantage of the Java Runtime Environment's (JRE) ubiquity across devices and enables creative professionals to begin building applications based on their current knowledge base. It also uses Java technology's "write once, run anywhere" capability to help realize a future where consumers can access content whenever and wherever on any Java-powered device. JavaFX applications will run on JavaFX Mobile, Sun's software system for mobile devices also previewed at JavaOne, as well as desktop browsers (see separate announcement).
I think it must be something about Silicon Valley. I've been at enough events out there to know that people actually talk like this (as opposed to writing press releases like this). The doodoo gets especially deep around the time of JavaOne.
What is at the heart of JavaFX? A new scripting language "based on Java." Hmmmmm, dynamic languages good, statically typed languages bad. I guess when Richard Stallman embedded Lisp in GNU Emacs, he really started a trend.
Scripting is all the rage these days, with Groovy, BeanShell, Javascript and others filling an important niche. But I have to feel it's just a fad. There are good reasons to use statically typed languages, especially when developing large, complex systems over long periods of time. I just hope this doesn't mean we are going into a scripting craze ("We are so past Java and C#...") only to have the pendulum swing the other way ("We tried writing our system in Perl...never again. No scripting here.").
More on the bestiary of Ajax Killers later.
Topics: Ajax Products, Announcement
Comments: 3 so far
Leave a comment
About Pathfinder
Recent
- Walk-Through Test Coverage
- Where minimalism fails: The problem with Apple’s less-is-more approach
- jQuery goodness with ASP .NET
- Design Thinking
- Bullseye Diagram
- Roles Testing For Security
- Blackbird takes the pain out of JavaScript logging
- Making GWT JSON not Quite so Painful
- IDEA - preconference workshop 06 Oct 08
- HTML5, Ajax history management, and The Ajax Experience 2008 Boston
Archives
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006


JavaFX (or F3) is statically typed (with type inference I think).
But it really is an embarrassment. F3 was OK for what it was. It is not an Ajax or Flash killer. There is no sound or video support. There is no nonlinear animation. There is no graphical designer. Their examples are half working imitations of other people’s Flash sites (copyright infringing images and all).
F3 was a hobby project, and it is nowhere near ready for real use.
Comment by Asd, Wednesday, May 9, 2007 @ 11:40 am
There’s nothing wrong with dynamic typing, as long as you can statically analyse the code too (plus give hints to static analysers). Mandatory static typing increases dependencies between modules, leading to more monolithic code.
I like Bracha’s pluggable types - add type annotations when you feel like it, but if your type annotations don’t match, that doesn’t stop programs from running.
Comment by Ricky Clarkson, Wednesday, May 9, 2007 @ 11:47 am
Flash, Silveright, and JavaFX aren’t positioned to be AJAX killers. AJAX is what the baseline of the web experience will become. Because of its inherent technical limitations, AJAX doesn’t compete with Flash or Silveright
Comment by Dave, Wednesday, May 9, 2007 @ 6:18 pm