I'd be surprised, especially given the historically abysmal adoption rates of new IE versions. If you're serious, you still have to support IE 7 - no other browser has any market share worth mentioning going back even nearly as far.

I was talking about the macro-economy. Your billing argument is a micro-economy view and totally besides the point. It's not wrong, it's worse than wrong.

Agreed. I maintain my point: Fuck them, let them feel the full impact of their stupid decision, it'll cause them to make better decisions next time.

It goes to their mail, but with tons of G+ crap wrapped around it.

Has anyone created a gateway for FB, G+, etc.? I can tell FB to send me an e-mail whenever I get a FB message, I can probably write some curl script to fetch the actual message and post an answer - but maybe someone has already done it? Integrate FB messaging into your e-mail program?

Mostly because people are printing out e-mails to take them to meetings.

The iPad does more for the paperless office vision than all other inventions of the past 10 years combined. The one thing it doesn't allow for is spreading out all your stuff in front of you to look important (managers) or get an overview (non-managers).

But in these cases, they don't really use the messaging functionality of e-mail addresses. They use the unique identifier functionality.

No, it doesn't. There are tons of examples out there, and I've got some first hand experience. Stuff that works just fine in every other browser will break on IE in random versions because IE requires some totally different way of doing it than everyone else. That goes up to at least including IE8, I'm not entirely certain about IE9 as at least everything I use seems to finally work there.

IE still sucks and I will applaud anyone who writes a fast-spreading virus to irrestorable removes it from every machine, world-wide. And fuck those who don't have any other browser installed and are now stuck without the Web, we're all better off without them idiots anyways.

I may seem extreme, but just try to make a rough estimate of the total damage that IE has done to the world economy in requiring all the wasted time and effort for having its quirks supported.

I agree that pixel-perfect is crazy, but most of us geeks do ourselves a disservice by not taking the importance of design as seriously as we should.

I definitely want my web stuff to look as similar as possible on all kinds of devices. I hate it when some browser doesn't support some feature I need and displays totally different. Because there's actual thought going into my designs, it's not just eye-candy. Losing parts of the design is pretty much the same as using parts of the functionality.

No, it doesn't.

Granted, every release of IE seems to finally bring it in line and make it play nicer with the other children, but IE is still the odd one out in many, many more cases than everyone else and probably more than everyone else combined. MS just has this "not invented here" fixation and insists on doing a ton of things differently than everyone else.

I've spent many, many hours working around IE quirks, and that was after declaring that IE6 will be completely unsupported and I don't really care all that much about IE7 as long as most of it barely works.

For something reasonably complex in both logic and presentation, I can easily imagine a cost of several ten-thousand bucks, if you count in overhead and all other expenses. 100k seems high, but not totally off.

I'm developing a web app so there's some personal frontline experience here. Supporting IE is still a bitch, it sucks badly and it's a punishment. If my target audience were private individuals, I'd say "fuck IE", plug a big "IE not supported" button on the homepage and be done with it. Unfortunately, my target audience is in the corporate environment.

The main problem is that IE does everything differently from everyone else and from version to version. In CSS, for example, sure, other vendors have their prefixes, but writing out half a dozen essentially identical statements for advanced CSS stuff is tedious, but not troublesome. Finding the five different ways the IE wants it done, that are totally incompatible with anything else is just horrible. Google up how IE does CSS gradients vs. how everyone else does it for an example.

For JS, fortunately we have stuff like jQuery or Prototype, and yet plugins to these still list compatability with various browser - and large everyone else is either supported or unsupported and then there's IE. It is very, very, very rare to find a plugin that works on Firefox, but not Chrome, or on Safari, but not Opera. It's a lot more common to find something that works everywhere except IE.

Basically, you can write a web app that runs fine and looks nearly the same on all recent versions of all major browsers, and breaks completely on IE. You would have to consciously try to do the same with any other major browser.

It's where your lunch money went . .v. :)

hawk