Re:Most expensive javascript ever
by ubernostrum on Tuesday July 21, 2009 @07:10AM
(#716045)
If Opera were significantly and wildly incompatible with other "popular" browsers like Firefox and Safari, you might have a point, but not much of one.
But the plain fact is that, these days, the only browser which incurs support costs high enough to consider cutting out is Internet Explorer. Stuff that works in any of the other browsers will, almost always, work in all of them.
can they really say it makes sense for the vendor to spend time and money testing and supporting a platform that barely anyone uses?
There's a huge gulf between "we don't support Opera" and "no version of Opera is allowed to even try to render our pages."
Re:Most expensive javascript ever
by codyrobbins on Monday July 20, 2009 @08:22PM
(#715485)
I agree. However, that's the point. Completely barring Opera means they're certain they won't receive any support requests from people using Opera. Doing otherwise means opening their support apparatus to people using Opera, who might find all sorts of things wrong with the software and not realize it's because the software isn't tested with it.
Of course, given the small number of people using Opera, the question is whether there would really be much of a burden on their resources.
Also, is Opera unable to recognize that the vendor has limited engineering and support resources, and that supporting a browser with limited market share has ramifications for both those things? Wikipedia says Opera has less than 1% of browser market share. I have nothing against Opera, but from a neutral point of view, can they really say it makes sense for the vendor to spend time and money testing and supporting a platform that barely anyone uses?
I feel like Opera should be asking why the vendor feels the need to do this, rather than getting self-righteous about it.