Official Support For PHP 4 Ends
Da Massive writes with this excerpt from ComputerWorld:
"For a technology that has been in stable release since May 22, 2000, PHP 4 has finally reached the end of its official life. With the release of PHP 4.4.9, official support has ended and the final security patch for the platform issued. ...With eight years of legacy code out there, it is likely that there are going to be a fairly large number of systems that will not migrate to PHP 5 in the near future, and a reasonable proportion of those that will not make the migration at all. For those who are not able to migrate their systems to the new version of PHP, noted PHP security expert Stefan Esser will continue to provide third party security patching for the PHP 4 line through his Suhosin product."
PHP 4 was released in 2000 and is finally getting an EOL date but is still going to receive patches. Microsoft XP was released in 2001 and its EOL date is 2009, with security patches until 2014. So you have two products with the same span of product life, and still going to have patches for security. Very poor trolling indeed.
The Revolution Will Not Be Televised
Python 3 is still in beta. And python on the web? No thanks.
I felt a similar disturbance..
However, I perceived that it was as if millions of underachieving non OO toting PHP devs (professional internet browsing technicians) suddenly cried out in terror and were silenced
I record my sleeptalking
There are many 1000+ page books on the subject.
I've read a few and they left a bad taste in my mouth. They are usually anti-RDBMS in my opinion. There is a strong anti-relational streak in pro-OO literature.
More literate and intuitive api's
Those are often a matter of opinion. Different people think differently. What you find intuitive may not apply to others. Without specific metrics or clear-cut examples, I cannot do much with such statements, to be frank. I'd have to know what you are thinking and what you are mentally comparing to what.
Type safety.
OOP is not necessarily about type safety. An OO language like SmallTalk is very weak-typed. (Much OO lingo comes from the inventor of Smalltalk.) And heavy-typing versus light-typing is a long and bitter argument that is never settled, even excluding the OO issue. (If I was forced to use OO, I'd rather use Smalltalk than say Java or Eiffel.)
As far as MVC, I find it outdated and unnecessarily complex. OOP and MVC clingage is main reason we don't have a decent cross-language GUI kit yet. Non-trivial OO API's are very difficult to make cross-language. Nobody has solved this problem. But you are right in that such a debate is not something we can settle via mere slashdot messages.
But thanks for your feedback anyhow.
Table-ized A.I.