Comments on: Ruby on Rails and PHP

By: Pies

Pies — Mon, 18 Apr 2005 08:43:05 +0000

You might want to take a look at the framework I’m developing that aspires — as Richard Dawkins once wrote, one can specify goals without presumptions — to be the Rails of PHP. It’s Public Domain, so steal whatever you like. http://www.sputnik.pl/cake/

By: Loud Thinking

Loud Thinking — Sat, 16 Apr 2005 10:12:04 +0000

Rails extends warm welcome to PHP developer

Ben Curtis is concerned about the “significant changes happening” in Rails and how to cope with keeping up. We hear…

By: Ladislav Martincik

Ladislav Martincik — Fri, 15 Apr 2005 15:32:19 +0000

If you’re going to save a time with Ruby and “Ruby on Rails” though you still have to invest a time to learn and check changes, than it’s always worth to go in.

By: Curt Hibbs

Curt Hibbs — Fri, 15 Apr 2005 14:14:38 +0000

Finally, there is youth. Rails is still in its infancy. While that’s a great opportunity for getting in there and being able to make contributions to the core product (I have more ideas than I do time), it’s not so great when you have to do deal with significant changes happening to your framework. This will settle down a bit soon, I’m sure, but at the moment I’m still a little hesitant to use something at version 0.11.1.

Don’t be put off by the version number… it’s misleading in two ways. The sequence of version numbers went 0.9.0 to 0.10.0 to 0.11.0 — the jump to 0.10.0 looked like a backwards step to many people, even though that was not the intent. Rails is just a month or so off from its 1.0 release. Also, the core of Rails is pretty stable since 0.10.0 — mostly new features being added. If you are short on time (as we all are), then you owe it to yourself to start working with Rails.

By: Loud Thinking

Loud Thinking — Fri, 15 Apr 2005 13:53:54 +0000

Comparing the infancy to your home-grown fruits

For all the flak I’ve fired at the old boys doing J2EE, it at least appears that they got one…