I have given up C#, PHP, and Java like a bad drug. I still play with haskell, python and lisp occasionally, but Ruby is what makes me happy, and for web stuff I only use Rails.
Well, I would love to concentrate my work on ruby and especially ruby on rails, but there are some projects which are implemented in Asp.NET. So I am stuck for now. Moreover, I think every web developer still has to maintain certain PHP skills in order to get some projects done. There are so many php open source projects out there, it would be a waste of time and resources to start them from scratch. So we still need the skills to maintain and hack them for our purposes. Still, the share of ruby projects is constantly increasing.
RoR is certainly picking up steam, but it's far from critical mass. Even though development is easy, there is still relatively little community consensus about what is the "right" way to deploy and scale. Companies like Engine Yard and Joyent are slowly solving these operations issues, but there is a long way to go.
Eric Knoller RoR Power http://www.rorpower.com
Ruby is fantastic, and Rails is a framework worthy of the language, but limiting yourself to a single language or platform is asking for trouble. I like to keep my hands dirty by playing in other niche languages (currently working on Erlang and D). You can pick up surprising insights by shopping around with an open mind.
Rails is a web framework not a language. :)
For the web, Ruby, for scripts, Ruby. I don't write desktop apps anymore as I don't have to deal with windows anymore, but native C/C++ is always the most stable and speedy language choice for desktop apps. Maybe C# if it was Windows only.
These days I use Rails exclusively. That's because my work is entirely with greenfields website development - for which Rails is well-suited. In the past I have had considerable experience with C - and if I were to write desktop (or terminal) apps, that is my choice.
I'd certainly agree with other programmers here who note that keeping your fingers in other pies is a wise choice. Don't want to anchor yourself too tightly to a single technology - for yea, even Rails will become a dinosaur someday. Happens to the best of them... but for the moment - it is still fresh and full of potential, and I will continue to enjoy it while it stands full in the sunshine.
By the way, is there any other framework developed in Ruby (is that possible?) other than Rails? ..or maybe Ruby written in other framework? Just wondering..
nice, didn't even realize there were so many. I do agree with the statement that sticking to one language only is not a very good thing. I guess doing two different languages/frameworks, like ASP.Net and PHP might work out really well. Cashwise, too. What's most annoying in ASP.Net is that it's not open source - though the source is downloadable now, but I found a fancy framework like an hour ago, called spring.net. heard of it?
As a student, developer and a "hacker" - I have to work with many languages and frameworks. Java, PHP, C++, TCL, Perl ... and Offcourse Ruby. Good to see there are certain php frameworks that now copy rails which makes life some what easier for me when I jump across languages. When doing my Java projects at university I always stick with MCV design pattern to solve all my problems. But sadly some languages/frameworks still have to catchup with rails awsome framework structure.
So.. untill then! rails it is.