Développement
Développement Web
——————————————————————————————–
Le choix reste assez vaste. En effet, il concerne : Eclipse, Netbeans, IntelliJ, JBuilder, JCreator, etc. Et la compétition entre ces différentes solutions fait que leur développement est rapide et ce qui était vrai il y a quelques mois, peut être totalement remis en cause en très peu de temps.
——————————————————————————————–
Why Ruby is wining the race?
It’s real that we don’t have just one place for one language to speak. While the Java platform is an excellent choice for full-blown application development, it’s never really fit the need for small programs or macros. Java 6 recognized this by adding the javax.script package for interoperating with scripting languages like BeanShell, Python, Perl, Ruby, ECMAScript, and Groovy as well as an invokedynamic virtual machine instruction to allow direct compilation of dynamically typed languages to the Java VM.
For 2007, I think there’s more and more longing to develop with Ruby, although it’s not actually my personal favourite. Python code seems a lot cleaner and easier to understand than Ruby code, and I think most Java programmers would agree. However, Python came out at the wrong time. Many developers had to make a choice between learning Python and learning Java code, and most chose Java code. Now that they’ve finally digested the Java syntax and are ready to add another language to their toolbox, they want tomorrow’s language, not yesterday’s, and that language looks to be Ruby. Most importantly, Ruby has an absolute killer app in Ruby on Rails. Its simplicity is incredibly attractive to the legion of disillusioned Java Enterprise Edition (JEE) developers.
Beyond Rails, the JRuby project offers as good or better integration with existing Java code and libraries than the other scripting languages. In fact, JRuby may well surpass the standard Ruby distribution and become the preferred platform for Ruby programmers, not just Java programmers doing a little Ruby on the side. It’s that good. Python programmers will object that they’ve had the best aspects of JRuby for years with Jython, and they’re right. It’s said I think, Ruby has the momentum and Python doesn’t.
The big problem or may be deal of JEE:
The overarching trend, in the enterprise space is a desire for simplicity. Massive frameworks are out; small and simple is in. Increasingly, customers are rejecting large parts of the JEE stack, and that’s likely to continue. Instead, customers are moving to simpler frameworks like Spring or off the Java platform entirely to Ruby on Rails.
