Thoughts on HTML Email

June 29th, 2009

So apparently an email marketing software development firm decided to directly address Microsoft’s woefully inadequate treatment of HTML email in Outlook 2007 and the impending 2010 by starting a Twitter campaign. Microsoft responded by basically saying that Word is the most awesome HTML email composition tool on the planet, that “there is no widely-recognized consensus in the industry about what subset of HTML is appropriate for use in e-mail for interoperability” (WTF?), and that since the whole thing was cooked up by an email marketing software company anyway, both the Twitter campaign and the Email Standards Project of which they are a major backer were worthy of complete and utter disdain (because ignoring and/or deriding third party developers is totally the way to win hearts and minds). If an email marketing tool developer can’t be trusted to lead a discussion on email standards because of their vested interest in the outcome, why should we listen to anything Microsoft says about computers?

Is it just me, or is Microsoft actively getting into the business of pissing off the people who develop tools and software for their platform? First they spend years ignoring the sorry state of the web that IE6 has left developers to deal with, put out a half-assed, still-busted update with Internet Explorer 7, and 3 years later followed it up with CSS 2.1 compliance and large amounts of mockery and derision towards CSS 3, HTML 5, ACID3, and the JavaScript performance race. Now they’re actively ignoring the fact that Outlook 2007 and 2010 display HTML emails worse than the ten-year-old Outlook 2000 by putting on a song and dance about the ability to use SmartArt and other Word capabilities when composing email.

In essence, Microsoft is completely missing the point of the Fix Outlook campaign. Web and desktop app developers trying to meet client demands for consistent branding in email communications are clamoring for improvements from Microsoft on the email rendering capabilities of Outlook. Microsoft on the other hand is trumpeting the capabilities of Word as an HTML email composer, and looking detached from reality in the process (”the best e-mail authoring experience around” is hardly the expression I would use to describe Word, especially when it comes to creating HTML).

Now, I know a lot of folks have really nasty things to say about HTML in email. For the most part, I agree, heavy HTML content isn’t something email should be used for. In particular, Apple’s stationary stuff in Mail is rather over-the-top (though its complexity does make Mail a best-in-show client for pretty much all HTML email handling, so that’s a plus). However, major corporations like banks and online retailers like to make use of HTML email because of the ability it provides to create visually pleasing, distinct messages with richer capabilities (ever gotten a shipping notice from NewEgg? The order info and tracking link are there courtesy of HTML, and it’s a lot easier to read and generate than tab-delimited plain-text “tables”) and branding that is consistent with the rest of their web presence. Non-profits and small businesses are replacing paper-based communications with email newsletters to save money. It’s these companies and organizations, and the developers who serve them, that Microsoft is not only ignoring, but being openly hostile toward by pig-headedly focusing on Word integration over standards-compliance.

And on the subject of Word’s advanced compositional features being built into Outlook, when was the last time anyone used Outlook directly for stuff like SmartArt etc.? Most people in the corporate world are application-oriented enough that I don’t think it even occurs to them that Outlook supports building complicated graphs and charts. These folks are going to do it in Word and attach it to a rich-text email because that’s their workflow. Anyone not in the corporate world is almost certainly not going to take advantage of the Word feature integration in Outlook, because really, who the hell would use it, and what the hell would they use it for? The whole thing seems like an effort on Microsoft’s behalf to further their vendor lock-in (since non-Outlook clients will almost certainly vomit all over Word’s fancy-schmancy complicated and completely non-standard HTML) and put an extra feature bullet on the back of the Office box.

I think the most mind-boggling part of Microsoft’s anti-standards screed is the argument that using IE to render HTML content is a major security risk. If that’s the case, the Trident engine still has a long way to go to catch up with the rest of the world, then. If disabling JavaScript execution, ActiveX loading, and defaulting image loading to “off” is something that the Trident control isn’t capable of supporting, the IE team loses even more points for not providing a powerful, flexible, and most importantly, secure tool for other developers to build into their applications. The Office team is making the IE team look incredibly lazy and unconcerned with security by making such a claim. Either it’s true, or the Office team is just really lazy and more interested in their marketing bullshit. Whichever it is, someone at MS is still apparently not on-board the secure and open standards movement that’s supposedly been sweeping the Redmond campus the past few years.

I guess all of this could be rendered moot if Word were able to generate and interpret standards-based HTML. Of course, this will happen the day that pigs fly and the Earth falls into the Sun, because Microsoft doesn’t give a rat’s ass about HTML compliance in Word. It “works”, and there’s no sense breaking something that “works”. If this requires another 5+ year campaign like what it took to get IE’s creaking, bloated carcass moving forward again, it’s going to be a cold day in Hell before I can use background-image in an email and have it appear correctly in Outlook.

Can we finally abandon the myth that Microsoft looks after its developers? Or that Microsoft is on the cutting edge of the web development platform? Or that Microsoft cares about standards? Because they don’t, they aren’t, and they most definitely have a vested interest in ignoring them.

Sliders?

June 23rd, 2009

