Yeah it's obviously impossible to satisfy everyone, it's just that for a long time JavaFX has been looking like a (rather fat) solution looking for a problem - I don't recall a real customer need when they took over F3. Gaining a marked is only good if you do not secretly/ passively deprecate an existing one (Sun let that pendulum swing before, from SE to EE). So while everyone owes it a chance (incl. me) it's obvious that some things have suffered and I just hope for Sun's sake it'll be worth it is all. My only gripe is Sun not acknowledging this, with a concerned community watching and affected.
/Casper > P.S. The backlash of Casper and others to JavaFX is also analogous to > the backlash Sun would get for any really disruptive Java "next" -- a > large portion of the community (myself included) would ask (scream) why > Sun couldn't just focus on the big problems and address them in a > non-disruptive manner in a non-disruptive Java version increment rather > than getting distracted by some Java "next" with disruptive barriers > between it and the community's existing Java investment. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
