I’m currently attending JavaOne, the first JavaOne hosted and sponsored by Oracle. So far the biggest change is that technical sessions start at 8:00am. I know, was speaking at one. 🙂 I had to get up at 4:45am to get into San Francisco on time. But, who am I to complain?
Actually, the real big news so far is the demise of JavaFX Script. The reviews from the blogosphere/twittersphere are mixed. Some people are loving it. Indeed, one of the comments I received on my JavaFX Script talk from last year’s JavaOne was “It’s beyond me why anyone would create such a language.” People such as this commenter are perhaps glad to see JavaFX Script go away.
On the other hand, there is also some disappointment, some criticism, some mourning, and even some denial. But this is the price — or perhaps the cost — of progress. (But see also below.)
There’s been some misinformation floating around the twittersphere about “JavaFX is dead” and some such. This is decidedly not the case. JavaFX Script is indeed on its way out (though existing programs will still run for a while, and you can still develop new ones, should you decide to do such a thing) but JavaFX itself is most definitely alive and will continue develop. Here’s a clarifying statement from the JavaFX Architect, Richard Bair (what Mr. Bair meant to say was…) about the changes coming in JavaFX 2.0:
Also, the official JavaFX roadmap statement is here:
* * *
The talk I gave this morning (along with my colleague, Paru Somashekar) was on JavaFX UI Controls. Originally we were going to present a lot more code examples, but with the move away from JavaFX Script we had to retool the talk. In the end we showed a survey of the controls and some demos of the controls in action but relatively little code. We did do a small comparison of JavaFX Script to a new, provisional Java-based API for JavaFX. Overall the talk was well attended (better than I expected for an 8am tech session!) and I thought it was a success.
One questioner at the session criticized the dropping of support for JavaFX Script and in particular its declarative syntax. He was very polite, apologizing for making a statement instead of a question and also for shooting the messenger. I didn’t get a chance to talk to the gentleman, but I wanted to say that I wasn’t offended by his comment. On the JavaFX team we knew that dropping JavaFX Script would be painful for some. Anyone who’s affected needs to speak out about it. I don’t think the decision will be reversed but it might be possible for those impact to get some help with migration.
* * *
We had a great lunch at Henry’s Hunan. I’m still full. Oh, well there was also that big cookie I had during the afternoon break.
* * *
It’s a bit odd not being in Moscone. Unlike I think all prior JavaOnes, this year JavaOne is in a trio of hotels: the SF Hilton, Hotel Nikko, and the Parc 55. The hotel meeting rooms are smaller, so they fill up sooner, and in general Oracle employees (such as myself) can only get in if there’s space available — which there often is not. As a result I’ve been unable to get into a few sessions that I wanted to attend. Oh well, I’ll have to pick up the presentation slides later on. But, who am I to complain?
* * *
This evening I’m attending a few BOFs: on Jigsaw, OpenJDK, and on Visual Design with CSS. After that I’ll head home, attempting not to fall asleep during the drive, and fall into bed at the end of a very long day.