Comments on: How WordPress Spoils Developers

By: import this. » Blog Archive » Spoiled by WordPress

import this. » Blog Archive » Spoiled by WordPress — Sun, 18 Feb 2007 19:16:50 +0000

[...] at The NeoSmart Files, they explain how WordPress spoils developers: …but every single time it boiled down to WP: No matter what the program, audience, or goal, [...]

By: News - Software Headlines

News - Software Headlines — Sun, 04 Feb 2007 02:17:00 +0000

[...] Z. | 2007/1/31 21:59:26 A principios de enero, alguien en neosmart publicaba un artículo llamado Cómo WordPress malcría a los desarrolladores, en el que planteaban una posición que probablemente muchas personas ya habían pensado pero que [...]

By: WordPress y Habari — yukei.net

WordPress y Habari — yukei.net — Thu, 01 Feb 2007 03:59:59 +0000

[...] principios de enero, alguien en neosmart publicaba un artículo llamado Cómo WordPress malcría a los desarrolladores, en el que planteaban una posición que probablemente muchas personas ya habían pensado pero que [...]

By: king game

king game — Mon, 29 Jan 2007 01:38:45 +0000

thanks

By: Is it time to Habari? · Emporium Blog

Is it time to Habari? · Emporium Blog — Fri, 26 Jan 2007 12:42:22 +0000

[...] you like to know more, this article is a good read too. Not to say it’s impossible, but Wordpress has it’s monopoly and [...]

By: Kisakookoo

Kisakookoo — Tue, 23 Jan 2007 18:16:06 +0000

Hi! Why I can’t fill my info in profile? Can somebody help me?
My login is Kisakookoo!

By: Open Letter to The Guru « Habari Wank!

Open Letter to The Guru « Habari Wank! — Sun, 21 Jan 2007 22:47:51 +0000

[...] likes a turncoat. I won’t trust you until you have a Habari tattoo. I DON’T CARE IF WE DON’T HAVE [...]

By: Why Habari? at The NeoSmart Files

Why Habari? at The NeoSmart Files — Sat, 20 Jan 2007 09:24:25 +0000

[...] forever – even though it isn’t. WordPress is my first-love when it comes to blogging, you may have noticed. But yeah, I left WordPress for Habari [...]

By: Jacques Distler

Jacques Distler — Fri, 19 Jan 2007 17:10:59 +0000

Being open-source is of dubious benefit if the developers are not responsive to submitted patches. Yes, you can always fork the project. But the costs of doing so are high.

I found MovableType’s developers infinitely more responsive to my patches and suggestions than WordPress’s developers. Admittedly, I’m something of an outlier, doing XHTML+MathML, so my needs may be viewed as “too specialized” by the WordPress team. Still, that doesn’t explain why MT (a commercial project) should have proven more accomodating.

I admit that I more-or-less gave up on trying to develop for WordPress after 2.0 came out. Perhaps things have improved since then. Still, I find it a little hard to credit its purported status as developer-nirvana.

It’s lite, XHTML-valid, and looks great

It’s not even well-formed (much less valid) XHTML. Not that anyone cares, but please …

By: The WordPress Community · Episode 18: Habari, WordPress 2.0.6 released, WordPress 2.1 enters Beta

Thu, 18 Jan 2007 21:50:23 +0000

[...] The NeoSmart Files offered some gushing praise of WordPress, calling it, “Undoubtedly the single most influential tool in the blog-boom, WordPress has [...]

By: Educated

Educated — Mon, 15 Jan 2007 01:38:44 +0000

WordPress: Market Full, Competition Unrivaled

We all know that WordPress is pretty much the best (or at least best open-source) blogging platform today. It costs you practically nothing to use it (on WordPress.com, it’s absolutely free), and all you need to start blogging, not counting the t…

By: Habari at K2 DK

Habari at K2 DK — Sat, 13 Jan 2007 23:37:46 +0000

[...] i organisationsstruktur og ejerskab. Du kan selv læse mere på de respektive sider, for eks. Neosmart: How WordPress Spoils Developers, Neosmart: A Clarification on WordPress og DrBacchus: [...]

By: CorKy.NeT Feeds

CorKy.NeT Feeds — Tue, 09 Jan 2007 19:52:54 +0000

[...] I ran across a post by Matt Mullenweg, the developer of Wordpress, linking to a rant about how Wordpress ”spoils" developers. Behind this diggable title is a confused argument that Wordpress is so good that (a) it makes [...]

By: DrBacchus’ Journal » Meritocracy

DrBacchus’ Journal » Meritocracy — Tue, 09 Jan 2007 16:40:07 +0000

[...] talk about whether Habari will crush Wordpress are really beside the point. The real issues are whether we’ll produce a compelling product, [...]

By: Computer Guru

Computer Guru — Tue, 09 Jan 2007 11:34:49 +0000

I agree Arvind, Movable Type is an excellent platform, with awesome staff. But the fact remains, while you guys may influence a couple of decisions or more, every single day developers and users alike influence WordPress in the WP-Hackers mailing list. The only thing that puts normal users off is the fact that it's a mailing list, not a forum. But almost all new features and aspects are discussed there before they ever happen, and users have an opportunity to shape WP daily.

However, it's not all in the users' hands, even in WP. The best known example is perhaps when Matt single-handedly blocked a motion to add inline PHP documentation to WordPress & its functions for no reason. He did later (just last month) allow it, but I guess it kind of defined where and how decisions are made.

To be fair, most Matt and the rest of the Automattic team are generally open-minded and are constantly polling the users' and developers' opinions on Matt & Ryan's blogs, and the WP-Hackers mailing list. At the end of the day, you can't really deny that users in general have more influence over an open source project than a closed source one. I don't for a minute claim that MT is close-minded or a bad platform, to the contrary, I only have praise for MT - it's just that I have more praise for WP though.