I hope I’m not the only person to find the current fad among mid-range restaraunt chains (like Friday’s and Applebees) of calling mini burgers “sliders” just a little bizarre. Maybe it’s a regional thing, but growing up in northern Kentucky, sliders were a derogatory term for White Castle hamburgers, so named because of their unpleasant tendency to slide straight through one’s digestive tract. I’m really not sure what the marketing guys at these much less intestinally disruptive restaraunts are thinking with this line of advertising. Like I said, maybe it’s a regional thing, but still, “sliders” just doesn’t really sound like something I’d want to order for dinner anywhere reputable.

Anyway yeah, what’s up with that?

Still Crazy After All…

June 19th, 2009

So Digg and Reddit have been ragging on this for over a day now, but as a web developer, I thought I’d chime in with some longer-than-140-character comments on Microsoft’s new “IE8 is the most awesome thing ever invented” comparison chart. While the “reasons to install” page is fairly reasonable,  the comparison chart is complete and total bunk, and also tremendously condescending. Taking it point by point:

  1. Security - I’m tempted to give them points on this, since Vista and Win7 run IE in a super-restricted access mode. However, Firefox seems to be much faster in pushing out security patches when they’re needed, and neither it nor Chrome have such deep-seated access to the OS that compromising them has the potential to cause widespread damage to the OS. Also, IE’s restricted process mode isn’t available in WinXP, which I think is still the dominant OS by a wide margin. Further, IE8’s “ScreenFilter” (seriously, what’s up with the CamelCase features?) has already been implemented by Firefox, Chrome, and Safari. FAIL.
  2. Privacy - And so the outright lying begins. Both Chrome and the upcoming release of Firefox 3.5 have identical private browsing features (and in fact, Safari’s had it for years), and Firefox 3 even has an add-on you can use to gain this capability now without downloading the Fx3.5 beta. FAIL, Microsoft.
  3. Ease of Use – I have two words for you, Microsoft: Information Bar. This thing is a hyper-sensitive waste of my time and an extreme annoyance on a daily basis. Also, have you looked at your preferences screen in the past decade? Jesus Christ… Minor points for Accelerators (with deductions for stacking the deck with your other products), but Web Slices are arguably a complete waste of time, and the rest of the browser is just an absolute mess (good luck trying to uninstall an add-on by yourself, by the way… the IE dev team had to post a how-to on their site for that!).
  4. Web Standards – Yes, I will give you congratulations for finally making it to where everyone else has been for the past 5 years. You do at least deserve that. However, your ongoing dismissive attitude towards CSS3, HTML5, JavaScript performance, and the ACID3 test are not encouraging. To be sure, ACID3 is not a test of established standards the way that ACID2 is (and lordy did you crow about passing that one). However, passing ACID3 is about much more than meeting obscure draft standards. Look at the blogs that the WebKit developers posted in their race to beat Opera to 100/100; they mention making deep-seated performance tweaks and fixing long-standing rendering glitches in order to attain the coveted perfect score. ACID3 is as much a stress test of a browser’s existing capabilities as it is a future-facing standards test, and on both counts, IE is failing miserably, and getting thoroughly spanked by Gecko, WebKit, and Opera. The competition isn’t standing still here…
  5. Developer Tools - Now you’re just being insulting. Every web developer I’ve ever talked to considers Firebug and the Web Developer Toolbar the gold standard in web developer tools. WebKit’s developer tools run a close second (they’re a bit more tedious to use when editing content on-the-fly). IE’s developer tools are junk. Sure, they’re bundled into the browser, which I guess is good news for the <1% of internet users who do web development, but they’re clunky, it’s difficult to add properties or make changes to existing attributes on-the-fly, and the enable/disable style feature seems to be completely unreliable in my experience: changing a style in the developer tools, uncovering a “fix” for a rendering issue, and implementing that fix often results in a completely different rendering outcome than the one implied by the developer tools. FAIL again, Microsoft. And an even harder FAIL for slapping developers in the face with your crappy tools and saying we should be thrilled about them. And why is this on the consumer-facing facts list? What average computer user is going to care about this? It’s like advertising Visual Studio Express on the Windows 7 features page…
  6. Reliability - Another lie. Chrome supports both tab isolation and crash recovery (though not explicit automatic crashed tab recovery [which seems stupid... if a tab crashes, you're probably not going to want to automatically re-launch it, because odds are it's going to crash again], so you get a few points on a technicality), and both Firefox and Chrome are far more reliable than IE8 in my experience. You could possibly win points over Safari on Windows, but that’s like beating the kid in a wheelchair on a 100-yard dash. Uphill. Nobody’s going to give you any credit for it (yeah, Safari on Windows still has some stability issues, but I’ll still take it over IE any day of the week).
  7. Customizability – Now I know whoever made this chart is a complete idiot. For all its awesomeness, Chrome is hardly customizable, so I’m not sure why they tried to make it look good by giving it a check mark. That said, IE’s customizability selling point seems to be that Microsoft has already done the customizing for you. That seems wrong somehow (it also seems like something they enjoy accusing Apple of doing)… And they then go on to mention the 1700 add-ons for IE in the Mythbusting section (which I’ll get to), while simultaneously denigrating Firefox’s much larger add-on library. Can’t have it both ways, Microsoft. Major FAIL.
  8. Compatibility – I hate you so fucking hard… if it were up to web developers, IE would be the least compatible browser on the market, but we can’t exactly do that when it controls over 60% of that market and people expect their websites to work. And you have no idea how bad it looks to only give yourself a check mark for compatibility when developers are already building in progressive enhancements to support the more advanced rendering features in other browsers like CSS rounded corners and SVG canvas support. IE is only more compatible with SharePoint and ActiveX-reliant sites, and speaking from experience, I hate both of them, and want them to die in a fire. FAIL, FAIL, FAIL.
  9. Manageability - Finally, something IE can honestly claim to have the upper hand in: enterprise distribution and lock-down support. I would frankly love to see Firefox pick up some enterprise-level GPO support, because it would only further erode IE’s market share (what are the chances of the GPO controls being impossible to build into open-source software though? Possible dick move alert…). The biggest base of IE6 users seems to be corporate enterprise and the US Government (at least, that’s what everyone cites when defending IE6’s ongoing existence). Get Firefox 3 with the IE Tab add-on on every one of those machines and watch public IE usage drop like a fucking stone. And they’d never have to upgrade off of IE6 for their internal sites (this is how I use SharePoint at work).
  10. Performance – Please, this is just pathetic. From a usage standpoint, IE’s interface is painfully slow. Opening new tabs is glacial thanks to the tab isolation implementation that IE uses. And gods help you if you want to install more than a few add-ons from IE’s huge 1700-strong gallery, because they’re only going to make the problem worse (seriously, throughout IE8’s development process, the only fix provided by the IE team for slow application launch and tab creation was disabling your add-ons… that’s sure customization-friendly!). IE8’s JavaScript performance is at least a generation behind modern browsers, and the disparity is only going to get worse as web applications put a larger and larger strain on JS DOM manipulation, and HTML5+CSS3 take the place of Flash and Silverlight for most website glitz and glam. One more FAIL for you, Microsoft.

