This is not documentation. This is literally the 30000ft high (I have written it on a Calgary-London flight) overview about Drupal 8 page flow as it stands on July 28, 2012. This doesn't mean it will be fully valid even a week later. Also, I am not writing out all the namespaces for classes, it's not necessary.

Two weeks ago I posted two brain teasers about extending ReflectionClass. Let's see the results -- after the break so people not having fun with them yet can.

Progress on what? Glad you asked... let's first go through a few important concepts:

Entity

If you have ever tried EFQ Views and it didn't work you might've thought it does not worth filing an issue because it was abandoned. It is no longer. Please file an issue telling me how it didn't work. Thanks.

Starting May 1, 10gen, the company developing MongoDB will pay me to make Drupal more MongoDB friendly. This will, in the shortest term mean a new release of the mongodb module and the EntityFieldQuery Views backend module. Longer term, I will try to help Drupal 8 make MongoDB friendly.

When we moved to git, at last year's DrupalCon NA in Chicago I asked dww to let me set up a bzr-git two-way mirror on drupal.org He said no, this is what it is, get with the program. As months passed, I have learned about git reflog and git log -S and git blame --reverse and git and I became uneasy friends although I still consider rebase the work of the devil itself. Similarly I disagree with a lot that's happening on the WSCCI side of the core development but what I am taking home from Denver DrupalCon: that's what it is and I will get with the program. I will resume core work to make sure the OOP-ifying of Drupal is done throughly and the render arrays of doom disappear from Drupal 8. Do it or do not, there is no try, and the community decided to do so I must help it doesn't become a try. See you in http://groups.drupal.org/drupal-8-blocks-layouts-everywhere-initiative http://drupal.org/node/1499460

I wrote a blog post some 1.5 years or so ago and everything I predicted is happening. However, I have revised my stance on them. Please, buy Apple devices. Please. You are giving me job security by driving up demand (by more relying on servers, these days fashionably called "cloud") and keeping the supply low (by raising a generation of computing-consumers who can't code). That freedom gets lost? I can't stop it so better be practical about what's going on.

While surely time clocks worked well for an assembly line worker, I have always found the push to clock my hours similarly rather annoying and this puncher makes me froth with rage. It's all sorts of wrong to force a creative person to work on an hourly basis. First, if I am able to solve something quicker, am I to earn less...? Worse, if I take a long time, perhaps even miss a deadline then you are to pay me more??

Two years ago I wrote a blog post about why not to use github. I simply was wrong. As jQuery won the JS framework war so did git won the DVCS war and one of the reasons is actually github. I have been using github to host private projects for my clients and the service / workflow is really top notch -- fork from the UI, hack, send a pull request, comment the diff line-by-line, do the minor fixes in the online editor on spot, click the merge button, done. Nicely done.

Private files are great but they are a huge resource hog. In certain scenarios, lower-resolution versions of the pictures are absolutely fine to be public, only high resolution originals need to be protected. In this case you can use Drupal's private file handling as it is and the following simple trick to make a style public.