The drop is always movingYou know that saying about standing on the shoulders of giants? Drupal is standing on a huge pile of midgetsAll content management systems suck, Drupal just happens to suck less.Popular open source software is more secure than unpopular open source software, because insecure software becomes unpopular fast. [That doesn't happen for proprietary software.]Drupal makes sandwiches happen.There is a module for that

PHP is also moving

Submitted by nk on Mon, 2008-08-04 07:19

As Drupal, PHP is also moving -- and it moves fast. On June 16 Christian Seiler suggested adding lambda and closures to the language and on August 1 the first alpha of PHP 5.3 containing this and more is out. And we thought the language will never get them...there are other niceties -- just one question remains, how long before Drupal can use this?

Commenting on this Story is closed.

On whose servers?
Submitted by Crell@drupal.org on Tue, 2008-08-05 04:18.

It depends when RHEL is released. If they include PHP 5.3, then 2 years. If not, about 7.

This is why long term stable software is not always a good thing! It holds back, um, everyone else.

Do I need to register GoPHP53.org? :-)

Then there is hope
Submitted by nk on Fri, 2008-08-15 08:46.

http://lwn.net/Articles/286874/ "It was also guessed that Red Hat Enterprise Linux 6 might not come out for some time and that it would definitely not be based on Fedora 9... but probably Fedora 11, 12 or even 13." Compare this with http://wiki.php.net/todo/php53 stable release between mid September and mid October.

As Fedora 10 is 2008-10-28 and Fedora 11 is 2009-04-01 I guess Fedora 12 is some time 2009 October. While PHP5.3 might miss Fedora 11, there is little doubt that it will be in Fedora 12... there is hope.

Writing Effictive PHP Caches with Memcached
Submitted by Anonymous on Wed, 2009-08-05 04:00.

When your website or project grows, demands on your architecture and infrastructure can dramatically increase once you've go through 642-446 exam and 000-331 exam. You can then run into "bottlenecks", or parts of your project that cap out their abilities, and cause the rest of your application to slow down. One of the more common parts of your architecture to reach its limits is your database. There is a reason for this: its called ACID. While I won't get into the details, basically databases are awesome because of it's "ACID compliance." You can store information and get information easily. However, these requirements of being a good database can also require a lot of leg work for your server. So when you have hundreds, thousands, and even millions of queries executing on your server, it can require a lot of CPU, Memory, and I/O to do all the work.
642-426 exam