The Mythbusting page is just as bad…

  1. “Internet Explorer is much slower than Firefox and Chrome.” – Again with the speed comparison. They even link to a video that uses the phrase “as it turns out” to prove their point (a phrase which my favorite author, Douglas Adams, once said made it possible to prove anything without backing up your statements… I think we have a case in point here). The video does nothing but compare page load times… no JavaScript performance comparisons, no comparisons of actual operations within pages like performing drag-and-drops, not even a demonstration of their Accelerators (which is what I thought the video was going to be about… when it comes to speed, pretty much the only point that could be made in IE’s favor is Accelerators, because they’re certainly going to be useful to some… though the lack of Google-targeted Accelerators is probably going to deter their use for many, because Google is synonymous with everything from search to translation to driving directions). As I said before, developers and other browser makers are not standing still. IE8 may meet today’s JavaScript performance requirements (and I personally don’t think it even manages that), but it’ll be at least another 2 years before we see even the beginning of IE9, and by then, who knows where things will have advanced? IE is definitely not leading the pack as it so bizarrely claims (and unlike Apple, whose claims that Safari is the world’s fastest browser are still questionable, IE isn’t even in the running for second place).
  2. “Internet Explorer is less secure than Firefox. “ – I’m amused by their use of the phrase “catches almost twice as much malware”… sounds like an affliction the way they’ve worded it, but whatever. I also don’t think it’s wise to make a claim that you respond faster than any other browser maker to new threats when evidence to the contrary is easy to come by… even the NSS Labs report on malware blocking indicates that Firefox is faster to block new threats than IE8. Kudos on using a MS-written report on security fixes to back up a MS-written marketing blurb though, and points for being on top of malware problems. Is MS using a different validation system than Safari/Fx/Chrome? Would they be willing to share for the benefit of all browser users? (Fat chance there… this is like the only point they’re scoring on.)
  3. “Firefox is a richer, more adaptable browser than Internet Explorer.” – Seriously, you’re going to try and refute this claim? For real? Are you on crack or something? Even if I give you the point for having more features out-of-the-box, half of those features you think I want are things I turn off during the setup process (Web Slices, Suggested Sites, virtually all of the Accelerators because most are pretty useless to me…). The things I do want, like spell check and ad blocking, are things I have to go find an add-on for anyway. Let’s also ignore IE’s lack of a download manager, and their absolutely worthless developer tools (I can’t really even say they’re better than shooting blindly at the problem, because of aforementioned discrepancies between developer tools-made changes and actual implemented code). Further, their boisterous claim of 1,700 add-ons is totally smashed by Firefox’s almost 7,400. Hell, there’s more add-ons in Firefox’s “other” category than in IE’s entire library. As to their claim that IE implements “almost all of the features [in] the most popular add-ons in Firefox” (their words, not mine), here’s a list of the top 10 most popular add-ons on AMO:
    • AdBlock Plus
    • FlashGot
    • Video DownloadHelper
    • NoScript
    • DownloadThemAll!
    • Greasemonkey
    • Personas
    • Firebug
    • IETab
    • Cooliris

    Of those, I think IE implements Firebug (sort of), and obviously IETab. Yep, that’s totally almost all of the features in the most popular Firefox add-ons. Isn’t there some sort of truth in advertising requirement FAIL going on here?

  4. “Internet Explorer doesn’t play well with Web standards.” – Again, I’m willing to begrudge them a lot of points on this because they have come a long way even just from IE7, but they’re still not off my shit list. I spent a whole day building a new skin for DPWR in IPB3.0 and had to essentially reboot the whole damn thing because I hadn’t tested it in IE at the time (I was working on my Mac and didn’t want to have VirtualBox running), and when viewing the site in IE8 and IE8’s IE7 Compatibility Mode, the entire skin was almost entirely unusable (topic view especially was impossible because anything after the first post was simply missing). And this was after building it using validating XHTML code and CSS 2.1 definitions. AUGH!

