> I would counter that only by saying that if you > use the fancy GUI tools in visual studio for .NET you are going to be > similarly trapped I believe.
The .NET languages are driven by "programmer usability" so you have a very strong de-facto standard helped along with language features (i.e. partial classes, as oppose to the locked-lines mess in NetBeans). From what I've experienced, much of GroupLayout (apart from the chaining nature of the API and the use of XML files) borrows heavily from .NET. That's fine of course, we never had a good WYSIWYG in Java before and most people welcome a good prototyping/RAD tool. However, in my experiences, GroupLayout fails later in the maintenance stage, where Matisse is all of a sudden unable to render sufficiently complex layouts and you have to go behind NetBeans back to be able to refactor, clean and fix stuff which is not always possible. I don't know what the current status of JDeveloper is, but for a long while they where quite mad at Sun for going this non-standard way so it seems NetBeans is, willingly or not, slowly talking the same path as Visual Studio in certain aspects. /Casper --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
