06-14-2009, 09:38 AM
|
#7 (permalink)
|
|
The Contributor
Join Date: Nov 2007
Location: California
Posts: 82
Thanks: 0
|
1. PHP is not a truly Object-Oriented Language
Is any language a true OOP language - sure, in some languages, everything is an object. But is that Object Oriented Programming?
PHP has become a matured language, and has a full range of OO, including reflection.
2. PHP Encourages Sloppy Code
PHP encourages flexibility. If you're sloppy dev, you'll write sloppy code no matter what language. I've seen it, in Java, C, Python. It comes down to the developer.
3. PHP doesn’t follow MVC
Of course not, PHP isn't a framework. I'm assuming the author of this question is a RoR follower.
Frameworks follow MVC, if you count Ruby on Rails as a programming language, you are sadly misinformed. RoR is a Ruby framework.
PHP has countless MVC frameworks. You _CAN_ do true MVC in PHP. Is it suggested? Not really, MVC frameworks are generally slow and have problems scaling. This is an issue inherited by the pattern, not the language.
4. PHP is slow because it’s interpreted
Incorrect, PHP can often out perform in execution of like logic in other comparable languages.
5. PHP doesn’t have a good IDE or Debugger
Misinformed.
Try some good IDE's, like Zend. and as it's been said, xdebug.org - one of the best debuggers out there in the industry. PHP also has quiet a few native debugging tools, including performance functions built into the language.
6. PHP apps all look the same
... uh.. what? That's like saying all cars look the same because they all have 4 tires and at least 2 doors.
7. PHP isn’t really for “serious” developers
That would be an insult the the developers I work with, that come from companies like: EA, Google, Yahoo, Lucas Arts
8. PHP is only good for web applications
PHP excels at web applications, but can just as easily be used for CLI, and extended to the desktop with GTK+.
I've written kiosk software entirely with WAMP stacks simply because it was affordable, scaled, and straight out worked.
9. PHP code is a mess of “include” and “require” statements that break easily
If you mean they break because as a developer you're not aware of what 'include' and 'require' are intended to do, then sure, yeah. It's the same process a dev has to go through to get their compile include paths set up in any C/Java project.
10. PHP Code is rife with in-line SQL statements
Only if you want it to be.
|
|
|
|