I’ve harped on this before, but Microsoft seriously needs to get their shit together when it comes to IE. Rather than actually dedicate more time and resources to getting a quality modern browser on all fronts, Microsoft still seems to be taking the path of least resistance and over-hyping their accomplishments to the point of fabricating outright lies about the competition. Every other browser developer is pushing strongly into HTML5 and CSS3 territory while back-filling what are frankly tweak-level CSS 2.1 compatibility issues (I think supporting content:before and content:after on fieldset tags was brought up on the IE dev blog as an example of IE8’s awesome CSS 2.1 superiority… how many times have you needed to use that?), and pushing JavaScript performance into frankly obscene levels. Meanwhile, the IE team is trumpeting their support for CSS 2.1 (we’ve only been waiting for you at this party for 5 years now, guys) and deriding other browsers for focusing on JavaScript performance and supporting draft standards (when you’re already supporting the vast majority of the CSS 2.1 spec, there’s not much else to focus on but the future…). The problem is, IE is already still well behind the pack with IE8, and with IE9 easily 2-3 years away, they’ll be even farther behind on supporting those emerging standards and performance benchmarks, while every other browser will have them in spades.

Don’t even get me started on their mobile platform, which in 2010 will still based on IE6. Urge to kill… rising…

Getting DIRTy Again

June 1st, 2009

I came to the conclusion last night that Uru doesn’t work as an MMO (shocking, I know). First of all, it’s not profitable (at least, not quickly enough to justify its continued commercial development). Secondly, its style of play isn’t very well suited to an MMO… I don’t think this is Uru’s failing, I just think adventure games in general make for pretty crummy MMOs. Not every genre works equally well when you tack “MMO” in front of it.

So I started thinking about how to make a game like Uru actually work. What I came up with is sort of a hybrid between a traditional single-player adventure game and the MMO world of Uru, with a splash of TV thrown in for extra flavor (I swear, it’ll make sense once I explain it!). Beware, those of you well-versed in Uru’s ancient history may find portions of the following explanation tiresome. Because this is a really long post, I’ve put the rest below the fold for the sake of those reading MystBlogs… (I’d also like to apologize if it doesn’t make much sense. This kept me up until almost 4:30 AM, so I’m a bit tired…)

Read the rest of this entry »

Ugh

May 28th, 2009

It’s stupidly hot in the apartment, I’m exhausted, the kitchen smells exactly as bad as one might expect it to when cleaning out the fridge for the first time in 5 months, and I had entirely too much molé for dinner.

No wonder I feel ill…

(Incidentally, I’ve also concluded that certain pithy thoughts are still simply too long to effectively cram into Twitter’s 140-character limit. For some reason I find humor in the fact that this post will be auto-tweeted when I hit “Post”.)

Taking Internet Explorer Seriously

May 27th, 2009

I’ve been ruminating on this for a while, and I’ve come to the conclusion that Microsoft still isn’t taking Internet Explorer very seriously. Sure, they’re taking it seriously enough to continue development and make overtures to improved standards compliance, but let’s face it: Microsoft is not funding IE’s development because it wants to make the web a better development platform. Microsoft is funding IE only because browsers like Firefox, Safari, and Chrome are starting to seriously erode the monopoly that Microsoft held over the browser market for the better part of 5 years, and they want that share back. The problem is, this is precisely why Microsoft is still losing ground in the battle for browser market share: they’re doing it for the wrong reasons. In fact, Microsoft – and especially cheerleaders for the company -have been taking what seems to be an increasingly hostile role towards web developers who dare to argue that Microsoft isn’t doing enough to satisfy their needs. The attitude seems to be one of “you’ll use it and you’ll like it, now STFU!” This from the company whose CEO famously leapt around a stage screaming “DEVELOPERS DEVELOPERS DEVELOPERS!” Blamer had it exactly right… the way to build a platform is through developers… nobody will buy it if it won’t do what they want. What boggles my mind is that they’ve let other companies and organizations completely trounce them when it comes to the web as a platform.

