Join the discussion! Leave a comment through the comment form below!
Feel free to leave a comment on this site. You can use Textile and Emoticons. Your email address is only used to show a gravatar. Please stay on-topic and use common decency. Spammers will be shot in front of a live studio audience.
If you plan on posting code, use pastebin please and post a URL to the code. The comment processing doesn't deal very well with code. Sorry for the inconvenience.
Human comment spammers: don't bother posting your crap here. Comments are moderated and I won't let any of your shit through.
At 07 November '05 - 14:15 stefan wrote:
At 07 November '05 - 14:30 Max wrote:
“Here, look, if you make it trough the tough-as-hell installation procedure, make sure that you’ve CHMODded about 212352 directories juuuuust right, and then howl to the moon at precisely the right time…
...see, you can code ‘hello world’ in just one line of code! This framework is teh roxor!”
Bah humbug.
Real men don’t do frameworks. =]
At 07 November '05 - 14:40 stefan wrote:
Still, I’ve never been convinced that MVC is a good design pattern for php/webbased solutions. So that is my main gripe with these frameworks.
At 07 November '05 - 14:46 Marco wrote:
And damn, a G5 would crash REALLY hard when falling down 7 floors all the way down. Thank God I got it to run just before I did that. Phew…
Anyway, I can see your point. However, I also hate doing the same thing over and over and over again which is why a framework would come in handy. I’ll definitely take a look at Symfony and Wasp. (After I finish my Typo theme, which will probably take a while, considering the speed I mentioned earlier).
Ah well… these things keep us off the street now don’t they?
At 16 November '05 - 05:30 Tracey wrote:
At 16 November '05 - 20:45 chris wrote:
Disclaimer: symfony forked from the mojavi project, a PHP4 MVC framework. I used mojavi a lot, so symfony is my foray into PHP5.
Just please stop calling it a PHP5 “Ajax” framework. Ajax is eye candy on top of the real muscle here.
At 16 November '05 - 22:31 Marco wrote:
At 27 December '05 - 03:58 Mike wrote:
At 28 December '05 - 04:51 Marco wrote:
There’s nothing awkward about programming in PHP that I can see really.
At 13 February '07 - 07:05 Jonathan Wage wrote:
PHP:
if( $test )
{
}
Ruby:
if test
end
With php I had to hold use shift for 4 characters. I know that seems like nothing, which it is. But when you get on a roll, the ruby code is much fluid and easier to type. I never have to go back and correct a type in ruby, but in php it is just one extra thing to have to worry about, parenthesis, brackets, dollar signs, etc…
2.) Max, I don’t know what installation you were working with, either it was a broken one or you were smoking angel dust that day. if you can’t install rails, then you aren’t a web developer, and based on your comments you REALLY aren’t a web developer..
I have been developing for about 8 years now and started from the ground up with early versions of php. I have used crappy php frameworks, I have used my own php frameworks, I have used symfony, and I have used rails. When you develop application after application, you start to see trends, and I see things that are needed no matter the size of the application. And every project we go through the same things. A framework solves this problem, they have taken care of all the trivial stuff required to build a powerful web application that is easy to maintain and debug.
I have noticed that a lot of php developers(script kiddies) are angry whenever someone tries to down php or someone brings in a new technology that could shadow php. You will never become a true developer if you cannot get past this, php will not be the top dog forever and is already fading as new technologies become available.
My own personal opinion is that rails is the top dog of all the frameworks out there, and for these reasons:
1.) Deployment. If you have ever managed a large web application across dozens of servers, it is not possible to do manually. You could write your own deployment scripts, but why? Capistrano rocks and they have thought of everything for you.
2.) Integration with SVN/CVS for Capistrano.
3.) Execute your applications from the command line.
4.) Unit testing. Why in the hell would you troubleshoot issues the OLD FASHIONED way when you have robots at your finger tip WAITING to be programmed to do the awesome Q/A testing.
5.) Logging. It logs everything, don’t have to think about it. This is a major troubleshooting/debugging tool.
6.) The data modeling in rails..
blah blah blah..I could go on and on just naming all the things I use on a daily basis but have never had to put development time towards or any brain power towards. Where if I was not using a framework, every time I need something the frameworks have, I have to develop it or hack something up :) no bueno my friend..
At 13 February '07 - 17:10 Max wrote:
I’m not scared of Ruby. I’m not scared of any language, actually. The problem is: I simply don’t have the luxury of having enough time to learn them. I’m not being paid for horsing around with a new language, framework or whatnot, I’m paid to, you know, deliver stuff. Even if Ruby, or any other language, is easier, prettier, or less-shift-using — I can actually agree to that argument, there you go — I still have to take out the time to get to know it. I do know PHP, and I can deliver stuff with it.
Another issue is availability: I can pretty much bet my left testicle on the fact that Webhoster X is going to have PHP installed on his servers. Maybe not PHP5, but for most things PHP4 will do perfectly. Finding a hoster that does RoR is going to be a bit harder. Now imagine that Customer Y already has a web site and is not willing to move around his hosting stuff.
Calling me “not a web designer” and PHP developers “script kiddies” is not going to change those facts in the least. You may try to educate me and enlighten me — and hope that my situation, whether you agree with it or not, can be changed — and that might even work. Name-calling is not.
At 13 February '07 - 17:14 Max wrote:
Welcome to the script kiddies club.
At 13 February '07 - 18:19 Jonathan Wage wrote:
You would be amazed at the time you save when using these frameworks, and rails has symfony beat as far as the tools available for web applications, hands down.
I deliver also, and I strive to deliver something better each time to our clients. To be on top of the latest technology, after all that is what we are hired for.
Also, can you not see why PHP would be considered more cumber sum to type than Ruby. I mean it is like comparing the size of atoms, but I find myself being able to type ruby syntax so much faster than php, combine that with rails and I see the king of frameworks.
“Here, look, if you make it trough the tough-as-hell installation procedure, make sure that you’ve CHMODded about 212352 directories juuuuust right, and then howl to the moon at precisely the right time…
...see, you can code ‘hello world’ in just one line of code! This framework is teh roxor!”
I have installed and configured rails servers several times and i have never encountered an installation where I had to do any of the things you listed above. Like you said, you haven’t given enough time to either of them in order to judge whether or not it is useful.
The sites in my resume for client project experience may be all php/mysql, but they are not small projects/sites by any means. I used to be a member of the php script kiddy crew several years ago, but I knew I didn’t want to stay at that level forever, so that brings us to where I am today. Loving rails/symfony and starting a new life with them :)
At 13 February '07 - 18:22 Jonathan Wage wrote:
At 14 February '07 - 11:35 Marco wrote:
I agree that Ruby has a lean and mean syntax. However, I don’t think it’s of major importance to the process of application development. Only a very small percentage of time writing code is spent on actual typing anyway. I’ve seen examples of Ruby being more elegant than PHP in certain cases but I wonder how important that really is in the big picture.
I’m sure every development environment has it’s advantages and disadvantages compared to alternative solutions. I just don’t believe any of them is ‘better’ than other ones or makes software development really significantly easier. The fundamental process of software design and development just doesn’t really get different when switching to another environment, at least it isn’t when doing it MVC style.
What’s left is pros and cons associated to each individual language/framework that may influence the decision which one to choose. In some cases PHP may be the best choice, in other cases Ruby may be. Or something completely different. It just really depends on the situation in my opinion.
As far as I’m concerned all the rest is merely zealotism and fanboy behaviour.
Just my 5 cents of course…
At 14 February '07 - 11:44 Jonathan Wage wrote:
It really isn’t the software development you save time on with frameworks, it is the trivial things you are required to do to build a web application no matter WHAT language, and having these frameworks do all the work for you in that regard, then you can solely concentrate on the actual development of the software, and not the technologies for web applications that already exist out there.