Exactly. And Joel is such a brilliant, persuasive writer he can actually convince you writing their own installer/language was a good idea. It’s scary, actually.
Just repeating what other, more clever, people have said so far, but I think you’re kind of missing the point here.
Writing their own installer and own language is indeed a great idea in this case, just based on what I’ve read in your article (haven’t really read Joel much ever).
From what you’ve written, Joel apparently has a web-based app which runs native on php on a lamp stack, and runs native in ASP/VBScript on a windows/IIS stack. This may just be because the non-standards compliant windows world scares me, but I don’t know of many web apps which run identically on both of those stacks, do you?
(I certainly don’t think running PHP on a Windows/IIS stack would be a walk in the park, even though I’m a lamp geek. Didn’t Zend recently have to make all kinds of modifications to php or fastcgi or something to get it to run php properly on windows?)
If it is the case that Joel can run the same app in the language which best supports the platform on several different types of platforms, then I think you’ve really missed the point. From what you’ve written, Jeff, the point of Wasabi appears to be that by abstracting away the underlying idiosyncrasies of a platform you can concentrate on developing the part that really matters of your app and think about that rather than having to keep 7 different versions in sync all the time.
That’s sweet, if you ask me.