WebKit and Gecko have been blowing IE’s Triton engine out of the water for years now, and despite Microsoft’s best efforts to play catch-up, the gap is widening. Gecko and WebKit already support several components of the HTML 5 specification, such as the <audio> and <video> tags, as well as offline storage databases and numerous portions of the CSS 3 spec, most notably stuff like border-radius, @font-face (for reals, not the proprietary MS implementation), and text-shadow. They seem like such minor things, but they really can make a world of difference in a web design, and doing them with CSS rather than Photoshop makes it so much more flexible and compatible.

Meanwhile, the IE team gives us dubiously-useful Web Slices, occasionally-useful Accelerators, tab grouping (which I find both useful and supremely annoying), and the bare minimum of CSS 2.1 and HTML 4 compliance. Their JavaScript engine is orders of magnitude slower than every other competitor, no matter how they care to doctor their statistics on the matter, and still lacks some DOM selection and manipulation methods. And while their Developer Tools are certainly much appreciated, they’ve driven me up the wall more times than I care to count because of how poorly-written they are, especially compared to Firebug, which is pretty much the gold standard for browser developer tools.

It’s really no wonder that developers and designers are starting to actively revolt against Microsoft’s browser platform. We were ignored for almost five years, and have been getting pretty marginal improvements at a dreadfully slow pace since development started up again in the face of an impending Firefox Apocalypse. Even today, Microsoft is still more concerned about making sure the HTML file you saved to your hard drive in 1997 will render properly than they are in ensuring that their browser can compete in the current fast-paced browser market.

This brings me back to my main point, namely that Microsoft isn’t taking IE seriously. (Or perhaps, that Microsoft isn’t taking the web seriously. Still.) There seems to be a fair amount of schizophrenia at Microsoft about how to handle the web, and it doesn’t help that they’re a massive company trying to compete against all comers. The simple existence of Silverlight as a Flash competitor is evidence that they’re dealing with a relatively fragmented web strategy aimed at dominance rather than support. It also, I think, hampers efforts to ensure that IE supports the latest and greatest HTML/CSS standards, because the counter-argument (which I’ve actually heard a few too many times by now) is simply “do it in Silverlight”.

Further, even the Windows Mobile team isn’t taking IE seriously. They shipped Windows Mobile 6.5 with Internet Explorer Mobile 6. And if you think the 6 is a typo, or somehow a misrepresentation of the IE version to keep it in line with the WinMo release number, you’d be sadly mistaken. Microsoft shipped the Internet Explorer 6 engine on a new product in the year 2009. It’s likely that release timetables kept them from even remotely being able to put IE 8 into WinMo 6.5, and it’s possible that architectural differences between Windows and WinMo prevented them from bundling IE 7, but simply put, it’s inexcusable and frankly embarrassing that an 8-year-old product has been bundled as the default browser on a new mobile OS in the year 2009. Blessedly, Microsoft has elected to provide proper 24-bit PNG handling and a more recent version of the still-glacial IE JavaScript engine for this build of IE 6, but Triton is still the same old non-compliant, glitchy, buggy POS that it’s always been on the desktop. If this situation doesn’t change with Windows Mobile 7, it will be just another nail in IE’s coffin of obsolescence. But hey, at least they’ve finally gotten away from IE Mobile 4…

What I’m most interested in seeing is what they do with the browser in the forthcoming touchscreen Zune HD. The Zune folks (like so many at MS) seem to be big believers in NIH, judging by the fact that the Zune desktop software and Windows Media Player development continue apace simultaneously for no apparent reason. As a result, any number of things could happen with this new Zune. They could go with the WinMo build of IE Mobile 6, and be an utter laughing stock. They could go with a third-party browser, like Skyfire or Fennec (though given Fennec’s current level of development, that seems unlikely). They could even build their own browser based on WebKit or Gecko (or, quixotically, the latest version of Triton). It’ll be interesting to see which possibility wins out, though I’d personally put more money on the IE Mobile 6 possibility than anything else, with a home-grown Triton-based browser a close second.

The really bizarre part of this whole escapade is that the IE team themselves seem fairly committed to reaching feature parity with other browsers’ rendering engines, and other departments within Microsoft are actively promoting the expiration of IE 6 support in future releases (like SharePoint 2010, which is opting to focus on ensuring broad compatibility with IE7 & 8, Firefox 3, and Safari [and speaking as someone who has the IE Tab Firefox extension installed just to deal with the slow-ass SharePoint 2007 at work, this is a welcome development]).

It may be a furtherance of the schizophrenic behavior I noted earlier, but some portions of MS seem to be trying really hard to embrace the modern, open web, and all that that entails, while others are still clinging – either through neglect, laziness, or stubbornness – to the outmoded days when IE 6 controlled about 98% of the browser market. As a whole, I really don’t think Microsoft is willing to put the sort of serious effort into Internet Explorer that would actually make it a modern, first-rate, first-class browser. It may be because there’s no profit engine behind such a move when other proprietary technologies like Silverlight can be used to much more powerful effect to control the web rather than operate within it, I don’t know. But I do know that Microsoft is starting to turn off wave after wave of their vaunted developers with their ongoing antipathy toward pushing Internet Explorer into the same category as Safari, Chrome, and Firefox. There doesn’t seem to be any sign of them trying to turn that ship around, and because of it, their market share will continue to decline, to the betterment of the rest of the web.

