The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

That I love Ruby's syntax, but I still don't find myself as productive as I do with PHP.

And that Ruby is even further away from a corporate standard than PHP, and is therefore even harder to introduce into an "Enterprise" environment.

I would just like to say that I find myself way more productive than with PHP. Also, as for the "corporate environment" it just takes time. It's starting to be adopted. I know a couple of fortune 500 companies that are starting to use ruby / rails for critical apps. It's mostly a question of people there realizing the potential... and how much respect the developers get from managers.

It runs like crap on Windows (Rails, not necessarily Ruby) so my chances of being able to actually use it at work is near nil (you try telling a Windows software company to switch its server platforms).

It runs like crap on Windows (Rails, not necessarily Ruby) so my chances of being able to actually use it at work is near nil (you try telling a Windows software company to switch its server platforms).

what about it runs like crap on windows?? I've had no problem with it on Windows, but I've only been using it for a few weeks...

My biggest problem with rails (not ruby) is I have trouble porting my apps to my host from my local development machine. This is probably more of a problem with the way my host is set up though..

It runs like crap on Windows (Rails, not necessarily Ruby) so my chances of being able to actually use it at work is near nil (you try telling a Windows software company to switch its server platforms).

A small quote from RailsConf last week (actually by Martin Fowler originally):

what about it runs like crap on windows?? I've had no problem with it on Windows, but I've only been using it for a few weeks...

Try deploying in production on an IIS server and without Apache or lighttpd as a proxy. It's possible, but the fact is Windows is a second-class deployment platform for Rails and it seems like Zed Shaw is the only person doing anything about it.

Originally Posted by Luke Redpath

A small quote from RailsConf last week (actually by Martin Fowler originally):

One of the ways I start learning a new language is by picking up my old and trusty algorithms and data-structures book, and then I start translating those into the new language to familiarize myself with the language's primitives.

With Ruby it was a big dissapointment, as you can imagine.

But on the other hand ... it is now my #1 scripting language because there's no other as productive.
I have a dozen cron-jobs written in Ruby that are in production.
I also have mixed PHP-Ruby applications ... just for fun

And I love the productivity of Ruby on Rails ... but I still use PHP and Java for serious websites ... and yes, it has something to do with fear of unknown problems that may appear, or fear of performance issues.

But that may fade in time, and I really hope performance improves, because its a wonderfull language.

As long as you have the cool Symbol#to_proc extension (its in Rails and the Ruby extensions project, and Ruby 1.9 I think).

You can do this:

Code:

def foo(block_one, block_two)
puts "One is a #{block_one.class} and two is a #{block_two.class}"
end
foo(proc{|x| ...}, proc{|x| ...})
#=> "One is a Proc and two is a Proc"

OK its not quite as clean, but its better than Proc.new. Having Procs as first class objects is the key I feel, not having blocks as first class objects. It would be like asking for parentheses as first-class objects; they are only syntax constructs.

Quit confusing rails with ruby
Ruby kills php in speed in coming out of a database
Php just has faster text processing.
Quit comparing them please, they are better for different purposes.

Even if PHP is faster so what? You just have to know when to use the right language for the job. If you need super performance then Ruby probably won't help you (for now, who knows with 2.0), but at the same time, very few dynamic languages would help at that kind of scale.