excessive profanity on the part of the kvetchers

Matt thinks Tarski must be ‘coded badly’ since it didn’t sail unproblematically though the upgrade to 2.1.

Apart from this being a complete non sequitur, if it sucks so much why did he put it on wordpress.com?

The original post is also good on the brokenness of the links manager in 2.1, as is this forum thread, notable also for the shock! expressed at the suggestion that negative comments might have been censored and the inevitable denial of any such thing. Bless.

(How long it it since Kvetch was launched now? And the world of wordpress is such a happy smiley place that there’s not a sufficient database of comments to show yet? Hmm. Shall we be charitable, and blame it on excessive profanity on the part of the kvetchers?)

9 Comments »

  1. adam said

    tarski is only ‘coded badly’ because it tried to fix the holes in wordpress that matt refused to acknowledge or fix. matt of course returned the favor by hacking those fixes right back out of the version of tarski we have here.

  2. Ah, so the answer to ‘badly coded’ themes is to hack all the meaningful code out of them so they become just another standard two-column blue and grey number with a big header. Makes sense. But also kind of makes you wonder: why not just hire someone to throw together a job lot of the things without inconvenient stuff like sponsors, owners, or functionality, and quit leeching off a theme community for which Matt clearly has nothing but contempt?

  3. Matt said

    I love the theme community.

  4. adam said

    if you love something, let it go.

    * don’t keep the reigns on wp-themes.org.
    * tell us how we should be normalizing our newlines, so that you don’t have to do it for us.
    * tell us specifically, and in detail, what causes features to be stripped from wp.com themes.
    * this may mean telling Ozh what, exactly is wrong/insecure about his theme options toolkit.
    * stop picking themes willy nilly as they fit your whim. pick them out of the most-downloaded and top rated themes on themes.wp.net (or themebot, or wherever).
    * follow through on directives like “anyone developing a new theme [should] try to build it on top of Sandbox”
    * if widgets are going to be core at some point, it shouldn’t be that hard to find the place to file trac bugs with them. and they should never have been as defiant of their own API as they were.
    * stop pretending like it’s a crime for anyone who follows your API to release code as something other than GPL.

  5. Root said

    And Matt – For a new Mac or two, 40 K USD and a trip to Mexico (as long as I don’t have to dorm with podz :) ) even I would help you fix up the multiple css / positioning glitches; validation failures and general borkage for you. Plus I would introduce a common, template. I’d even go black (like in 24) so the shame of the climb down won’t damage the stock on Wall Street. :)

  6. […] flytrap indeed. matt thinks he loves theme designers. it’s baffling to me, then, why he feels the need to keep changing the titles and […]

  7. Joe said

    Yeah, that was my topic on the support forum, Matt has cleared up most of the questions when I started the topic fro my post on my blog.

  8. Root said

    That thing about Matt hacking back out the fixes. He has been at this for a long time since he messed in Classic and claimed a joint credit alongside one of the worlds leading web designers. It would be OK except he hasn’t got the first idea what he is doing.

    As to sites being badly code WP never exactly set any kind of standard by example did they? Do we remember the multiple borks at the Alex King Theme Site? Do we recall the thread from hell when Kubrick came out of left field? Matt would like to move on no doubt. But we have er memories. Funny that.

  9. Ah, the Alex King style contest. He keeps the link to that rather obscure since he redesigned his site. Perhaps he is embarrassed by Dots ;)

RSS feed for comments on this post · TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s