Quote of the Day

May 20th, 2009

This was posted in response to yet another bigoted anti-equality ad from the national Organization for Marriage and their “rainbow coalition” of hate, this time featuring the ever-popular children-as-political-mouthpieces stunt:

Yes, if laws promote equality, then we’ll have to teach our children not to be assholes. Think about it.

- NoWireHangers, Wonkette

Faulty Logic

May 8th, 2009

Comparative statistics reporting (i.e. “worst x since y”) does something weird to my brain. Even if the x we’re experiencing is a really bad thing, and it’s bad enough to be worse than y, for some reason my brain wants to get the better of y and out-do it.

For example, most economists think that the unemployment rate in the US may reach 10%, which would make this the worst recession since the 1980s. A particular economist by the name of Nouriel Roubini, however, expects unemployment to top 12%, making this the worst recession since the 1930s. For some strange, bizarre reason, I find my brain rooting for us to hit the latter figure, despite how incredibly bad I realize it would be for people and the economy.

I think my brain may be broken.

Labyrinth! Status Report

May 7th, 2009

Quick update on Labyrinth!…

I’ve had a number of other things taking priority over Labyrinth! development over the past few weeks, which successfully nixed the chances of getting the game released in April. Given that this summer is going to be rather busy between going to AFF next weekend and having Mysterium 2009 planning kick into over-drive very, very soon, I don’t know if I’ll be able to wrap the game up by the end of May, or even by the end of the summer, but I’ll keep soldiering on and giving it my best shot.

Some Thoughts on Myst for iPhone

May 7th, 2009

First, I would like to note that I’ve been very impressed by not only the positive response to Cyan’s recent release of Myst for iPhone, but also by the apparently high interest in the title. I suspect that there is a certain nostalgia factor involved in its popularity – especially amongst the Mac crowd, which has lately been unable to play the game on modern Mac hardware, or even in the latest OS X release on older hardware – but I don’t think nostalgia alone is enough to push a $5.99, 700MB application into the Top 10 Paid Apps list in multiple territories (and even the Top 5 in some).

Perhaps the most fascinating thing about the game’s popularity is its price point. The App Store has gotten quite a lot of press about its “race to the bottom”-style pricing wars, where just because you can charge more than $0.99 doesn’t mean you necessarily should. In fact, of the Top 10 Paid Apps currently in the US App Store, only Myst is priced higher than $0.99, and the average price of the other Top 25 Paid Apps is only $1.70. At $5.99, Myst is practically a premium application by App Store standards, and is managing to out-sell heavyweights like EA (with Trivial Pursuit, Tetris, and Tiger Woods PGA Tour) and PopCap (with Bejeweled 2), who have their games priced between $2.99 (Bejeweled 2) and $9.99 (Tiger Woods PGA Tour, because someone has to pay the licensing royalties to both Tiger and the PGA Tour, I guess). Given the fact that more expensive apps generally seem to be a turn-off for many buyers, coupled with the fact that at 700MB, Myst is easily the largest app in the App Store several times over, I’m honestly impressed at how well the game is selling.

What doesn’t surprise me quite as much, honestly, are the reviews. Overall, the game has a 4.5 star rating, with 86% of its ratings giving it 5 stars. I’m not exactly surprised by this fact given how well-done the port is, and given that there’s probably more than a few repeat buyers giving it these glowing reviews (though the repeat buyer thing doesn’t necessarily mean it’s guaranteed a good review… the DS port seems to be getting a pretty cold shoulder from veteran fans for what I understand are perfectly valid reasons). What does surprise me a bit is that the game is still so popular and well-received even though it’s 16 years old now, is rather clearly dated in terms of its technology, and has a rather vocal crowd of hard-core gamers who love to rip on it (amusingly, there are notably few complaints about its slideshow nature in the App Store reviews, and most entertainingly, someone commented on the absurdly long length of the intro… whether they were referring to Cyan’s classic logo or the actual game intro I’m not sure, though I suspect it was leveled at the logo, which is a lot longer than most of the “throw it up and get it over with” logo splashes of game developers these days).

Ultimately, it’s a testament to Myst’s staying power that 16 years later it’s still such a popular game. I think it sets a new bar for quality games in the App Store, and could well re-establish the traditional adventure game genre on a new platform, though I hope developers have learned from earlier efforts to duplicate Myst’s formula with spectacular failure and avoid making a lot of downright disastrously bad adventure/puzzle games.

Personally, I picked Myst up over the weekend just after it was announced as available on the Lyst (perhaps the first time in several years that I’ve gotten breaking Myst news from the Lyst, which was itself a nice bit of nostalgia ;) ), and played through it on Sunday and Monday. Overall, I’m very impressed with how well the game runs on my 1st-gen iPod Touch (the slowest Touch product in Apple’s lineup). It eats practically no battery (I think playing a long podcast is more battery-intensive, which is just weird, but also awesome), and with one exception that a reboot seems to have fixed, is rock-solid.

