Mac IE Development Team Dissolved?
Saturday May 13th, 2000
Microsoft has dissolved the Mac IE development team, according to this report at MacInTouch (scroll down to May 11. There are confirmations in the May 12th news). You can read another more detailed confirmation on the MacInTouch front page (which contains their May 13 news).
There is a forum at metafilter discussing what Microsoft's reasoning could be behind the decision.
I find the dynamics of this quite intriguing. The statement of the Microsoft PR person (see the first MacInTouch link) gives an impression that the team is not dissolved, but this view is deemed false by the three independent confirmations. MacCentral has decided to believe the Microsoft PR person.
Who to believe? Does it matter? The fact is that Microsoft doesn't have a cross-platform strategy, even for the two platforms that they support. This was clear when MacIE5 came out and trounced the WinIE development team's efforts. I had been wondering how Microsoft would deal with this situation. Would they continue Mac development on a separate track, duplicating (or surpassing) the efforts of the Win IE team? Or would they attempt a cross-platform effort similar to Mozilla? I didn't expect that they'd dissolve the Mac development effort completely. But, then again, those Apple people are getting a bit uppity, with their iMacs and G4s and new OS...
I think Microsoft will have to come up with some strategy to deal with the fact that their two browser efforts are diverging so drastically. It is very difficult to claim that IE is a solid, consistent development platform when the feature sets on Mac and Windows are so different. And what about web appliances like WebTV? How can MS convince developers to develop across 3 differing browser implementations, especially when Mozilla can offer a consistent cross-platform development environment? I think this might be the first move of Microsoft to address this issue. Whether it means that they give up the Mac platform completely, or just temporarily, I think it shows that even Microsoft has a limit to the number of developers it is willing to commit to a non-revenue-generating enterprise.
BTW... I read the news at Taylor's website, while looking at an interesting piece on "bidirectional links". Why do I mention this? I'm interested to see if mozillaZine shows up on his bidirectional links list!
UPDATE: Another non-denial denial, this time from the IE5 for Mac Program Manager, Jimmy Grewal, in the microsoft.public.inetexplorer.mac newsgroup. However, Jimmy does state that Mac IE developers (not all?) have been moved to another project and that "In fact, we are working on a new release of MacIE that will ship on the MacOS X CD." However, it's important to note that nothing he says is contrary to what the sources at MacInTouch say, and it sounds quite like what the PR guy stated at MacInTouch (just more verbose).
#18 Mac user's will live
Sunday May 14th, 2000 3:33 PM
You are replying to this message
I swear, that's the ONLY thing I EVER see Mac users discussing in regards to Mozilla. They're coming out of the woodwork specifically to whine that Netscape doesn't deem them worthy of the endless, endless hours it takes to develop a Mac-native UI.
If Mac users would prefer to use BROKEN-ASS IE just because they don't like a BETA-LEVEL UI, that just verifies exactly why I feel I have nothing whatsoever in common with Mac users.
Did anyone catch that they intend to land a Classic skin for PR2? Maybe it won't look just like Mac Nav Classic with the little stripes in the title bar, but so what? I don't personally think that the entire Mozilla cross-platform development strategy should be scrapped just so Mac users can keep their particularly unexciting native UI, especially when all they have to do to get it back is make a damned skin or even package. Anyway, they're not going to make a native UI for Windows -- by far the more prevalent market -- so I don't know why Mac users would think Netscape should make an exception in Mac's case. Feel lucky that you're still considered one of the three core OSs.
Bottom line: If Netscape was wasting time on native UIs, Mozilla would not be so nearly easy to port to the new Amiga as it is now. YOU may not care how easy it is to port, I who wants to port it to the new Amiga DO care about cross-platform UIs... ALOT. It saves a TON of work, that's the point in scrapping native UIs.