I think 'jumping ship' is the wrong way to think about it. C# is still a very useful language, however in certain situations Ruby is the more logical choice. I don't see this as either\or, but a way to extend your toolset and choice the right language for your scenario - be it C#, Ruby or even VB.net! Plus there are a lot of legacy systems and knowledge based around C#, certainly a decision when deciding on your language.
Ben Blog.BenHall.me.uk On Wed, Jun 18, 2008 at 10:53 AM, Michael Foord <[EMAIL PROTECTED]> wrote: > I think you'll find that C# has a strong following and that not *everyone* > prefers Ruby (or Python)... > > Michael Foord > > SoftMind Systems wrote: >>> >>> Just wondering what percentage will still prefer to work with the ugly >>> coding and long code approach with C#.....? >>> >> >> ------------------------------------------------------------ >> To be frank and honest... I just hate C#. C# 3.0 is just nothing but >> imitating few powers of Ruby onto C#. >> >> I just do not know.. whether MSFT will respect IronRuby like C#. >> >> The Day i feel, IronRuby is treated as a MSFT child, i will make a >> switchover to IronRuby with wasting a second. >> >> I am currently exploring Ruby and Ruby on Rails >> >> > > _______________________________________________ > Ironruby-core mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/ironruby-core > _______________________________________________ Ironruby-core mailing list [email protected] http://rubyforge.org/mailman/listinfo/ironruby-core