There are a couple of differences between the PC and iPhone versions which bear mentioning just for the sake of being nit-picky. First, the Linking Books are all still images, with the obvious exception of the initial fly-over of Myst Island (because that’s frankly impossible to remove); the animated fly-throughs from Myst Masterpiece Edition are the only moving overview you get of the Age. I suspect this was done for space-saving reasons, and ultimately it doesn’t detract from the experience. If anything, it’s made up for in spades by actually being able to “touch” a Linking Book for the first time. Suffice it to say, I geeked out over this more than was probably necessary.

Second, some of the sound effects seem to have been changed or removed, and the “loose” nature of some of the controls have been tightened rather substantially. This is most notable in Mechanical Age, where the Fortress Rotation Simulator doesn’t make a thrumming buzzy noise when “booting up”, the elevator rotator doesn’t have any inertia to it (making it impossible to over-shoot the elevator’s position, which was sometimes annoying but fairly realistic) and sounds a lot less substantial (I think the wrong click sfx was used there), and the fortress rotation puzzle also lacks its inertia. It may also be because of the touch-based interface, but the pressed state of many buttons seem to be missing; again, Mechanical Age is a good example, where the elevator buttons don’t dim when they’re pressed. Most jarring was the change made to the Generator Room’s sfx on Myst Island… gone is the reverberating series of “ka-chunk”s as the lights turned on, replaced now with a pretty bland pair of “click”s. Again, these don’t really detract from the experience, especially if you’ve never played the game before, but from the perspective of an old-timer, they were noticeable changes.

Finally, the wipe transitions seem to have all been replaced with fades. This is fine for moving from place to place within the game, but it does remove some of the pseudo-animated feel that the doors used to have in the original, where wipes were used in the place of video to “swing” doors open. The transition speed also seems to be used for the “animation” of large button presses, like the pump switches in Stoneship. I like having the transition speed set medium-high, which is fine for walking about, but it seems too slow for the pump switches.

One thing that is markedly improved over the Windows release, at least, is that the game performs just like it did on the Mac, even back in 1993. The Windows release was plagued by a couple of pretty glaring quality issues, most notably the fact that it couldn’t play two sounds at the same time. If you were standing by the Planetarium on Myst and turned the marker switch on, the windy ambient sound would cut out so that the switch sfx could play, and then the wind sfx would return. It also suffered from a problem with Quicktime’s behavior under Windows, where the cursor would flicker and display as black-and-white rather than color whenever it was placed over a video. These two problems persisted even into the Masterpiece Edition of the game, which has always bugged me given how well the rest of the game is presented.

Changing gears to actual presentation, I’m absolutely blown away by the visual quality of the images, even 16 years away from the game’s original release. To be sure, the construction seems a tad crude in places by modern standards (especially the massive color-only bitmaps used for ground texture), but the image fidelity itself is fabulous. With the iPhone’s 160ppi display and the original 24-bit rendered images, everything looks super bright and crisp… much better than trying to play it on a 24″ monitor set to 640×480. I would suggest setting your display brightness to at least 50% before playing, though, or the darks are a bit over-dark (display brightness has always been a concern in the Myst series, so this isn’t exactly a new development ;) ).

The audio sounds great in most places, though some of it just suffers from poor source quality… the voice work is a bit fuzzy, I suspect largely because it was done by a couple of guys in their basement with what was very probably not top-of-the-line recording equipment 16 years ago. It’s probably as good as it’s going to get, and while it’s not crystal clear, it’s still pretty darn good (and it’s nice to have Atrus pronouncing “futile” correctly, even if the audio quality does suffer ;) ).

If there’s one audio cue I do wish would be remastered from scratch, it’s the chime on the Selenitic clock tower. Gods bless Chris Brandkamp’s pitch-shifted Craftsman 7/8″ wrench, and kudos to him for his sound design ingenuity (between that and the toilet bubbles I still giggle every time I watch the Making Of video), but it just doesn’t have the bass of a real clocktower chime, and it gets lost under the louder and more trebble-heavy tick-tocking and grinding noises in the cue.

The auto-zoom is a nice feature, though it does rather clearly illustrate that the images being used in the game are only as large as the display itself. Most of the auto-zoomed content looks fuzzy because of the scaling… I’m pretty sure there isn’t much Cyan can do about this because the original images aren’t really big enough to make high-quality zooms, but I’ve caught myself waiting for an image to “resolve” the way Safari does when you zoom into a webpage, before realizing that the image is as clear as it’s going to get.

One thing that is a tad jarring is the fact that the game seems to flash to black rather frequently when transitioning from a still image to a video and back again. I don’t know if this is just a side effect of playing on a 1st-gen iPod Touch, or if it affects all platforms, but it is a little distracting and breaks the immersion a little. The loading throbber that appears for about a half-second before a larger video (like one of the brothers’ ramblings) plays is also a little distracting and seems largely unnecessary, but neither of these things are really deal-breakers.

