Re:CSS 3D in Firefox, demo
by orillian on Sunday October 02, 2011 @01:32PM
(#3063408)
It's a step in the right direction and one of a number of updates that the firefox dev's seem to be making in the last couple months to catch up.
Yup, it would have been nice if they were on par with webkit a long time ago, but it's still an improvement and one to be excited about. One less thing that "only" webkit can do. This makes my job easier, especially when the client wants/needs cross browser support.
I wouldn't be to excited or proud about being "ABLE" to only work for Safari. You are shoe-boxing yourself, and as nice as it may be to have such a singular focus it's not so good; if at a later date you are ever forced to work outside the confines of your space.
Until webkit becomes the only rendering standard it behooves the web developer to be as versatile as possible within the web space to maximize their potential.
Re:CSS 3D in Firefox, demo
by sid0 on Sunday October 02, 2011 @03:47PM
(#3063801)
Until webkit becomes the only rendering standard
This shouldn't ever happen. We've been there before and seen how much it held back innovation. It is our duty both as individuals and as a collective to make sure it doesn't happen.
Re:CSS 3D in Firefox, demo
by azakai on Sunday October 02, 2011 @03:03PM
(#3063648)
> I have to say, as a web developer who is permitted to make stuff that only works in Safari, I really really love WebKit.
On the other hand, WebKit (and Safari in particular) has been very slow to add JS features Firefox has had for a while. For example, typed arrays. And the new ES6 JS bits are being prototyped in SpiderMonkey (Firefox) and V8 (Chrome), but apparently not JavaScriptCore (Safari).
Maybe Firefox cares more about JS, and Safari about CSS? Probably a huge oversimplification.
Overall though, all the major browsers seem to be doing very well these days in implementing standards. The only real holdout at this point is IE with WebGL.
Re:CSS 3D in Firefox, demo
by chc on Sunday October 02, 2011 @01:54PM
(#3063463)
The prefixes are there so browser makers can implement features that aren't settled without leaving a bunch of broken, incompatible implementations of the same attribute out there. The alternative is trying to find hacks that exploit the browser's CSS parser like we've been doing with IE since time immemorial. If you're using prefixed attributes, you're using a non-standard version of the feature.
I have to say, as a web developer who is permitted to make stuff that only works in Safari, I really really love WebKit.
Yup, it would have been nice if they were on par with webkit a long time ago, but it's still an improvement and one to be excited about. One less thing that "only" webkit can do. This makes my job easier, especially when the client wants/needs cross browser support.
I wouldn't be to excited or proud about being "ABLE" to only work for Safari. You are shoe-boxing yourself, and as nice as it may be to have such a singular focus it's not so good; if at a later date you are ever forced to work outside the confines of your space.
Until webkit becomes the only rendering standard it behooves the web developer to be as versatile as possible within the web space to maximize their potential.
This shouldn't ever happen. We've been there before and seen how much it held back innovation. It is our duty both as individuals and as a collective to make sure it doesn't happen.
On the other hand, WebKit (and Safari in particular) has been very slow to add JS features Firefox has had for a while. For example, typed arrays. And the new ES6 JS bits are being prototyped in SpiderMonkey (Firefox) and V8 (Chrome), but apparently not JavaScriptCore (Safari).
Maybe Firefox cares more about JS, and Safari about CSS? Probably a huge oversimplification.
Overall though, all the major browsers seem to be doing very well these days in implementing standards. The only real holdout at this point is IE with WebGL.