|
|
To Kill a Mockingbird (Collector's Edition)
|
I'm not sure why this article was written, as there appears to be nothing particularly newsworthy in it: The News.com reporter Marguerite Reardon has covered muni-Fi for as long as I have, and after reading this in-depth piece, I'm left wondering whether it was assigned far too early, and she was meeting an editorial desk requirement instead of feeling like the story was ready to "print." The article looks at Network Acquisition Corp. (NAC), the allegedly interim name for the group that's taken over Phila-Fi.
One source at the Knight Center for Digital Excellence notes, "The new network owners are supposed to have a much more sustainable business model." Supposed to. Later, "Network Acquisition Company, which acquired the network, hasn't talked publicly about the details of its new plan, but it has hinted that its strategy will differ from EarthLink's." Hasn't talked publicly. Then, "[NAC and Tropos] spokespeople said the companies would talk more about the network later this month when details of the new business plan are ready." Huh.
Reardon explains digital divide issues and looks into what Wireless Philadelphia has been up to, although doesn't note that delays in EarthLink's deployment and other factors have led to just a few hundred individuals that have been assisted by the non-profit; numbers may have changed, but that was as of a few months ago. Still, Wireless Philadelphia has apparently diversified its funding sources--Reardon cites 30 now.
I think we're still coming off the doldrums of August.
At the August 2008 Coding the Architecture London User Group, I presented an overview of Flex, Silverlight and JavaFX. If you've watched the video from the session, you would have seen that I wasn't very complimentary about JavaFX.
There are a number of reasons why I don't think that JavaFX is anywhere near ready for people considering building RIAs at this point in time ... quite simply, the latest preview build ships with a bunch of crippled Swing components. Granted, some of this has been talked about in the recent SDN interview; but tables are gone, tabbed panels/tabs are gone, you can't configure how scrollpanes should scroll, etc, etc. In addition to the crippled Swing components, the out-of-the-box result looks ugly when compared to Flex and Silverlight. Take a look at the screenshots in the slides from my Flex, Silverlight and JavaFX presentation for an example.
I have some other complaints about JavaFX too, which I'll admit only stem from a couple of days with it. I personally found that the error messages reported by the NetBeans plugin are cryptic and I actually couldn't get some stuff to work because the error messages just didn't make any sense. Oh, and then there's that declarative syntax. MXML and XAML are far easier to work with. Although I appreciate the folding support that you get in the JavaFX plugin, it still took me a long time to figure out what was going on when a curly brace was missing. That syntax isn't productive and I don't see anybody (especially designers) using it without some decent drag-and-drop tooling.
In Does Anyone Really Care About Desktop Java?, Bruce Eckel talks about how Sun might be taking the wrong tack with JavaFX. And I agree. Java on the desktop is a tough proposition given the competition. So then, the important questions...
I know it's (still) early days for JavaFX, but the preview version doesn't impress. Nobody may care about Java on the desktop, so why not focus on that mobile space instead.