Meh. While webchick's post was surely written with the best intentions, it's not hard to misinterpret it and guess what? someone did and posted it to ZDnet as "Perfectionists need not apply". I do not want to say bad things about ZDnet but... well, even when it's a blog, it's typical journalism and let it rest there. My fellow perfectionists, we do need you. It requires a lot of tenacity and striving for perfectness to get a patch into core -- just let the community help you achieve that and do not work in isolation. You should strive for the perfect solution but do not hesitate to show the world the stages leading there.

Long after the first GHOP is finished, we still see new blood coming to Drupal -- this time, the fathers of the GHOP wonderkids! We were all awed by Deadwood but in all honesty, I believed boombatower took on a second nick just for the fun of it. I was proved wrong when his father, Jim Bery showed up at DrupalCon -- and he said he now does Drupal in a professional capacity. And yesterday, a small issue got committed -- filed by Charlie Gordon, coded by his father.

We are not like that currently. We are driven by forms. We are freely mucking with database tables belonging to other modules. Following David Strauss' call, I made sure that in Drupal 7, fields can be stored anywhere, not just SQL. Think CouchDB or Amazon SimpleDB.

I can not even guess what drove James Walker to have a talk like he had at DrupalCon DC. It's full of false information, half-truths, false expectations and the like. I am trying to refute a few of his claims (where I could find a factual claim to refute). I am addressing this post to him. Also note that it might not make sense without the video.

Although it's posted in the paid services forum, I think we should collect strategies to this question here.

I have my hands in many parts of Drupal and for some time now I make concious effort to make sure things would go fine if I disappear or something. Not that I want to leave the Drupal project, not at all, but you never know what happens.

Not for the faint of heart but I have Drupal that boots without SQL using memcached. It's fast. Very. If you have a focused site, you can gain from running a code coverage script and moving everything to conditional includes that's not used on the focus-pages. You can easily get several hundreds of requests from one small machine.

Again I need to use my blog to answer some really bright guy who thought that the world would be poorer if his wisdom would not pollute the Drupal Planet. He is wrong: Drupal is not WordPress. We do not make compromises in security design. Any ways of updating/installing a module on the webserver which does not ask you a password does make such a compromise. Now, Drupal has an auto update but it stays secure. Joshua Rogers took on implementing that under the name of Plugin Manager as a Summer of Code project. He stayed with us and develops it. There was a call for core inclusion. A port has been made by swentel. What more do you want? I know what I want: Plugin Manager in core. Care to help?

Thanks to Hagen who uploaded Dries' talk at DrupaCamp Koln 2009 to blip.tv. (His link made the video a bit hard to find so I posted direct links)