Live data from Hacker News

Hey Paydirt: Your Site Works Just Fine In IE

blog.reybango.com

111–120 of 217 posts

Re: Hey Paydirt: Your Site Works Just Fine In IE

#111
post #107

IE9 may have caught up on some things, but there are a lot of things it doesn't do, that Safari/Chrome and Firefox (as well as Opera in most cases) do do. So even if it might not be quite as hard now to get it to layout properly (it still is not the same as Chrome/Safari/Firefox/Opera, really, things just don't behave the same unless you train yourself to avoid things that IE9 doesn't like), there are lots of other r…

Oh god, we might as well start asking why FF didn't support ellipse for what seems like decades.

Everyone has different release schedules. IE is a lot more conservative because they support enterprise who are mighty touchy.

Grow The Fuck Up Cry Baby. I'm all for IE6 and IE7 whining, they suck. I'm even for IE8 and the entire stop at XP whining. Damn MS for that.

But you just sound like a total privileged prat who doesn't have a clue what's going on when it comes to web standards. FF and Chrome have a lot more latitude. If you want to know what happens when stuff starts moving too fast keep an eye on the webkit mobile css support fiasco unfolding in front of us right now. There is such a thing as moving too fast.

Re: Hey Paydirt: Your Site Works Just Fine In IE

#112
post #107

IE9 may have caught up on some things, but there are a lot of things it doesn't do, that Safari/Chrome and Firefox (as well as Opera in most cases) do do. So even if it might not be quite as hard now to get it to layout properly (it still is not the same as Chrome/Safari/Firefox/Opera, really, things just don't behave the same unless you train yourself to avoid things that IE9 doesn't like), there are lots of other r…

most use just three or four features out of that list. And IE10 is adding support for many of them. By leaving them out you're hurting users for no reason.

    drop IE6: great! kill it with fire
    drop IE7: reasonable
    drop IE8: risky, millions of users
    drop IE9: kind of stupid. 15% of the web, soon to be 30%
So much for fighting for open standards.

Re: Hey Paydirt: Your Site Works Just Fine In IE

#113
post #107

IE9 may have caught up on some things, but there are a lot of things it doesn't do, that Safari/Chrome and Firefox (as well as Opera in most cases) do do. So even if it might not be quite as hard now to get it to layout properly (it still is not the same as Chrome/Safari/Firefox/Opera, really, things just don't behave the same unless you train yourself to avoid things that IE9 doesn't like), there are lots of other r…

Oh god, we might as well start asking why FF didn't support ellipse for what seems like decades. Everyone has different release schedules. IE is a lot more conservative because they support enterprise who are mighty touchy. Grow The Fuck Up Cry Baby. I'm all for IE6 and IE7 whining, they suck. I'm even for IE8 and the entire stop at XP whining. Damn MS for that. But you just sound like a total privileged prat who doe…

I noticed that neither you nor the other person who replied promptly seemed to notice or respond to my main point in any way.

Re: Hey Paydirt: Your Site Works Just Fine In IE

#114

Earlier quoted context omitted.

It seems unnecessary to straight up block potential customers from signing up because of their browser. Encourage them to get the full experience using another browser might be a better idea.

Suppose you are the proprietor of a physical retail business. You're the only employee, so on Sundays you close the shop because otherwise you'd be short-staffed. Do you listen to potential customers who complain that you're not open on Sundays by (a) offering them a degraded experience by letting them shop while you aren't there, (b) hire additional staff to support the shop on Sundays, or (c) tell them to come back…

Did you mean to post this comment to the previous article and not this one? The article shows that the site works in IE9 and IE10.

Not to mention that the author not only chose (c) but also posted the equivalent of saying closing the shop on Sundays is a feature because Sundays suck for shopping(which is obviously wrong) and basically advised other sites to do the same.

Re: Hey Paydirt: Your Site Works Just Fine In IE

#115
post #53

Earlier quoted context omitted.

I think you'll find that they're using LESS or SASS or something. Such that when you define a box shadow that it produces the appropriate CSS for each respective browser.

Neither adds that automatically, you define the prefixes yourself (or use a framework that does).

I think he means something like http://compass-style.org.

Re: Hey Paydirt: Your Site Works Just Fine In IE

#116
post #113

Earlier quoted context omitted.

Oh god, we might as well start asking why FF didn't support ellipse for what seems like decades. Everyone has different release schedules. IE is a lot more conservative because they support enterprise who are mighty touchy. Grow The Fuck Up Cry Baby. I'm all for IE6 and IE7 whining, they suck. I'm even for IE8 and the entire stop at XP whining. Damn MS for that. But you just sound like a total privileged prat who doe…

I noticed that neither you nor the other person who replied promptly seemed to notice or respond to my main point in any way.

Well, MS is betting on modern HTML for Metro.

Re: Hey Paydirt: Your Site Works Just Fine In IE

#117
post #29

Supporting IE has nothing to do with how well it renders a site. Supporting IE carries massive baggage as you have to pin yourself to Microsoft's erratic, tactic based release cycles and limiting yourself with future features. Chrome and Firefox now how have rolling releases and are closely tied with the developer community, so new features and rendering uniformity is what you gain. There's also the ethos you buy int…

> There's also the ethos you buy into by supporting IE: you're supporting a closed source, proprietary internet. By your reasoning, nobody would write an iPhone app either, or anything targeted for a platform other than GNU/Linux.

That point was very weak, I have to admit. I guess a better way of putting will be you're supporting an open internet by supporting open browsers. Not the other way around.

Re: Hey Paydirt: Your Site Works Just Fine In IE

#118
post #61

What does it mean to "not support" a browser? Does it mean you know your site is broken in the browser? Does it mean you block that browser? Does it mean you intentionally broke your site in that browser? None of the above. It means you don't want to waste your QA time testing and fixing minor quirks in the browser and you don't want your users having a degraded experience on that browser. To protect your users, you…

There's lots of enterprisey stuff out there that only "supports" various versions of IE, and bounces out other makes and models of browser. HN folks may or may not see much of that, because that stuff is typically in various corporate portal technology. In health-care IT in particular, there's a popular radiology app that uses an ActiveX control that is bug for bug compatible with IE6 and doesn't work on IE7. That's…

Very true, but in some cases (such as mine) an individual working on an app can slowly work towards cross browser compatibility every time they touch a page. After a year, I'm almost there. :) There are several other apps... but you do what you can.

Re: Hey Paydirt: Your Site Works Just Fine In IE

#119
post #92

Earlier quoted context omitted.

With IE, a testing environment costs my company about $300 per developer. I.e., miniscule relative to the cost of actually having a developer.

fair.

So you just agreed the premise of your whole argument above is not valid. Just saying.

Re: Hey Paydirt: Your Site Works Just Fine In IE

#120
post #72

If I, as a developer, decide my site supports a browser, I know I'm going to have to spend some time doing QA on that browser. Standards are cool, but I've run into enough FF and Chrome bugs that I always test. That being said, the cost of testing in IE is waaay higher than the cost of testing in FF and Chrome. Why? Because FF and Chrome are cross-platform, I and my fellow developers can test on our OS of choice. Wit…

With IE, a testing environment costs my company about $300 per developer. I.e., miniscule relative to the cost of actually having a developer.

Or compared to the cost of the developer's time for testing and writing code for it.

It's annoying that supporting IE costs one Windows license. It's painful that it's so far from standards compliance.

Post reply on HN