Is redirect_canonical() the hotfix for wp->query()? Two are candidates for a refactoring anyway.
-
Defective by Design - HTML5 is so awesome you can screw it now. Congratulations. Tell W3C: We don't want the Hollyweb! - Get educated and spread the word! -
Issue 2.1 is out! (; as print version so far, not yet on the website.) Take a look at conferences and events to get as well all back issues of Libre Graphics magazine with a discount or just order online. -
Wordpress Licensing – hakre on wordpress- GPL: This Deserves a Special Mention, II
- b2/cafelog is GPL
- WordPress Changes GPL License Text Again
- Akismet Introduces GPL Version to WordPress (Updated 3x)
- Kses, GPL, Copyright, Licensing and Disclaimer
- WordPress, Copyright, Hello Dolly Lyrics, the GNU GPL and I
- WordPress Licensing Issues – Plugins are GPL, Right?
- WordPress Licensing Issues – On Showing License
- Relicensing of IXR – The Incutio XML-RPC Library (Day 15)
- WordPress Licensing Issues – NOOP (Day 8)
-
- Wordpress Questions (and Answers)
- An error has occurred; the feed is probably down. Try again later.
hakre on wordpress 
why do you think $wp_query need re-factoring ? is it because this global variable become too powerful and control too many segment of wp engine ?
Well in my eyes it looks like the function is the opportunity to write down how something should work w/o a concept of what exactly should be done.
Over the years that led to complexity (that’s totally normal). So when you look for stuff to be re-factored (simplified, better structured), you take a look for complex functions first. Because it might be the case that those things have a lot of potential to be made less complex.
WP::query() is one of the most complex functions in wordpress.