14 Comments

  1. Owen

    What a great post, and I hope the WordPress team end up reading it. The best way to improve something and to maintain leadership is to be aware of what risks exist and have plans on how to counter them. I think you’ve done a great job of identifying these and hopefully this will help WP remain the blogging platform of choice for millions (in my head everyone should use WordPress ;) )

    Report

  2. Angsuman Chakraborty

    Nice article. Few thoughts:

    WordPress.com & Akismet is mostly free. It costs them a ton of money to maintain the infrastructure. How good is their cash position? In this climate of recession, their burn rate is what I would be most concerned about as VC fundings are harder to get.

    WordPress is not very cooperative (barely tolerates) with commercial plugin or theme developers and relies on people to donate their time & labor to the community only for free. Today we mostly moved away from developing WordPress plugins and down the road I am sure others will too. Let’s see how many people are as willing to donate their labor & time for free when the economy is crumbling all around them and the “day-job” of these moon-lighters may be at stake.

    Report

  3. Ryan Imel

    I’d say the only real “threat” is that someone else shows up doing it better. Aside from that, not much could rock their boat. Third parties come and go, but they came around originally because of WordPress’s success. Change in license couldn’t happen, no way. Anything else is just too unlikely to be concerned with. Matt is really young and (if his pictures are any proof) very healthy; he’s not going anywhere.

    @Angsuman Chakraborty – Also, they offer a premium service on WordPress.com, so there is some revenue coming through that project at least. Also, how should the WordPress team leaders be more cooperative to commercial WP developers?

    Report

  4. John (Human3rror)

    this is awesome. nice post.

    Report

  5. Jim Child

    Thanks for your thoughts, Jeff! You managed to put together a very concise consolidation of the “risks” that WP faces as time goes on.

    So now “we”, and that should definitely include the folks at WP/Automattic, have a list of things to watch out for. As a loosely knit community we can all make efforts to avoid the known pitfalls.

    WordPress Forever!

    Report

  6. jeremyclarke

    I was very pleased to hear Matt say in the special interview I conducted with him that the decisions he makes regarding WordPress.org are made with the community in mind. That is exactly what I wanted to hear.

    Not to say that Matt was being dishonest or anything, but watch out with that kind of language! Of course he’s going to say what you want to hear in public! The question is whether it really seemed honest and whether they are actually thinking of the community (which they are IMHO, they just don’t always LISTEN to the community, because they think they know better).

    Report

  7. tekzt

    @Angsuman Chakraborty – There is no need for WordPress to cooperate with commercial WP Developers. The developer would be the one who benefits through it, not wordpress or the wordpress community. They have their own developers who not only develop wordpress but also some of the plugins, which are considered “third party”, cause they are released by the persons and not through automattic.

    If they had money issues they would cut the wordpress.com-stats plugin for .org users which runs on wordpress.com and would remove pingomatic as a default service (or strip pingomatic itself down to a lesser server load). that would cut some major costs.

    Automattic doesn´t keep you from developing for wordpress. It´s very accessable for any developer. They just don´t want to host stuff of you if you´re an commercial developer and have link to your commercial site in the foorer. That´s perfectly ok with me, because even if the plugin on their site is free, it´s advertising. Just because its not on the wordpress site doesnt mean you can´t get word about your plugins out there.

    @jeremyclarke – That´s true, sometimes they forget to listen *coughtinymcecough*

    Report

  8. Six million ways to die: choose one - WP FUN

    […] million ways to die: choose one So Jeff wants to know how WordPress will die. Well, seeing as he asked, I will tell you. WordPress is already dead, its just that no one has […]

    Report

  9. Brad

    Security is my number one fear and the same for most I think. WP did have an exploit that let a lot of websites get hacked. I have a few clients that were hit (before my services of course :P) and lost all of their data.

    If WordPress suffers a larger hack that infects hundreds of thousands of websites I think most mainstream users will run horrified to another platform.

    Another good reason to stay current on updates :)

    Nice post Jeff, very thought provoking! Looking forward to the podcast tonight, should be frEAkY!

    Report

  10. that girl again

    Actually, I’ve always thought that the main reason MT got overtaken by WP was that PHP is better generally more user-friendly than Perl ;) If it hadn’t been wordpress, it would have been some other PHP-based platform. Budget webhosts were more likely to offer PHP support than Perl, and to offer automated installation of PHP software. The licencing screwup just speeded up the process.

    Therefore if another framework were to overtake PHP in popularity, wordpress would be dead in the water. I have no idea when that will happen but I find it difficult to believe that it never will. Anyway, I have my suspicions that either #4 or #5 will do for them before that happens.

    Report

  11. links for 2009-02-14 | This Inspires Me

    […] Six Ways In Which WordPress Could Die (tags: wordpress) […]

    Report

  12. Matt

    WordPress will be around and thriving long after I’m gone, and I’m only 25. :)

    Report

  13. Heißt die Zukunft von Wordpress Habari? | eliwagar

    […] verwiesen (klar, mal wieder Verweise *stöhn*, aber who the fuck ist Jeff?), der sich in seiner WP Tavern fragt, wie WordPress sterben wird. Er führt da sechs mögliche Szenarien auf: Third party […]

    Report

  14. Lastest News » Wptavern.com - A New Kid on the Block in the Wordpress community

    […] He doesn’t always agree with the decision made within the team. One of his posts foresees 6 ways in which WordPress could die. I cannot be more agreeable with the […]

    Report

Comments are closed.

%d bloggers like this: