Posts Tagged ‘microsoft’

Seattle/Redmond dinner update

Monday, April 7th, 2008

Sitting in the Virgin America part of the SFO International terminal.  Talk about an awesome terminal.  Can’t wait to fly Virgin, too - my first time (hah!).  I doubt anyone on the plane throws down in DOOM the way I do, so I expect a river of tears in the aisle.

Wish I could be at the Google Campfire tonight, cuz the news is awesome, but Microsoft got to me first, so up to the frigid North I go….  Hope this MS stuff is as good as it sounds.

It turns out the Seattle Photography Group is meeting on Wednesday night.  Cool!  So I’m going to that. You should come.  :)

Then, afterwards, I’m hoping we’ll head out for some food.  If you want to get food afterwards, please leave a comment so we have at least a rough head count.  Attendance at the SPG isn’t mandatory, but I’m sure you’re welcome to come.

On Tuesday, I already have dinner plans, but wouldn’t mind hanging out with some geeks afterwards.  Doubt I’m up for going into Seattle, though, so if you’re in Redmond or Bellevue, holler.

(I’ll try to email everyone who sent emails, commented, and twittered - but if you haven’t heard from me, re-comment because I’m lame)

Thoughts on the new IE compatibility switch

Wednesday, January 23rd, 2008

Over on IEBlog and A List Apart, they detail a new flag for the upcoming IE8 that would enable you to “lock” the browser down to older versions should you be expecting older broken behavior from IE6 or IE7.

This is a bad idea. The Safari team has a great write-up about why they think it’s a bad idea, which I agree with, but I also have an additional take:

Pages and sites that are likely to care about this are poorly written and poorly maintained. Microsoft created this problem themselves when they let IE6 sit idle for more than half a decade, and now they have to deal with it. Instead of letting someone flag their site as being broken (that’s what they’re doing), why shouldn’t they finally force them to fix their site and improve the browsing experience for everyone (not to mention improve the stability, speed, and maintainability of their codebase)?

If someone owned a car, but didn’t know how to drive it properly, would we bend the driving laws to let them on the road? Of course not. Some reasonable adherence to standards and moving things forward is the only thing keeping the web browser mess from descending into pure chaos.