Microsoft and AOL settle lawsuit

[mikeymike]

I'm more concerned about Netscape/Mozilla's future as a result of this.  While yes, there are tonnes of people developing for NS/Mozilla, I wouldn't be surprised if much of the work, be it organising effort on issues or whatever, is done by AOL:Netscape employees.

[mikeymike]

$750 million?  That probably just about covers AOL's legal fees :-)

[mikeymike]

I hope I'll never go back to IE.  But that depends on the alternatives, don't it :-)

Hopefully, with a bit of luck, Mozilla will be fully handed over to the community if AOL give up on it.  So development will slow down a bit on it, but it's better than nothing.  Bear in mind that Firebird/Thunderbird are also probably owned by AOL.

Opera isn't quite to my taste in browsers :-)

With an extra bit of luck, particuarly important as the A1/OS4 is nigh, one of the browsers will have their socks pulled up, and I won't have to keep hoping that someone will start porting Mozilla to AmigaOS.

On the email side of things, I wonder if Qualcomm (Eudora) can be persuaded to port Eudora to AmigaOS4.  It's quite a nice email package, though I've moved on (I might come back to it though).

[mikeymike]

@ nOMAAM

What is *actually* wrong with IE ? besides the fact that its microsoft ?

Oh please.  Credit me with a little more maturity than that :-)


I've written some of my opinion about it here, but you'll probably find more knocking around that section of my website.  There's not much point in starting an IE-bashing thread :-)

[mikeymike]

@ ogy

it seams to me that lot of people out there have lost their minds completely

Ah, the good old "I have an opinion, people disagree, they must all be wrong" attitude.

I used prety much all the browsers out there and IE6 is the best one by far...

Of course you are entitled to your opinion, but that's what it is.  Opinion.  There is no right or wrong in opinion, just in the facts that it's based on.

Its the only browser that fully and completly supports the contemporary web content without gliches and compromises... So I just wonder what the hell is the problem...

Wrong.  here's one example.  Run it through W3C's HTML validator if you want to be sure that it is standards compliant code.

Can we quit the browser advocacy please? :-)