Ruby, Python and JScript--OH MY!
The road to the Emerald City is paved with umm, err, developers! (OK maybe not actual developers cus that would be too gross) Perhaps this is a bad analogy but Sun is very much committed to developers and of course open source communities. It follows the whole Volume Drives Value philosophy in that the more developers you have using your platforms the more value you can deliver. And scripting (or dynamic) languages are gaining a lot of attention among developers. One recent forecast put Ruby adoption at four million in the next five years.
In the latest installment of Sun does scripting we announced the availability of NetBeans 6.1 Beta which includes JavaScript editing features, as well as enhancements to existing Ruby/JRuby features. We've also added support for the Spring framework and tighter integration with MySQL.
If you have been paying attention - and I'm sure you have - you've probably noticed that Sun has been putting a lot of effort in bolstering our scripting language play, including the hiring of two leading Python developers and our much heralded Ruby/JRuby support.
But why you may ask? The answer lies in the notion that the Web is THE primary platform for delivering dynamic applications and services, which in turn are built using dynamic languages. Who better than Sun to be place where developers can build, test and deploy the applications and services driving what can be referred to as "The Web Economy."
One of the pillars that will help us get there is a concept we call the Connected Developer.
What or who is the connected developer? Well there are others who can better define it and when they blog about it I'll let you know. But in the meantime you'll have to settle for my understanding of the definition. The connected developer is the new breed of developer who was "raised" on open source and collaborative communities and wants to be part of a dialogue. The connected developer is also the traditional/corporate or ISV developer looking to tap into a new, Web-centric development model. The connected developer will be critical to the success of our software strategy and we hope to tell you more about it as we approach CommunityOne so stay tuned!
In the latest installment of Sun does scripting we announced the availability of NetBeans 6.1 Beta which includes JavaScript editing features, as well as enhancements to existing Ruby/JRuby features. We've also added support for the Spring framework and tighter integration with MySQL.
If you have been paying attention - and I'm sure you have - you've probably noticed that Sun has been putting a lot of effort in bolstering our scripting language play, including the hiring of two leading Python developers and our much heralded Ruby/JRuby support.
But why you may ask? The answer lies in the notion that the Web is THE primary platform for delivering dynamic applications and services, which in turn are built using dynamic languages. Who better than Sun to be place where developers can build, test and deploy the applications and services driving what can be referred to as "The Web Economy."
One of the pillars that will help us get there is a concept we call the Connected Developer.
What or who is the connected developer? Well there are others who can better define it and when they blog about it I'll let you know. But in the meantime you'll have to settle for my understanding of the definition. The connected developer is the new breed of developer who was "raised" on open source and collaborative communities and wants to be part of a dialogue. The connected developer is also the traditional/corporate or ISV developer looking to tap into a new, Web-centric development model. The connected developer will be critical to the success of our software strategy and we hope to tell you more about it as we approach CommunityOne so stay tuned!
