Comments on: Not so Judicious capital_P

By: John Blackbourn

John Blackbourn — Wed, 14 Jul 2010 21:45:19 +0000

I didn’t comment on the capital P issue, I commented on your unfounded remarks about Matt.

By: Gil Rutkowski

Gil Rutkowski — Wed, 14 Jul 2010 20:38:32 +0000

If you don’t feel strongly enough to comment on it, then why did you comment on it? #justsayin

By: John Blackbourn

John Blackbourn — Wed, 14 Jul 2010 19:28:19 +0000

Oh get over it. You seem to think that Matt is the beginning and end of this issue. He has given numerous responses to this issue on the wp-hackers list about this issue. I don’t feel strongly enough about the issue at hand to comment on it, but remarks like this are completely unfounded and completely unnecessary. Put your effort into something productive.

By: Paul

Paul — Wed, 14 Jul 2010 18:26:55 +0000

Hi Gil

I want to say 2 things.

First, I want to say thank you for reopening this ticket
http://core.trac.wordpress.org/ticket/13971
( I don’t know how this would end but it’s good to know there are people who stand up and do the right thing. )

Second, this is clearly not about the coding standard or else that matters.
It’s purely to serve Matt’s egoistical part, nothing more or less.

Look at this message from the About page of wordpress.org

“Everything you see here, from the documentation to the code itself, was created by and for the community. WordPress is an Open Source project, which means there are hundreds of people all over the world working on it.”
http://wordpress.org/about/

and here below is what Matt wrote 3 years ago

“WP has never been driven by committee, or voting, and I personally think that approach tends to create bland, soulless software.”
Matt ( @ticket#4254 )

and look what’s happening now in ticket#13971

I don’t know what all the core dev are afraid of here.
What hold you back from doing the right thing ?

By: Gil Rutkowski

Gil Rutkowski — Wed, 14 Jul 2010 15:49:58 +0000

Tom,

I think, by and far, the TEAM does prioritize good code and performance over everything else.

Several core contributors have quietly commented about this and other similar subjects — but they find it difficult to openly speak out and I don’t blame them for keeping quiet. They’ve seen what happens to people when they speak up.

By: Gil Rutkowski

Gil Rutkowski — Wed, 14 Jul 2010 15:42:03 +0000

Someone has to … When things like this become the norm in a community project, there has to be someone willing to relentlessly push back.

From a technical point of view, WordPress has become an amazing project. From a community point of view, it’s in dire need of help.

By: Tom

Tom — Wed, 14 Jul 2010 05:14:27 +0000

Thanks for blogging about this issue. You see it in the same way I do – in fact, I really don’t understand how there is any other way to see it! I hope the WordPress team fix the “bug” soon: http://core.trac.wordpress.org/ticket/13971 . It makes me mad that the WordPress team don’t prioritise code efficiency and performance over everything else.

By: Robert

Robert — Wed, 14 Jul 2010 03:46:32 +0000

Why are you putting so much energy into this? It stems from Matt so it will not be reverted. Period. That’s the essence of “benevolent dictatorship”.

By: Gil Rutkowski

Gil Rutkowski — Wed, 14 Jul 2010 01:35:40 +0000

Thanks, Ben.

It really is pretty silly that I even need to point this type of junk out – it’s code that would have been punted if it were submitted by anyone else. At this point, I’m sure it’ll stay in the core JUST because they can’t admit being in the wrong.

By: Ben Cook

Ben Cook — Tue, 13 Jul 2010 22:48:43 +0000

The fact that they realize a change is needed, but are STILL sticking to their guns on this egotistical issue is actually surprising to me.

If you admit there’s a problem, why not remove the filter & put it in a plugin? There’s just no feasible reason for this at all.

And I love the irony that the idiotic filter breaks its own code when trying to share it’s own code lol. Well done.