Microsoft Not Worried about FireFox

didde writes "It seems like our friends in Redmond are quite happy about IE. According to this article, they won't be updating it until Longhorn. My favorite quote would be [We have a very, very innovative set of capabilities that we're putting in the next version. And in the meantime it's an extensible platform, and there will be a set of extensions that Microsoft does as well as others.] Oh boy, are they actually working side by side with the virusmakers and phishers?" That just gives the MozBoys a year head start.

Comments

Re:Working with phishers?

[October_30th]

Yep. That was rather pathetic.

I wonder if /. accepts Microsoft related submissions these days only if they contain a witty soundbite that's in line with the OSS groupthink.

Re:Firefox browsing speeds

[CypherXero]

What's with everyone talking about this? I've been seeing this ALL OVER THE PLACE in the past few weeks! I've been using these tweaks ever since the browser was called Firebird. It's nothing new. It's probably someone who found this information out, and is spreading it like it's new.

Re:Safari blew up

[plj]

I've tried to understand Safari's shortcomings and have even defended it on /., but I think my cup just leaked over. Following the crash I wrote this to the crash report I sent to Apple:

Please describe the circumstances leading to the crash and any other relevant information:

Running browser SECURITY TEST at http://bcheck.scanit.be/bcheck/ is what crashed Safari this time - in addition to the n+1 other situations where it normally crashes (generally involving ridiculous memory consumption indicating huge memory leaks).

Now, if Mac OS X Panther as a whole would be so badly programmed as Safari is, I'd probably gladly switch to some crap from Redmond. See, Internet Explorer for Windows, even while being hugely insecure without virus scanner and continuous patching and having horrible CSS support, has much, much greater stability than the newest version of Safari.

Luckily, though, real alternatives exist - alternatives like Camino, Firefox, Opera and Omniweb. They all do not take advantage of all the fine features (those like Keychain) of Mac OS X and Cocoa API as well as Safari, but they really do have much greater stability comparing to Safari.

So shame on Apple's Safari & WebKit team. Safari has been like this for a really long time, and does not seem to get better at all. If you just can't figure out anything better, you should drop Camino altogether and move to back Camino, which, despite it's shortcomings on feature side, at least runs very smoothly, and besides uses much more widely supported rendering engine than Safari, which is a plus too.

I do wonder, though, whether someone at Apple actually reads these crash reports I'm sending to you? Perhaps I should send them directly to Mr. Jobs' mailbox instead?

Well, anyway, if you want to argue with me about all this, please don't hesitate to mail me at [address here] But I really think the best thing you could do would be just start fixing those bugs instead - and designing them out completely, for that matter.

Yours sincerely,

The MozBoys

[lousyd]

That just gives the MozBoys a year head start.

Yeah, probably the girls, too. Or is there something special to developing software when you have a dick?