Hacker News Reader

Comment by irrational | Hacker News Reader

At my work we just decided this week that we will no longer support IE or Edge. We won't actively block them (or show a message) and if the site works in those browser then great. But, we won't test in IE or Edge and we won't make any bug fixes just for those browsers. Frankly the number of users using those browsers (low for our site) versus the number of hours required to fix problems with those browsers (high in our experience) makes it a poor business decision to continue to support them. Though, lets face it, some of the decision also come down to a sense of Schadenfreude after all the pain MS gave to web developers for so long. I started as a web developer in 1996 and I'd be delighted if both IE and Edge went away forever.

View on HN

> I'd be delighted if both IE and Edge went away forever.

To be fair Edge is a pretty solid browser these days, I don't think you can put them on the same league. I've been using it for some time now and other than a slightly different font rendering engine I have yet to find a fault on it; everything works like you would expect in a modern browser. Development wise, we test for Edge ocasionally and so far we haven't come across Edge-specific quirks like the good ol' days of IE.

You mean you haven't found any Edge edge cases?

(Sorry I couldn't help myself)

How Edgey.

Not bad [0]; although still a bit of catching up to do, it's nowhere near as far behind as IE traditionally was. Apparently, Edge is the first desktop browser to support columns properly, which I give it massive props for.

[0] http://caniuse.com/#compare=edge+13,chrome+51

SVG rendering is still wonky, FWIW.

how so?

I recently ran into this. I was putting an SVG into an <img> tag and sized it with CSS. In every other browser, it worked as expected. The SVG filled the space and stretched to the set dimensions. In EDGE, the SVG appeared tiny at the top-left of the space the <img> took up. I could not figure out a way around it. Had to convert it to a PNG. It seems that it handles SVGs as background images just fine.

I use SVGs all the time in Edge, styled appropriately. Edge however considers (as the spec says) that the bounds of the image are at the bounds of the "page" (as Inkscape sees it, in my experience)

I do The Bad Thing™ with inline styling on occasion, but I've had no problems:

Works 100% fine in IE using a layout kit like Marx or Twitter Bootstrap every time.

>Development wise, we test for Edge ocasionally and so far we haven't come across Edge-specific quirks like the good ol' days of IE.

Edge is simply expansive to test for, because at the places where i worked the only windows laptops (that are locked down like Azkaban for obvious reasons) around were those of the sales people. Majority of the developers on linux, where the designers are on macs.

Unless it is actively formalized, Edge ends up not getting a lot of testing with anything we make.

It had some annoying CSS quirks that pissed me off last time I had to deal with compatibility issues.

I mean, that's fair for you to make that business decision, but if I'm a customer of yours and having issues, and I find out you're not supporting me, I'm just going to do business with someone else. And if that's fine with you, it's fine with me too.

Where I work, we need to use IE for many things, and we have exactly one piece of software that requires a different browser. If in the future, I have the opportunity to replace that product with something that also works in IE, I will, without hesitation. Because the frustration caused by the one IE-incompatible software outweighs the benefit it could possibly provide over a competitor.

I have seen plenty of corporate software that was supposed to work with exactly that version of IE. When you were automatically forced to upgrade to a newer version usually nothing worked anymore. In some cases even forcing the compatibility layer. I would rather see that kind of software, developers that produced it and users disappear. In my experience few things are more annoying than an IE specific website. If you are happy with it, then great for you. But I believe that you are the first person that is actually happy to use IE given the aforementioned quirks.

It's not really about being "happy" to use IE. It's about using what does the job.

Am I correct in assuming that you "need to use IE" for software that is incompatible with other browsers?

Yes. Obviously, I'm going to need to use the browser best supported by most of our infrastructure. If that rewards Microsoft's earlier behavior, so be it. I need things to 'just work' for non-technical coworkers.

Reply on news.ycombinator.com