Why PHP?

MadCat · 2008-09-23, 01:33 AM

@poornpig: RoR and a 120G database dick? Try Catalyst working off 5 read slave databases handling around 1Tb of data

Biggest (in database size anyway) project I've worked on so far. Anyway, you sure RoR is the right choice? I'd prefer PHP over Ruby since RoR has known issues scaling up to anything near useful

@justbondage: Actually, finding bad perl code can be easy but it depends on what it is you're looking at. Most one-off (or two-off) scripts that people smack together are an exercise in how-not-to-do-it but they work. Most people writing code that will be released (either on CPAN as open source or sold as a product) will take the time to tidy up the code and most likely re-do bits of it to be more easy to read.

E.g.

Code:

do_something unless $foo eq 'bar';

will get turned into

Code:

if $foo ne 'bar' {
  do_something;
}

Purely because the latter is easier to read.

As far as the holier-than-thou attitude, yeah you got us perl guys there

It tends to be a 'grown' attitude though since most non-perl coders will immediately dismiss perl as some silly sysadmin glue language -- hear enough of that, and you'll get very bitter and cynical. Coincidentally most perl coders are (or have been) system administrators, and most (if not all) sysadmins are very bitter, cynical and angry people

2008-09-23, 01:33 AM	#21
MadCat If something's hard to do, then it's not worth doing Join Date: Sep 2008 Location: Berlin, Germany Posts: 247	@poornpig: RoR and a 120G database dick? Try Catalyst working off 5 read slave databases handling around 1Tb of data Biggest (in database size anyway) project I've worked on so far. Anyway, you sure RoR is the right choice? I'd prefer PHP over Ruby since RoR has known issues scaling up to anything near useful @justbondage: Actually, finding bad perl code can be easy but it depends on what it is you're looking at. Most one-off (or two-off) scripts that people smack together are an exercise in how-not-to-do-it but they work. Most people writing code that will be released (either on CPAN as open source or sold as a product) will take the time to tidy up the code and most likely re-do bits of it to be more easy to read. E.g. Code: do_something unless $foo eq 'bar'; will get turned into Code: if $foo ne 'bar' { do_something; } Purely because the latter is easier to read. As far as the holier-than-thou attitude, yeah you got us perl guys there It tends to be a 'grown' attitude though since most non-perl coders will immediately dismiss perl as some silly sysadmin glue language -- hear enough of that, and you'll get very bitter and cynical. Coincidentally most perl coders are (or have been) system administrators, and most (if not all) sysadmins are very bitter, cynical and angry people