From: David Pollak Date: 2006-06-22T22:43:57+09:00 Subject: Re: Ruby goodies? ------=_Part_4279_15457697.1150983834310 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline I think the way to answer your question is by examples of what has been built in Ruby: - Erb -- It's a very simple text/HTML markup system that has most of the features of ASP.Net and gets the benefits of Java tag libraries without anything other than the syntax of Ruby. - ActiveRecord -- Ruby's philosophy has allowed for a light-weight, very powerful, very flexible OR mapping system without code generation or the other stuff that comes along with OR mapping in .Net or Java. - Writing tests -- look at the tests that are part of Ruby projects... they're far expressive and syntactically simple than anything I've seen in C#. - OS integration -- Ruby is better integrated in the OS and with C code than .Net will ever be. Even though .Net allows near-seamless integration with COM objects and calls in the C code, in the practical world, there's always a hidden 'gotcha' that causes 30 hours of QA to reproduce and 20 hours of development time to fix. - Rails -- If Microsoft could have developed something as simple and powerful as Rails, they'd own the world. Instead, the Ruby gestault allowed a small, very smart bunch of folks to roll 75%+ of the mundane web development chores into an amazing package that doesn't generate a single line of code. C# has its roots in C++ (as does Java.) There are benefits to those roots. There are also costs to those roots. Ruby has its roots in (among other things) SmallTalk. Out of SmallTalk's gestault grew OS X's InterfaceBuild and Rails, two of the most beautiful development environments. It's not about features on a checklist, it's about the approach that Ruby allows to solving problems. Thanks, David On 6/22/06, Roger Johansson wrote: > > Im a C# programmer and Im totally new to Ruby. > > What would you guys say is the main benefits of Ruby over C#? > C# has closures and is getting lambdas in C#3 > > So in what scenarios should I absolutely go for Ruby instead of C#? > > One of the benefits that I've found myself is the reflection/runtime > modification support. > > When I implemented my .NET AOP lib NAspect in .NET it took a few good > months to make it work. > > In Ruby it took me about 5h to get support for pointcuts, interceptors > and the whole kit. > So that part was pretty amazing. > > but are there any other areas where ruby really shines, or are all of > the goodies related to the abillity to modify things on the fly? > > //Roger > > -- > Posted via http://www.ruby-forum.com/. > > -- -------- David Pollak's Ruby Playground http://dppruby.com ------=_Part_4279_15457697.1150983834310--