Page 2 of 2
Posted: Thu Sep 30, 2004 12:49 pm
by Mobius
Defender wrote:Mobi: This is why people code for IE:
That's the lamest dude. On many "IE-designed" sites the navigation doesn't even WORK in Mozilla. Now, if you owned a bricks and mortar store, would you stop upwards of 10% of your customers coming inside because of the kind of hat they had on? Same thing.
DESIGNING FOR IE IS DUMB, RETARDED AND GAY.
Design for W3C specs - and THEN make it work in IE - but most likely it WILL work in IE.
Posted: Thu Sep 30, 2004 1:57 pm
by CDN_Merlin
Netscape was around long before IE was. Thing is, MS decided to incorporate it into Windows and offer it for free to kill any competition(netscape). They actually went to court and were told to unlatch it from Windows and offer it as a seperate d/l to comply with anti-competative practices.
I've used Netscape since Day 1 of web browsing and so far I'm the only one who voted for it in this thread.
Posted: Thu Sep 30, 2004 2:32 pm
by Top Wop
Its one of those rare occasions that I agree with Mobius.
And Sargeant Thorne, congrats! You are now no longer considered a wuss.
Posted: Thu Sep 30, 2004 3:28 pm
by STRESSTEST
Posted: Thu Sep 30, 2004 5:31 pm
by MD-2389
DarkShadow wrote:I belive this was it.
FIREFOX
1. Type "about:config" in the address field.
2. Set the value of network.http.pipelining to "true".
3. Set the value of network.http.pipelining.maxrequests to "100".
4. Set the value of network.http.proxy.pipelining to "true"
5. Set the value of nglayout.initialpaint.delay to "0"
Thats it, and it works in Mozilla Suite as well. Its meant for broadband users, but it worked quite well for me too. (56k)