Hacker News new | past | comments | ask | show | jobs | submit login

Actively doing something that predictably results in 7.6% less traffic to your profit generating website seems quite the questionable business decision.



How much money are you spending on dealing with IE11 bugs? My estimate from my last job is more than that 7% brings in.


Assuming IE11 users are otherwise representative of the customer base, multiply your total web based revenue by 7.6%. (If this assumption is wrong, then just check your reports to get the correct number.) If, for example, the business in question makes $10M yearly revenue, your estimate has 7 entire devs working exclusively on IE11 support fulltime, year round.

That is one fancy as fuck ecommerce site to be that reliant on features in modern browsers that lack automated transcompilation/shim generating tooling.


Are there actually IE11 bugs at a noticeably higher rate than bugs (or intentional deprecations) in other browsers? I thought we were just talking about a lack of new features that are present in Edge.

(If you were talking about IE5 or IE6 I'd understand the argument.)


most ie11 bugs that are relevant/annoying are around its flexbox impl. specifically equal height boxes via min-height and such. maybe some other fancy css animation or 3d transform stuff, but these are not terribly critical and can degrade without much impact.

thankfully, js and dom bugs are either rare or well-known and have lightweight polyfills.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: