Are you ready for Internet Explorer 8?

Kimosabe said:
At work I am forced to use IE7, cos the IT people claim that they cant manage firefox. When I get home and use Firefox i always say to my self, wow IE7 blows, why the hell would anyone want to use it.
Click to expand...

IE has very good support for large enterprises.

Firefox really needs to work on this. Things like pushing updates from a central point or disabling installation of certain plugins must be implemented.
 
EtienneK said:
IE has very good support for large enterprises.

Firefox really needs to work on this. Things like pushing updates from a central point or disabling installation of certain plugins must be implemented.
Click to expand...

Uh.. what? Actually, intranet developers are too lazy or too stupid to develop for anything else besides internet explorer! Some huge organisations can't even handle IE7, now that is sad! If they developed for standards based browsers first, and worked their way back supporting internet explorer, they wouldn't have this problem!

Better support, hahahahahahaha... catch a wake up.
 
Firefox has a hassle doing domain authentication, you constantly have to type in passwords. Part is why IE is easier to manage over networks, etc.

That being said I would have to go with FF being the superior browser, lets wait and see what teh IE8 brings to the table.
 
cookiemonster said:
Uh.. what? Actually, intranet developers are too lazy or too stupid to develop for anything else besides internet explorer! Some huge organisations can't even handle IE7, now that is sad! If they developed for standards based browsers first, and worked their way back supporting internet explorer, they wouldn't have this problem!

Better support, hahahahahahaha... catch a wake up.
Click to expand...

Err... actually you need to catch the wake up. It has nothing to do with the web developer so much as FF lack of enterprise management and support. Until FF implements some NT domain goodies, it is simply not feasible to roll out in an office environment. Imagine having to manage several hundred installations manually, not to mention user frustration with no domain authentication.
 
My parents taught me not play with viruses and to use proper protection. Thus I may not use Winternet the Fexplorer.
 
cookiemonster said:
Uh.. what? Actually, intranet developers are too lazy or too stupid to develop for anything else besides internet explorer! Some huge organisations can't even handle IE7, now that is sad! If they developed for standards based browsers first, and worked their way back supporting internet explorer, they wouldn't have this problem!

Better support, hahahahahahaha... catch a wake up.
Click to expand...

You're not getting what I'm saying.

Let's take a company with a 1000 people and desktops as an example. How would an admin easily install Firefox on all of those 1000 PCs?

And what if a new version of FF gets released? Should all of those 1000 installations download the update from the net? Of course not, that'll be stupid. A central repository within the company for updating will make a lot more sense.

And what if the company does not WANT to update its current version of FF, because the new update breaks something? How would they stop users from updating?

And how would you stop users from installing their own plugins for FF? How would an admin be able to set up a list of allowable plugins? Plugins can be big security risks.

And then there is NT authentication to think about...

FF is a great browser for an individual or small company, but they should really start implementing some enterprise features for it. They should really work on features to make admins' lives easier.
 
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5) Gecko/2008050509 Firefox/3.0b5

All I got to say.
 
EtienneK said:
Good!

For years I've had to listen to stupid, arrogant web designers laugh at me for following standards. Some claiming that Microsoft is the only standard!

Cretins.
Click to expand...

You have the wrong people as 'friends' / 'colleagues' giving you advice.

Anyone not designing for all browsers and platforms many years ago should have been hung, drawn and quartered. It's called 'accessibility' and should be a designer's / coder's number one objective. If you have to recode it you have my consolences but shouldn't have to if done properly the first time round. Hope it's on your weekend. This is a great move from Microsoft (finally) to support proper CSS standards. Old news though (about IE8).

Oh any any web designer still stating a site is best optimised for a specific browser has their 'Team Fail' membership.
 
EtienneK said:
You're not getting what I'm saying.

Let's take a company with a 1000 people and desktops as an example. How would an admin easily install Firefox on all of those 1000 PCs?

And what if a new version of FF gets released? Should all of those 1000 installations download the update from the net? Of course not, that'll be stupid. A central repository within the company for updating will make a lot more sense.

And what if the company does not WANT to update its current version of FF, because the new update breaks something? How would they stop users from updating?

And how would you stop users from installing their own plugins for FF? How would an admin be able to set up a list of allowable plugins? Plugins can be big security risks.

And then there is NT authentication to think about...

FF is a great browser for an individual or small company, but they should really start implementing some enterprise features for it. They should really work on features to make admins' lives easier.
Click to expand...

Did I mention Firefox? No. There are other standards based browsers that support domain authentication. Opera comes in an msi package, so it's possible to deploy over many systems. There has also been an MSI package for Firefox since version 1.

Besides, even if these browsers don't support these features, is that reason not to support standards? I'm not saying they must develop for these browsers, they must develop towards a standard. That is what everyone is saying, when they take just a little bit of time to think about it and look further then their nose.

If they did, upgrading to IE7 wouldn't have been a problem, and upgrading to IE8 even simpler! The fact is, huge corporates are still stuck on IE6 not IE7, why? Not because standards based browsers are hard to deploy, or don't have domain authentication, but because their developers can choose the evironment they develop in. This is extremely narrow minded and not only extremely lazy, it's selfish.

This is one of the biggest reasons proper developers who don't only develop in these closed environments are going to have to develop for IE6, IE7 and IE8 when it comes out. We obviously can't afford to not accommodate all the corporate users.
 
Last edited:
It's a very gray area with IE8. On the one hand if you think about, I can see why Microsoft wants to implement a line of code that enables their most standards compliant rendering. Everyone could then upgrade to IE8 with no problems...

However, catering for these antiquated sites is a lot of dead weight to carry and is inevitably going slow down innovation on the internet. If developers aren't forced to upgrade their applications, they wont.. Cliché I know, but you can't go forward by always looking back.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X