> -----Original Message----- > From: Benjamin Morel [mailto:benjamin.mo...@gmail.com] > > One gain that's very often overlooked on this list, is teaching a better PHP > to > new generations. It IS confusing if PHP has more than one way to do one thing,
Not directly related to this RFC but out of curiosity - where does this "doing the same thing in multiple ways is confusing" comes from? (I mean this as serious question) I had the impression that programming in essence is all about that - achieving/accomplishing something/the same different ways? Because then you have to question a lot of things (not saying it's a bad thing) - like for example why does heredoc <<< (or nowdoc) exist when we have =, .= (also probably won't be found in most if any popular/public projects, libraries) and so on.. (While extreme) then dropping PHP just because there are 10 other programming languages that do the same thing (or even better) also becomes an argument because it is kind of "confusing for new generations" to pick and choose which one is better (Which one is more easy? Which uses less system resources/is faster? Where do you get more salary as employee? Etc)? p.s. sorry for offtopic rr -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
