|
|
|
|
Tools
Posted:
Oct 28, 2005 1:57 PM
|
|
|
Please post your thoughts and ideas for Tools here.
Keyword for this area:
source code editors
integrated development environments (IDEs)
plug-ins
performance analysis tools
monitoring solutions
modeling systems
collaboration
experimental tools
Other
|
|
|
|
|
|
|
Re: Tools
Posted:
Nov 1, 2005 2:44 PM
in response to: rwc
|
|
|
I would be very interested in how Sun are going to get the JavaBean Component market started. Not before there are oodles of really good component will the desktop truly take of.
Today .NET outweight Java 10 to 1 in this area since the component support is so much better on that competing platform. Basically it easier to make an advanced component and edit that is Visual Studio.
Some connection to JSR-273 would be good.
Cheers,
Mikael Grev
|
|
|
|
|
|
|
|
|
Re: Tools
Posted:
Nov 25, 2005 4:43 PM
in response to: mgrev
|
|
|
Maybe it's not the tools or Javabean specs. When you compare to .NET you're talking about Visual Studio alone, and MS librries, but when you talk about Java you're talking about Eclipse, Netbeans, Sun Studio, IDEA, JBuilder, JDeveloper, etc.
It's harder to create components when you have to target multiple IDEs. Then people develop libraries that require just coding and forget about tool integration.
However people use the Java Platform because of standardization and to avoid vendor lock-in, so they don't feel compelled to use vendor-specific tools and components.
So things like data-aware components should be part of the platform itself, and not add-ons from comercial vendors or open-source projects. The Java Platform is sometimes too hugue but other time too little for decelopers.
It doesn't help either that some JCP standards were left in incomplete state, like JDO 1.0, EJB 2.0 and JSF 1.0. Incomplete because they don't define how some things have to be done (like OO/relational mapping in JDO and EJB) or they define a too small set of components (like JSF).
A healthy market for components require a lot of people developing using components, so there are potential buyers. But Java developers today don't develop for components, they develop for APIs, because that's the way the Java platform and all its editions were built.
So the platform needs to have a rich of components, suitable for use in IDEs (any IDE!) before there is a market for vendors to sell value added components.
|
|
|
|
|
|
|
|
|
Re: Tools
Posted:
Nov 1, 2005 5:38 PM
in response to: rwc
|
|
|
I strongly agree about Javabeans possibilities. It is a wonderful field to be developed, as soon as specs get better.
Diego.
|
|
|
|
|
java.net RSS
