Live data from Hacker News

We don't support Internet Explorer, and we're calling that a feature

paydirtapp.com

151–160 of 167 posts

Re: We don't support Internet Explorer, and we're calling that a feature

#151
post #116
post #113

yay! Something I did with my homepage http://adnansiddiqi.com . Try it on IE :D

Do you know that your site works OK on IE9 when changing the UA? Ironically, your site page does not include a doctype so it is interpreted in quirksmode [1]... [1] http://en.wikipedia.org/wiki/Quirks_mode

Yes I do.

Re: We don't support Internet Explorer, and we're calling that a feature

#153

Earlier quoted context omitted.

There are definitely oddities about how iOS Safari does things. Handling orientation changes and using high-resolution images for the devices with Retina displays are repeat offenders.

Well, adding support for Retina displays is definitely an iOS-specific thing (at least right now). But orientation changes? Is that not a general "mobile issue" for you? Or is (are) the WebKit build(s) in iOS doing something specifically bad compared to (say) Android?

In my experience, the problem is that the Android/WP7/[other smartphone OS here] web browsers are so far behind iOS WebKit in terms of functionality that you basically have to handle each device on a case-by-case basis. Given that, a lot of developers choose to focus solely on iOS since it's the lowest-hanging fruit with a massively large userbase and a relatively-standards-compliant codebase.

For example, all mobile web browsers should theoretically throw either a resize or orientationchange event on orientation change, but some Android devices don't, with no other viable fallback, and no clear rhyme or reason as to which devices support it and which don't (other than that newer flagship devices are slightly more likely to be standards-compliant). CSS media queries are more consistently supported, but they aren't the solution to every problem.

Re: We don't support Internet Explorer, and we're calling that a feature

#154
post #91

Earlier quoted context omitted.

As a counterexample, let's consider Google's blocking of Opera. Google routinely blocks Opera when rolling out new stuff. I kind of get it, because of your point 1. However, they sometimes offer a "try anyway"-link and sometimes not. The times that I can not easily "try anyway" makes me dislike Google much more than the times that I "try anyway" and it ends up broken in funky ways. Bottom line; Yes, your reputation s…

Actually, your reputation does not actually suffer. You have been up-front with your customers from the very start. If you use Internet Explorer, then you should be blocked or else you will probably come against a bug that causes you to: * potentially lose work * have a product that you paid for that doesn't do everything you want it to do * get frustrated when things don't work and nobody will fix them ("Why don't y…

>detecting document.all, or via something proprietary or broken in IE

Please don't do that, it will also break support in browsers which emulate that behavior for compatibility with IE-only websites. document.all is actually also there in Opera.

Re: We don't support Internet Explorer, and we're calling that a feature

#155

Earlier quoted context omitted.

Well as long as they are running WebKit and support the device pixel ratio media query, they will be supported. But I'm guessing that Android phones with high-dpi screens that support that query are still at the single digit percentage of browser statistics.

That's fine for CSS images (media queries), but what about content images?

All the code I've seen for content images involves some JavaScript stuff that uses the device pixel ratio as well.

Re: We don't support Internet Explorer, and we're calling that a feature

#156

Earlier quoted context omitted.

That's fine for CSS images (media queries), but what about content images?

All the code I've seen for content images involves some JavaScript stuff that uses the device pixel ratio as well.

The server should not have to decide which image to send, based on whatever it can gather of a combination of various factors, including device display resolution capability (double-density vs regular pixel mapping) and connection quality (wireless vs broadband) or whatever else comes into play. The server should be advertising the capability of high res images and the user agent should be requesting them if it wants.

Re: We don't support Internet Explorer, and we're calling that a feature

#157
post #128
post #64

Earlier quoted context omitted.

Is it rational to claim that if you upgraded a Pentium III computer to Windows 7 you aren't in "the smallest fraction" of users of old computers?

The point is having a Pentium III Win 7 machine covers using a Pentium 4, Athlon XP, and all those other old computers to install IE9 - covering the biggest fraction of users through backward compatability.

Correct, thank you.

You can run Windows 7 on pretty much anything that will run Windows XP. "It costs money to upgrade" may prevent you from doing so, but at this point, after a decade, it's not Microsoft's problem if you're not willing to spend the money. They're not obligated, nor should they be obligated, to avoid using their new stuff (Direct2D, for example) in order to continue to target XP users.

Re: We don't support Internet Explorer, and we're calling that a feature

#158

Earlier quoted context omitted.

I'm confused why you believe you need hardware for testing? iOS simulator should be plenty sufficient in any standard dev environment...

So you don't need iOS hardware, just Apple hardware... so much better!

People without Apple hardware create websites?

Re: We don't support Internet Explorer, and we're calling that a feature

#159

My personal web projects always start with standard-conforming HTML with forms and links. They're fully interoperable contributions to the world-wide web and should be usable by every browser and robot written in the last sixteen years. I call that a feature, and I'm disappointed that so many devs set their sights lower.

That's nice. The problem is that Internet Explorer doesn't conform to these standards. What do you do in this situation?

IE has a nasty habit of sniffing content or examining URLs and disregarding the actual media type of a resource, but it hasn't come up much in practice, and otherwise I haven't seen any showstopping problems in talking HTTP and rendering semantic HTML. Its CSS and javascript are a mess, but those are optional, and I'd be embarrassed to release anything that would become completely unusable without them.
Post reply on HN