So recently the WordPress plugin review team, and the WordPress meta team (the team responsible for maintaining wordpress.org and tangential properties like the plugin repo) have been talking about and making some pretty big changes, and it looks like some of those changes are starting to take effect.
The conversation came up internally at WebDevStudios, and I knew I have seen Ethan Marcotte, and/or Matt Marquis rant on it a bit before (I mean that in the best way), so I hit them up on twitter: .@wilto @beep do either of you (or anyone) have a good resource for “why you should care about disabled JS” that I can pass around?
Visit the post for more.
So today, I instigated a lively discussion on the topic of WP_Error vs PHP Exceptions. I’m curious why try/catch exceptions are rarely used in WP dev? Any insight?
The other day, I tweeted out that I believe there is hesitancy in the WordPress world to use autoloaders. Don’t believe me? I feel like there’s hesitancy in the WP world w/ autoloaders. spl_autoload_register is your friend. Namespaces NOT required.
Last year I wrote an “Intro to Post Meta” series of posts for wpsnipp.com. I highly recommend you check them out if you’re looking to learn how to use WordPress post meta. What is Post Meta? An intro to WordPress Custom Fields Post Meta.. How do I save it? Post Meta..