Why Ruby?

Another classmate wrote a slightly garbled blog, revealing a yearning for "everyone still uses Java. Let alone the article itself. Just talked to Paul hammant about jruby in recent days. To put it simply, a classmate's guess is just a guess.

The key is that if you want to make a prediction, the safest prediction now is to say that Java is about to die-just like today's Delphi. Five years ago, Delphi and VC were undoubtedly mainstream. Java was not much better than Ruby today. However, nothing can beat time. Java is so popular today that it is enough to show that it has entered a three to five-year recession. This is the software industry: trying to embrace a technology for the last five years, the result is usually complaints such as "Why technology changes so fast.

What is next? This is not a difficult prediction. First, it should be simple-think about how many times you press Ctrl + space when writing a Java program using eclipse or idea, and you will know how simple your next language should be. Second, it should be flexible, because people need more flexibility to construct their own DSL in the face of the possibility of unlimited Internet applications. Finally, it does not necessarily need a "unified" framework (or a "platform") to solve all the problems. Martin Fowler's "post-modern programming" seems to be a more desirable way of working.

So the "Next" may not be Ruby, but at least ruby looks like it, so it is a good starting point for me to solve some problems at hand. Another mistake made by a student is that "researching ruby" is a long process that people will always study and lose patience. By mistake, Ruby is at hand and can be used at any time. It can help a lot. I don't mind if it is Ruby, rubyclr or jruby. The so-called "post-modern programming" is my favorite, that is, you never need to spend three full months to "Learn" something, you just use them.

In fact, this topic can be quite boring, because everyone knows that Java is going through the most brilliant stage of its lifecycle and the decline that comes with it-some may not want to believe it. What is really interesting is that the upcoming decline of Java is not because it is no longer competent for enterprise application development, but because the larger context-economy, enterprise, it-is about to (or is changing. Unfortunately, this topic is hard to be clearly explained at the end of this short article. As a reminder, you can still recall Delphi: it is still the best tool for developing desktop applications, but desktop applications are no longer needed.

As a simple conclusion: As in the past, changes are unstoppable. Ruby looks like a development tool we will need and can help me solve the problem at hand, so I am very happy to use it. If it is not the "one", I will not worry too much, because -- as I said -- the next mainstream language must be very simple, that is, the Migration cost from Ruby will not be too high. So it seems that there is no reason for me to stop using ruby-it is indeed a pleasant programming experience.