Deprecated - Drupal core

I am at barcamp and I have a guy sitting besides me who seems to know PHP -- runs under the name "Rasmus Lerdorf" -- and I demo'd split to him. Results are: Drupal HEAD core eats 6 megabytes, with split it eats 1.5 megabytes on admin/modules. We divided memory usage of every module by filesize and there seems to be a very constant 5-6 multiplier. This means that if you have 8 megabyteslimit then you can install another 3-400K of modules. Rasmus says that memory usage won't be seriously affected by APC.

With APC I need to benchmark performance but it seems that split is cool!

As a novice developer of drupal i'am not able to understand from where to start to go through the code.
i started from index.php i'm not getting where menu_execute_active_handler() is implemented.plz give me a overview from where to start to go through the code

For the last few years I have been using Nucleus CMS. I switched to Drupal because Nucleus lacks some functionality I need for a new website (social networking type stuff).

Drupal and Nucleus are both PHP on MySQL. Drupal is promising and forward looking, but still has lots of frustrating unresolved issues. Nucleus is much more stable and transparant.

Couldn't Drupal and Nucleus work together? Exchange code? Even merge and build the ultimate PHP/MySQL CMS for "web 2.0"?

Hey, not sure if anyone is interested in this... but I didn't want to ask my host to give me lock tables permission, so I instead wrote an atomic db_next_id replacement that does without it....

Enjoy!

How do I apply a patch to Drupal to my personal copy of Drupal? I don't have CVS installed on my server, and I don't have command line access.

I guess what I need is a link to the .patch file syntax so I know what it means and can apply the changes manually (unless there's some other way to do it).

One of the difficulties faced by almost all Drupal newcomers is the "how do I structure my site" question. It's easy enough to say that taxonomy solves all of their problems, but that's not quite right.

To achieve the navigation system most users are familiar with in 'traditional' sites, it's necessary to set up a navigation taxonomy, custom paths for each node, and custom menu entries for both navigation blocks and breadcrumbs. path.module and menu.module do a good job providing this core functionality, but it takes a few weeks or months of fiddling with Drupal to realize this.

For paths, the excellent pathauto module does a great job of mapping node and taxonomy rules to custom url paths. In 4.7, the integration of menu on the fly will also help put custom menus in the forefront. There are still a few hitches, though.