JavaScript is becoming the Ruby killer?

I love Ruby and participate in the Ruby community where I am located. I am a member of the programming society RubyFools. Sometimes I give some lectures on Ruby's greatness and Ruby projects I have worked on in my spare time. I feel very free to use Ruby for programming. I love the vitality of the Ruby community's continuous development of new frameworks and new tools, and I am everywhere to promote its development. In a word, I am a Ruby cool "Ruby dude ").

Recently, however, I have always felt that our Ruby cool is extinct, and there is a hype about new JavaScript Engines such as V8 and TraceMonkey. One night, JavaScript attracted a lot of attention and people started to talk about it: Now JavaScript may be fully used to create rich client applications. Almost every computer in the world has some JavaScript Engines, and people are aware of the potential of JavaScript.

As many of my Java/. NET developer friends have said, has Ruby actually become the so-called "instant hyping language" temporary hype language? Have those enthusiastic participants left Ruby? Has Ruby been developed enough to establish a foothold in the future? What will happen to the Ruby community if the boom declines? How can I prove that Ruby is the language choice for new commercial programming projects?

Of course, the client's quick JavaScript leaves a lot of space for the server-side framework, and I still think Ruby is very suitable for this. It is no longer a "gap" between other technologies, because many methods introduced by Rails have slowly found a living space on other frameworks of other platforms.

There are other ideas: Ruby is more than just Ruby. Ruby 1.8 is widely known, and a lot of work has been transplanted to Ruby 1.9. Some new language structures have been added, and the biggest problem is that Ruby 1.9 is still "feeling Ruby "? I haven't used Ruby 1.9 yet, but I certainly don't like all these new language structures. These new language structures make Ruby increasingly difficult for new scholars to learn. If the community is split into two parts: 1.8 and 1.9, which is obviously unfavorable, isn't it?
I am worried that my favorite language will be in trouble in the near future. However, for the near future and the near future, I will still use Ruby as a great tool to quickly solve many problems, but I will always pay attention to what will happen, such as JavaScript.

Related Articles]

• Is Ruby on Rails ready for Enterprise SOA?

• Overview of advantages and disadvantages of Java,. Net, PHP, and Ruby