> 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.
But it was still just XML, with a schema attached. And the code-behind still C# and VB. > 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. Fair enough. > WP7 is a big strength for Silverlight, but that's more about the > significance of WP7 than the quality of Silverlight. Well I still see it as a quality of Silverlight, that the programming model and probably most of the WPF subset, is immediately recognizable to a very large crowd of .NET people. Even Android is less approachable, since it represents some fairly radical new ideas... an R file for statically encapsulating resources, Apache libraries rather than JSE, missing BufferedImage, no Enum support etc. So while Android is clearly a hybrid/non-sanctioned subset/fork, it looks like WP7 will be a more complete story. Could you imagine the enum removed from WP7? -- 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.
