- Keep JavaONE - with heavy focus on developers.
- Embrace OSGi down in the core VM.
- Kill JavaFx - Work closer with Adobe on Flex / BlazeDS / LCDS.
- Improve Dynamic Language Support - groovy / scala / JRuby / Jython /etc...
- Talk to Google about ME (seriously?) / Android
- Kill NetBeans - Eclipse may be King, but IntelliJ is God !
- Introduce new language primitives XML / Function / JSON.
- Improve language - set/get bean, native String ( switch myString {case "foo": ...}) as for casting.
- LINQ for Java - LCDS can help here.
- Talk to the Spring folks - there-is-only-one-framework-zuul :-)
- No "Effing" store !
Wednesday, February 10, 2010
How Oracle Can Improve Java
Found this great article "15 Ways Oracle Can Make Java Better (and Improve Its Stance with Developers)" - here is my "in the weed" take:So....what do you think ?
Subscribe to:
Post Comments (Atom)
2 comments:
For me this one is very important: "Kill JavaFx - Work closer with Adobe on Flex / BlazeDS / LCDS"
Thanks for sharing ...
Regards,
Christian
I can't understand why people tolerate the unstable mess that is Eclipse. Eclipse gets in the way, IntelliJ just lets me focus on my work.
OSGi in the core would be fantastic. There were some JSRs that together provided a lot of the same functionality - what a waste of time, just bloody adopt OSGi, bozos.
Post a Comment