Wonderful [sarcasm].
So now when I create something that requires a browser that actually has good hardware acceleration, it will be a dastardly turd of a performer in Opera.
Opera confirms support for WebKit vendor prefixes
31–40 of 50 posts
Re: Opera confirms support for WebKit vendor prefixes
#32I know everyone talks about fragmentation concerns, and WebKit as the new IE6, but does this argument really make any sense? Internet Explorer was a poorly updated, closed source product that only worked on a single platform; WebKit is open source, maintained by two separate companies (that are basically locked in a cold war), and is available on all major platforms. If anything, why isn't the notion of a single rend…
A monopoly leads to a lack of innovation. A lack of innovation leads to proprietary solutions. Proprietary solutions lead to a lack of innovation. This is what happened with Microsoft and IE6. IE6 launched in 2001. Microsoft didn't care updating it for the next 6 years. This lead to a rise of Flash in websites, which at the time seemed like a good solution to fill the lack of support of CSS. But then it also lead to…
>A monopoly leads to a lack of innovation. A lack of innovation leads to proprietary solutions. Proprietary solutions lead to a lack of innovation. This is what happened with Microsoft and IE6.
But why should we blame monopoly? MS had no competitor in the desktop space (even now, OS X has like 10% and Linux around 1%), and still they improved Windows continuously from 3.1 to 8. Same for Office. After the demise of WordPerfect, it never had any serious competitor --even today the vast majority of people choose it over the free OpenOffice, whereas Google Docs have insignificant user share (from what I've read). Still, MS continuously added things to do. Same for Photoshop, Illustrator, etc. They did not have any competitor, especially with Macromedia acquired (Corel's software is not used by the majority of graphic designers, and almost nobody uses Gimp outside of Linux), and yet, Photoshop just received it's most substantial update to date.
So, monopoly != necessary stagnation.
Re: Opera confirms support for WebKit vendor prefixes
#33Earlier quoted context omitted.
Opera is not making WebKit the new IE; web developers who only use -webkit CSS prefixes have done that.
By this move they are essentially legitimizing it. The only way to oppose stupidity is to not agree to it.
Exactly, couldn't Opera instead release an advisory tool which examines stylesheets and points out how to convert -webkit- prefixes to a) standards or b) -o- prefixes?
Re: Opera confirms support for WebKit vendor prefixes
#34I know everyone talks about fragmentation concerns, and WebKit as the new IE6, but does this argument really make any sense? Internet Explorer was a poorly updated, closed source product that only worked on a single platform; WebKit is open source, maintained by two separate companies (that are basically locked in a cold war), and is available on all major platforms. If anything, why isn't the notion of a single rend…
WebKit is not controlled by 2 companies and WebKit is not a single rendering engine. WebKit is a single upstream project, the downstream browsers differ from each other just as much as they differ from gecko or presto based browsers.
The "as much" part is BS. Webkit browsers are FAR more alike rendering-wise than they are with any third party engine.
Re: Opera confirms support for WebKit vendor prefixes
#35Earlier quoted context omitted.
Opera is not making WebKit the new IE; web developers who only use -webkit CSS prefixes have done that.
By this move they are essentially legitimizing it. The only way to oppose stupidity is to not agree to it.
>Exactly, couldn't Opera instead release an advisory tool which examines stylesheets and points out how to convert -webkit- prefixes to a) standards or b) -o- prefixes?
So all of 0.1% of web designers who use Opera can change them?
Re: Opera confirms support for WebKit vendor prefixes
#36Wonderful [sarcasm]. So now when I create something that requires a browser that actually has good hardware acceleration, it will be a dastardly turd of a performer in Opera.
No, it will continue to be fast on opera and firefox and to be a "dastardly turd" on chrome and safari: only some selected -webkit- properties will be translated by opera.
Re: Opera confirms support for WebKit vendor prefixes
#37Earlier quoted context omitted.
The other vendors choose when/if they merge Google's commits. The grandparent's comment made WebKit sound like a single entity when it's actually several competing companies with overlapping but also differing views on things. They just happen to be working from a common code base.
Some of Google's engineers have Webkit priveleges. Webkit is a single rendering engine - this should not be confused. It is used by several browsers, who of course, use slightly different compilation configurations, but I doubt that the web designer ever needs to concern themselves with that!
No Alex, not all WebKit browsers have feature parity with each other.
Re: Opera confirms support for WebKit vendor prefixes
#38Earlier quoted context omitted.
WebKit is not controlled by 2 companies and WebKit is not a single rendering engine. WebKit is a single upstream project, the downstream browsers differ from each other just as much as they differ from gecko or presto based browsers.
The "as much" part is BS. Webkit browsers are FAR more alike rendering-wise than they are with any third party engine.
Any difference in rendering between Gecko and WebKit is a bug.
Re: Opera confirms support for WebKit vendor prefixes
#39Earlier quoted context omitted.
Is vendor prefixing really worse than UA sniffing Paul? Your employer is one of the worst offenders of the latter (not blaming you). Maps, for example, falls back to a very primitive version in Firefox Mobile despite it being perfectly capable of rendering the more advanced site. My attitude is that if you don't want to test on anything other than Safari Mobile and Android Browser then fine, don't test, but let the s…
> don't test, but let the site degrade gracefully In practice, graceful degradation requires testing.
I chose the wrong words, my meaning was that they should allow non-WebKit browsers the chance to render the site and if they fail, they fail. Forwarding the browser to another URL because you whitelist only a couple of UAs is a bad bad idea.
Re: Opera confirms support for WebKit vendor prefixes
#40I know everyone talks about fragmentation concerns, and WebKit as the new IE6, but does this argument really make any sense? Internet Explorer was a poorly updated, closed source product that only worked on a single platform; WebKit is open source, maintained by two separate companies (that are basically locked in a cold war), and is available on all major platforms. If anything, why isn't the notion of a single rend…
WebKit is not controlled by 2 companies and WebKit is not a single rendering engine. WebKit is a single upstream project, the downstream browsers differ from each other just as much as they differ from gecko or presto based browsers.
Chrome and Safari do differ from each other. But "as they differ from gecko or presto based browsers"? No. Nearly all engine-related bug reports we get apply to all WebKit ports. Gecko and WebKit only rarely have bugs in common.