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.
Yes it does. Naming conventions change, etc. Very very many settings are unnecessarily configureable. I had tons of problems with PHP, and I used it since the beginning of PHP3. I still have to maintain some sites where I use pdflib and gdlib, the latter is behaving quite differently in different versions, quite a mess.
...but the actual runtime mechanism itself. I don't particularly want to use FastCGI and I really want to stay with Apache.
What's your grudge against FastCGI? It can be a little bit enervating if you have to do it yourself. But if the main work is done, you shouldn't be experience any big differences. E.g. most ISPs use the FastCGI version of PHP for security reasons.
The paragraphy immediately before that comment specifically called out Rail's myriad of special syntax.[/i|
could you give examples? my main understanding issue with rails was to see how dynamic ruby is. the functions that can be called inside a class definition that modify the class. btw.: the pragmatic programmers book is really the book to read for ruby ;-)
p.s.: i don't want to sound rude. if i do, it's probably the language barrier. i just wanted to jump into the gap of missing rails experience. i have been on both sides, php and rubyonrails, and i won't do any php unless i must to maintain my old sites anymore / or the scope isn't a web application, but merely one function in a website. and one more thing: i don't want to sound like i'm opposed to your framework. essentially a good designed framework can be done in most of the languages out there, also the crappy ones. php has so many inconsistencies, most of the functions lack exactly the thing you would have needed, there is a plethora of functions for almost the same task, their naming is absolutely arbitrary, things like $hash[-1] fail abysmally, this:
[pre]
function MyArray() {
return array('de'=>array('eins','zwei','drei'));
}
// That would work in any decent language I know,
// in PHP it doesn't
$DE_MyArray=myArray()['de'];
$DE_MyArray=array('de'=>array('eins','zwei','drei'))['de'];
// With PHP you have to do this:
$DE_MyArray=myArray();
$DE_MyArray=$DE_MyArray['de'];
[/pre]
Scoping of variables... I could go on for ages. Most of the annoyances I haven't written down, but argued over verbally with my coworkers.[/pre]
by Dominik Wagner — Aug 24
Yes it does. Naming conventions change, etc. Very very many settings are unnecessarily configureable. I had tons of problems with PHP, and I used it since the beginning of PHP3. I still have to maintain some sites where I use pdflib and gdlib, the latter is behaving quite differently in different versions, quite a mess.
...but the actual runtime mechanism itself. I don't particularly want to use FastCGI and I really want to stay with Apache.
What's your grudge against FastCGI? It can be a little bit enervating if you have to do it yourself. But if the main work is done, you shouldn't be experience any big differences. E.g. most ISPs use the FastCGI version of PHP for security reasons.
The paragraphy immediately before that comment specifically called out Rail's myriad of special syntax.[/i|
could you give examples? my main understanding issue with rails was to see how dynamic ruby is. the functions that can be called inside a class definition that modify the class. btw.: the pragmatic programmers book is really the book to read for ruby ;-)
p.s.: i don't want to sound rude. if i do, it's probably the language barrier. i just wanted to jump into the gap of missing rails experience. i have been on both sides, php and rubyonrails, and i won't do any php unless i must to maintain my old sites anymore / or the scope isn't a web application, but merely one function in a website. and one more thing: i don't want to sound like i'm opposed to your framework. essentially a good designed framework can be done in most of the languages out there, also the crappy ones. php has so many inconsistencies, most of the functions lack exactly the thing you would have needed, there is a plethora of functions for almost the same task, their naming is absolutely arbitrary, things like $hash[-1] fail abysmally, this:
[pre]
function MyArray() {
return array('de'=>array('eins','zwei','drei'));
}
// That would work in any decent language I know,
// in PHP it doesn't
$DE_MyArray=myArray()['de'];
$DE_MyArray=array('de'=>array('eins','zwei','drei'))['de'];
// With PHP you have to do this:
$DE_MyArray=myArray();
$DE_MyArray=$DE_MyArray['de'];
[/pre]
Scoping of variables... I could go on for ages. Most of the annoyances I haven't written down, but argued over verbally with my coworkers.[/pre]