Since it’s been the subject of a fair amount of conversation in the various places the game is being talked about, I thought I’d also discuss the game’s size from my limited-knowledge perspective. A couple of people have noted that the game’s size is absurd considering that the original game fit onto a 650MB CD, and was able to be installed on hard drives that were smaller than the iPhone port itself is with plenty of space to spare. These people are forgetting that the original game only installed the executable for the game’s engine; the media used by the game was streamed off of the CD, not copied to the hard drive. They are also forgetting that the original game used 8-bit images with additional Quicktime compression layered on top of them, while the iPhone release uses the original 24-bit renders, which are probably either JPG (if they were shooting for space-saving) or 24-bit PNG (if they were shooting for losslessness), and probably don’t have additional compression applied to them because it’s ultimately not as important as it used to be to save every possible byte. I’ve also noticed someone in the Wired review complaining that the game was smaller on the PC despite having larger images. Ignoring the 8-bit vs. 24-bit difference, there is no conceivable way that the original images were twice as large as those used on the iPhone. The game ran at 640×480 (versus the iPhone’s resolution of 480×320), but the images were nowhere near as large as the screen. Assuming RAWA’s example images in his dissertation on dithering are the correct size, the original game’s images were 544×333, or about 20% larger than the iPhone resolution. I am uncertain whether the images used in the iPhone release are the same size as the originals, or if they are scaled/cropped to fit the iPhone’s screen (the aspect ratios are different, though only slightly, so some cropping has occurred), but it would very likely not go as far toward explaining the increase in the size of the game as some of the other factors discussed above and below.

The video content was also super-compressed (and often looked terrible overlaid on the dithered 8-bit images) and poor quality, while the iPhone release’s video content is virtually indistinguishable from the still images. I’m wondering if the videos weren’t just re-mastered to all play as full-screen video content rather than embedded on a still background to avoid the overlay issue entirely (this would explain the full-frame flashing I experience, as well as why the Linking Book animations were removed), which would make them substantially larger in file size, despite improvements in compression technologies in the intervening years. More than anything else, I think this would have had the largest impact on the game’s size (and would explain how it went from just over 500MB in an interview with Rand several weeks before the game’s release to over 700MB… such an increase seems unlikely to be caused by a boost of audio or still image content alone).

Finally, the audio and music is all 100% intact and very high quality. The musical cues were truncated in the Masterpiece Edition release (again, ironic that the Masterpiece Edition would suffer from so many technical failings), likely to help keep the game on a single CD. The iPhone release made no such compromises, and it’s likely that a number of megabytes of content are taken up just by using the complete cuts of the music.

Ultimately, this is a no-holds-barred, damn-the-torpedoes release of the original Myst, which I have to say is well overdue. It’s a fantastic port, even factoring in the minor issues I’ve mentioned, and it plays very well, even on my low-end hardware; it probably plays better than it did on our $2000 PC back in 1994. It’s also great that I can play the game without having to migrate to my aging laptop or reboot my iMac into Windows, and I can take it with me to keep me occupied outside the apartment.

Several folks have said that despite the ludicrous size requirements, they would love to see Riven make the jump to the iPhone as well. While I won’t argue that it would be great to have Riven on the iPhone (even if it meant it was the only thing on some people’s iPhone… I can easily see it topping 5 gigs in size), I think that it’s such a massive undertaking that Cyan would be better suited to put it off until later. If any of their existing back catalogue gets ported, I’d love to see Manhole, Cosmic Osmo, and Spelunx make the jump before Riven (if only so I can actually play them).

Interestingly, something RAWA once said about Spelunx has me thinking that it would make for a great game to port to the iPhone under OS 3.0. In discussing Spelunx for those who had never seen or heard of it, RAWA mentioned this:

The cave system is also modular, so it is possible that if new rooms are discovered in the future, they can be added to your cave.

Given Apple’s impending support for in-app purchases and Spelunx’s modular design, it seems like a natural fit for a kid-friendly, extensible, educational game for the App Store.

Beyond re-releasing their back catalogue, I think Cyan could conceivably get into the market of making smaller iPhone-only games, given the high percentage of each sale that goes back to the developer, the low cost to market, and the potentially high return on investment due to the massive install base.

To be pie-in-the-sky, since the super hard work of moving Myst to a Cocoa-based application has already been done (while noting that going from an iPhone to a Mac app isn’t just a toggle in XCode), I’d also love to see Myst re-released for Mac OS X, and I’d definitely love to see Riven re-released on the Mac as well (definitely more than I’d like to see it released on the iPhone), since neither will currently run on the platform that launched the series. Given that Riven is the only game in the catalogue still limited to 8-bit dithered images and highly-compressed, 16-bit, outdated-codec videos, a Masterpiece Edition re-release with 24-bit images and high-quality video would be very, very much appreciated, regardless of the platform it ends up on (though Apple will need to improve their installation process if Riven hits the App Store at several gigabytes in size).

Ultimately, though, it’d be nice to see Cyan break new ground rather than continually re-tread the past… the question, I guess, is whether they can get any money to do so. I hope they can.