Eric Gunnerson comenta sobre el JavaOne 2004, en particular me llama la atención algunos comentarios:
JavaOne 2004: Final Thoughts.
JavaOne 2004 FinalThoughts
"I’m also impressed at the speed at which JSRs progress and how they’re decoupled from main releases of the product. There’s an opportunity to design/code/release in several iterations rather than in one big release that we aren’t currently utilizing (though we have discussed doing this in the past)."
Sería interesante que MS cambiara su ciclo de liberación para hacerlo más dinámico, a pesar de que ultimamente han hecho un esfuerzo importante por involucrar a los clientes claves (por ejemplo a los MVP's), en las fases iniciales del producto (lo que evita el: "Tienes razón esa sería una excelente característica en el producto, pero ... la fase en la cual podiamos agregar eso ya paso, ahora solamente nos estamos concentrando en cerrar bugs", aún esta es una área de oportunidad.
"Java Language
The “Tiger” release of Java (was 1.5, now named 5.0) provides some interesting additions to the language, but after looking at the features in more detail and sampling the public reaction, I’m not convinced in the overall success of their additions. "
No estoy familiarizado al detalle de las nuevas características de Tiger, y aunque por el momento estoy bastante ocupado explorando el Beta 1 de Visual 2005 buscaré dedicar un fin de semana a explorarlo particularmente con el enfoque de comparar desde una perspectiva de programador las características similares (por ejemplo Generics) en ambas plataformas.
"Java IDEs
Several features in the Java world make it hard to write IDEs.
The fact that IDE development isn’t coupled to API development causes a lot of problems. I’m not an expert on Java development, but the fact that there were lots of demos of laying out forms and hooking them up leads me to believe that such features aren’t as expected in the Java IDE world as they are in VS. The fact that the ASP.NET team owns the whole stack from design-time to runtime gives a much more coherant experience."
Esto es cierto, como todo tiene ventajas importantes ser dueño de todo el stack ... aunque obviamente esto no siempre puede ser así y un modelo acoplado tiene su impacto en la diversidad de herramientas ...
"Eclipse is an interesting wild-card in this area. Because users often use a collection of modules that aren’t necessarily written to work together, consistency can suffer. On the other hand, the low-level extendability is far better than what we have in VS, and the fact that you can deal with your code at the AST level is a very powerful capability that isn’t available in Visual Studio. "
Eclipse en lo personal, es el único IDE de Java con el que se siento a gusto trabajando, tanto por el modelo de extensibilidad como con su desempeño ...
"Misc
There was a big “Java Timeline” display that ran 50 or so feet in the tunnel between Moscone South and North. There was space and markers for people to write their own comments on the timeline, and by the end of the conference, there was little free space. It was a cool thing to do, and would be especially cool if it ended up online so others could look at it."
Cool!
De:
 [Eric Gunnerson's C# Compendium]
11:13:08 AM 
|
