MT3 Perspective.

<p>Since <a href="http://www.sixapart.com/corner/archives/2004/04/wheres_the_beef.shtml">the release of MT into beta testing</a> there has been quite a furor from the community, much of which really bothers me enough to actually come up for air and make a weblog post. </p>
<p>Many of these missives I&#39;ve read do not take into consideration a number of things are come off as being rather reactionary and unforgiving for a what has been a relatively good track record so far. </p>
<p>I&#39;m not an apologist. I certainly have a number of gripes and quite a bit of frustration with SixApart these days, but I&#39;ve chosen to try and be more constructive with them and keep things in perspective. I suppose its that perspective that I don&#39;t rant &#8211; at least publicly. My professional background is in corporate IT and Internet services that this seems all typical and to a degree expected. (The stories I could tell about Microsoft, Sun, IBM, Macromedia, and Vignette!) Does it still suck? Yes. Do I expect better from SixApart? Yes, again.</p>
<p>Many of the posts I&#39;ve read don&#39;t seem to acknowledge that Six Apart is a real business now and what that means. Besides end users and developers they have brought on the added dimension of investors needed to continue. Having been involved in multi-million dollar contracts negotiations and done some investor relations work, these relationships are highly complex (lawyers!) and expectations of the investors quite high. </p>
<p>Not everything can be open source because developers have to eat too. (I&#39;m ecstatic to have access to the code after a decade+ of working with systems where I had no access and was beleaguered with limitations and bugs I could do nothing about.) Ben and Mena could not humanly meet the expectations of the growing user base themselves and hiring people costs money. It also takes time an effort to get new developers worked in and going. Of the posts I read none of them acknowledge that a significant part of the coding is being done by a new employee, <a href="http://www.ezrakilty.net/ezlog/index.html">Ezra Cooper</a> and not Ben. I sense the design and HTML was still done by Mena, but could be wrong.</p>
<p>Perhaps 3.0 isn&#39;t deserving of the <q>dot 0</q> label, but I could argue otherwise so its a grey area. The real problem is that the lack of updates to MT has created an anticipation that did not forsee or properly address through their communications in order to manage these expectations. It is here were the <q>radio silence</q> has been so damaging. I can only hope they see how damn important this is going forward and make it a priority and not an after thought as they have. They make a tool of collaboration and communication after all!</p>
<p>I think calling the reaction of a few to MT3 an <q>exodus</q> is quite an overstatement. Users and software systems&#39; paths diverge over time that sometimes a switch is in order. Its a natural part of software ecosystem and not anything to be upset about or take it as the sky falling chicken little. Its going to happen. I&#39;ve been involved in the MT community since version 1.2 and I seen a lot of users switch from MT to another for various reasons only to be replaced by 5 new happy users. </p>
<p>This biggest issue has nothing to do with software. While I disagree with or think much of this post and the ones it links to are bogus, <a href="http://www.patchworkprogression.com/archives/2004/04/28-the-sting-of-mt-30.php">this point from patchwork progression</a> says it well: <q>Six Apart seem increasingly unresponsive to end users, particularly with respect to communication. We feel resentfully slighted.</q></p>
<p>This has been especially disheartening and frustrating for me since <a href="http://www.appnel.com/">my primary source of income</a> since laast May has been MT consulting. So I would add developers and not just leave it at end users. </p>
<p>I had hoped for more <q>wow</q> features in MT3, though mine are quite different then many of those then has been voiced. Les at Stupid Evil Bastard rightly <a href="http://stupidevilbastard.com/archives/2004/04/22/my_thoughts_on_movabletype_30.php">points out</a> about the enhanced plugin architecture <q>this may be MT3&#39;s saving grace in some respects.</q> Later he states <q>the new plugin API gives good reason to hope that third parties will put out some amazing new plugins that shouldn&#39;t require any hacking of the code so perhaps the best is still yet to come.</q> (His comments on the patchwork thread are the most reasonable along with Adam Messinger.)</p>
<p>That is why as a developer I&#39;ve found it confounding that communications with developers is been scarce &#8211; some might even say no existent. Even with funding and staffing up, it will be impossible for Six Apart to address all of the varying and often conflicting needs of their increasingly diverse user base. The only reasonable way to address these needs is through a strong developer community though constant communication, feedback and knowledge transfer. Of course I am highly biased and will just stop here on that point.</p>
<p>I&#39;m still optimistic though not thrilled with MT3 and think there is tons of untapped potential for the tool that has yet to be explored. For the nature of the work I do I&#39;m still convinced that MT suits my needs and my clients well now and going forward. Until that changes I will continue to recommend MT.</p>
<p>Back to work.</p>