On Sep 21, 1:25 pm, Casper Bang <[email protected]> wrote: > Well except in the case of Silverlight, developers did not have to > learn a new syntax nor wait for the tool-chain to catch up.
Sure we did. I worked on a team of .NET developers using Silverlight for the first time: we had to learn XAML, the new wildly different layout scheme, the new control set, and brand new multithreading model. I've done significant programming with both Silverlight and JavaFX. They both had learning curves and I wouldn't say either was substantially better in that regard. > I agree, both aren't exactly success stories. Microsoft has the WP7 > card up their sleeve though. Similarly JavaFX Script could've been > wonderful on Android... Yes: Runtime Relevance > Tool Quality People are enthusiastically using Objective-C because of the iOS platform, not out of love for the language itself or the theoretical design of the tools themselves. WP7 is a big strength for Silverlight, but that's more about the significance of WP7 than the quality of Silverlight. JavaFX, and desktop Java as a whole, is strictly limited to Win/Mac/ Linux, which basically kills it as mass market consumer platform. But for various workstation type software it (along with Silverlight) is still completely relevant. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
