Month: January 2013

GPL / WordCamp Twitter Drama Wrapup

Posted on by David Bisset

Interesting day. It all started with Jake Caputo’s Automattically Blackballed post and Twitter exploded (or resurged, if you prefer that term) with debates over GPL and who can (or who no longer desires to as a result) sponsor or speak at official WordCamps. This blog post isn’t to share my views (so if there’s more below of one side vs. another, it’s just concidencse). I simply am sharing the best tweets of today.


https://twitter.com/carlhancock/status/293788737366798337
https://twitter.com/ryancduff/status/293790291356442624


https://twitter.com/wonderboymusic/status/293794595261804544


https://twitter.com/trepmal/status/293795268745388032


https://twitter.com/ryancduff/status/293807585017073664


https://twitter.com/ryancduff/status/293820522448424960


https://twitter.com/MacManXcom/status/293863675197026305
https://twitter.com/chip_bennett/status/293872915919822848

My Take On WordPress and Application Frameworks

Posted on by David Bisset

After reading Justin Tallant’s well written thoughts on why WordPress is not an application framework and Chris Lema’s response, I decided to quickly jot down my thoughts on the subject. I work with a number of programmers that are experienced in a number of different levels, so I have heard Justin and Chris’s side before. I think you should read both posts, as they are interesting reading for debate.

As a freelancer, I do projects in WordPress and CodeIgnitor (either/or but sometimes together). I can understand where both sides are coming from. However Justin’s viewpoint that WordPress should stick to being blogging software makes just as much sense as requiring the use of CodeIgnitor or Rails for only “complex” or (fill in the blank here) projects. Both corners have their pros and cons – hence why i use both of them – but to paint WordPress into a general bucket of “blogging” or “CMS” is limiting and lacks imagination.

Justin’s viewpoint is not unique – I know many people that primarily code in Rails, CI, or another PHP framework that think WordPress is great – but great only for blogging and that’s about it. “They should stick to that” is the general mentality.

I also know other people that want to use WordPress for literally everything when either (1) Custom PHP Framework would be more flexible/make more sense and/or (2) those people don’t have the coding snuff to properly tweak WordPress into what they need and it ends up biting them or the client in the end. These people also need to know their and WordPress limitations.

I personally predicted months ago that there’s going to be a lot more talk in 2013 about “application development” (which is vague really) and WordPress. About WordPress sticking to what it does best – and if/when/how it should expand. About WordPress being bloated software and others discussing how efficient it is. Looks like i’m right on these predictions so far. We aren’t even seven days into 2013.

The fact that mobile has taken center stage and that applications are such a hot topic (some say blogs aren’t as cool as they used to be) I think is putting WordPress under the gun a bit. Could PHP frameworks and Rails do things that would be difficult for WordPress to do? Yes. But could a lightweight developer approach Rails as easily as WordPress? Probably not.

Final thought: Discussions are great, but actions speak louder. The best way to shape the WordPress future is to get involved.

Copyright ©2023 David Bisset