I beg to differ. PHP has big changes even in minor version upgrades. Just look at the Changelog. Total horror.
I don't watch the changelogs closely but I can't remember the last time this actually impacted anything I was working on. Obviously it depends on which modules are affected.
So I don't really get what you mean by "By contrast, Rails seems to use the database itself as the primarily source of configuration information."
I'm willing to say I'm flatly wrong about this. I just got this impression from the tutorials and a conversation I had with somebody. I'll talk about DataCruxWeb configuration in the next post and perhaps you can help me figure out how far off base I was. I still think the model concept in Rails is a bit different.
If you run your own server from scratch, and have to compile everything, deploying rails isn't harder than PHP.
I think you missed my aim in terms of deployment. I'm not concerned about configuration or compiling, but the actual runtime mechanism itself. I don't particularly want to use FastCGI and I really want to stay with Apache. As far as I know, Rails doesn't seem to have a deployment option that fits me.
Although there are the issues with the dumb configuration options like "magic_quotes" and stuff...
That's a one line directive, not really a big deal. :)
It's hard to comment on your comparison without having the possibility to look at DataCruxWeb
Absolutely true.
is it available publically?
Soon. :) Probably around Sept 15. I'm filling in some gaps and cleaning things up. If somebody is interested in absolute bleeding edge, they can contact me if they want something sooner.
It's definitely easier to add behavoir with Ruby & Rails than PHP. The language is much more dynamic, powerful and consistent.
These kind of statements are rather hard to prove or disprove, but I think I phrased the heading poorly. I didn't mean "it's easy to add behavior to a PHP app," I meant "it's easy to add behavior to DataCruxWeb if you know PHP."
What kind of behavioural changes do you mean? Do you know that the rails guy first tried to do the stuff in PHP, then rewrote in in Ruby into a smaller codebase in less time, because the language was so much more dynamic?
This is probably just leftovers from the previous comment, but again this is stuff that is hard to prove, and I'm really not that passionate about PHP in any case. I like Ruby and I like PHP for different reasons. To me, PHP is just like C -- it's out there in the ecosystem, it's simple and it's ubiquitous. DataCruxWeb isn't supposed to be a "Rails/Ruby killer" or anything like that. I'm trying to make this idea clear.
by Scott Stevenson — Aug 23
I beg to differ. PHP has big changes even in minor version upgrades. Just look at the Changelog. Total horror.
I don't watch the changelogs closely but I can't remember the last time this actually impacted anything I was working on. Obviously it depends on which modules are affected.
So I don't really get what you mean by "By contrast, Rails seems to use the database itself as the primarily source of configuration information."
I'm willing to say I'm flatly wrong about this. I just got this impression from the tutorials and a conversation I had with somebody. I'll talk about DataCruxWeb configuration in the next post and perhaps you can help me figure out how far off base I was. I still think the model concept in Rails is a bit different.
If you run your own server from scratch, and have to compile everything, deploying rails isn't harder than PHP.
I think you missed my aim in terms of deployment. I'm not concerned about configuration or compiling, but the actual runtime mechanism itself. I don't particularly want to use FastCGI and I really want to stay with Apache. As far as I know, Rails doesn't seem to have a deployment option that fits me.
Although there are the issues with the dumb configuration options like "magic_quotes" and stuff...
That's a one line directive, not really a big deal. :)
It's hard to comment on your comparison without having the possibility to look at DataCruxWeb
Absolutely true.
is it available publically?
Soon. :) Probably around Sept 15. I'm filling in some gaps and cleaning things up. If somebody is interested in absolute bleeding edge, they can contact me if they want something sooner.
It's definitely easier to add behavoir with Ruby & Rails than PHP. The language is much more dynamic, powerful and consistent.
These kind of statements are rather hard to prove or disprove, but I think I phrased the heading poorly. I didn't mean "it's easy to add behavior to a PHP app," I meant "it's easy to add behavior to DataCruxWeb if you know PHP."
What kind of behavioural changes do you mean? Do you know that the rails guy first tried to do the stuff in PHP, then rewrote in in Ruby into a smaller codebase in less time, because the language was so much more dynamic?
This is probably just leftovers from the previous comment, but again this is stuff that is hard to prove, and I'm really not that passionate about PHP in any case. I like Ruby and I like PHP for different reasons. To me, PHP is just like C -- it's out there in the ecosystem, it's simple and it's ubiquitous. DataCruxWeb isn't supposed to be a "Rails/Ruby killer" or anything like that. I'm trying to make this idea clear.