'Long Term' is a year

I'm so very affected by what Mr Baker says in this article on slashdot.

I had formerly assumed Mr Baker to be the leader of a software project which was developing a reliable, decent enterprise-ready browser suite. That's what the description once said, anyway.

I learn, now, that either Mr Baker, the project itself, and/or all of us have been deluded. What part of 'reliable' and 'enterprise' equates one year with long term? I've fixed bugs that were older than that. I've maintained apps that were there in the Netscape 3 days, and I'm no one special.

It's unfortunate that Mr Baker hasn't worked in the Enterprise previously, or he'd realize that a product's longevity is something of a feature he may want in his little browser. It's too bad that we'll probably have to look for something a bit more reliable for our product at work, because we can't be back-porting fixes for the latter 4 years of this thing. Once again, Microsofties can taunt:

"Yeah, but will it still be a main-stream product on Monday?"