Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

APIs that will transform the Web in 2013

blog.alexmaccaw.com

Post reply on HN
Print view View original

61–70 of 108 posts

Re: APIs that will transform the Web in 2013

#61

Post by azakai »

1. First I heard about GLSL custom CSS filters. Is this on track to being standardized? I suspect Microsoft would never support it, for example.

2. Chrome Apps? What does that have to do with the web? It's a Chrome thing, not a web thing (those apps don't run anywhere else). I guess the author is a Chrome fan based on the end of the article though so that figures.

3. No WebRTC, and no WebGL? Perhaps ironic I mention it given my point #1, but these two are going to make huge strides in 2013, and their effects are much larger than nicer CSS filters.

Re: APIs that will transform the Web in 2013

#62

Post by dreamdu5t »

tjholowaychuk wrote: post #16

web components are still very flawed, they completely ignore a slew of problems, and still promote tons of global variables which is just a major no no. Some of the features that come along with the web component spec are fantastic, but the way they're doing it is quite wrong IMO, and it cant really be done right from a browser point of view really, the bulk of this should still be user-land, I find it a little scary…

Agreed. It's frightening to see people embrace web components while completely ignoring the usability issues, and adopting the attitude of "develop first, think about API design later."

Re: APIs that will transform the Web in 2013

#63

Post by yuhong »

timmclean wrote: post #45
superasn wrote: post #37

CSS filters are already in Chrome and Safari, and allow advanced styling as as blurring, warping and modifying the color intensities of elements. Isn't it funny that the first browser to implement these "filters" was IE 4.0 [1]. And at that time using any of these filters was a bit frowned upon and amateurish. Now suddenly everyone is gung-ho about it and calling it the API that will transform the web in 2013. [1] ht…

Except IE's filters were an unrelated proprietary technology with an ugly syntax: filter: progid:DXImageTransform.Microsoft.Blur(pixelradius=2); compared to filter: blur(2px);

Actually the first syntax was introduced in IE 5.5. The second is very similar to the IE4 syntax, so why not make it compatible?

Re: APIs that will transform the Web in 2013

#64

Post by yuhong »

superasn wrote: post #37

CSS filters are already in Chrome and Safari, and allow advanced styling as as blurring, warping and modifying the color intensities of elements. Isn't it funny that the first browser to implement these "filters" was IE 4.0 [1]. And at that time using any of these filters was a bit frowned upon and amateurish. Now suddenly everyone is gung-ho about it and calling it the API that will transform the web in 2013. [1] ht…

And IE10 got rid of them: http://blogs.msdn.com/b/ie/archive/2012/06/04/legacy-dx-filt...

Re: APIs that will transform the Web in 2013

#65

Post by bcoates »

azakai wrote: post #61

1. First I heard about GLSL custom CSS filters. Is this on track to being standardized? I suspect Microsoft would never support it, for example. 2. Chrome Apps? What does that have to do with the web? It's a Chrome thing, not a web thing (those apps don't run anywhere else). I guess the author is a Chrome fan based on the end of the article though so that figures. 3. No WebRTC, and no WebGL? Perhaps ironic I mention…

Isn't WebGL still a disaster that bears an uncanny resemblance to a C .h file mechanically transformed into a browser API?

Re: APIs that will transform the Web in 2013

#66

Post by InclinedPlane »

st0p wrote: post #17

None of this will work in IE7, IE8, IE9 or IE10. This will transform absolutely nothing on the web for many years to come. I can understand people getting hyped up about cool new tech like this, but the article has way too much hyperbole to take any of it seriously.

This isn't 2005 anymore, IE is becoming rapidly less relevant as time goes on. Other desktop browsers have been gaining marketshare and the most popular mobile devices do not use IE. Currently, IE marketshare is on a half-life of about 3.5 years, in another few years IE may even become inconsequential. In the meantime I think IE has lost its ability to prevent advancement of web technology merely by lagging on adoption. Indeed, I think the opposite trend may become true, where IE's lack of features which all the "cool kids" are using on cutting edge sites will drive IE usage even farther down.

Re: APIs that will transform the Web in 2013

#67

Post by pavel_lishin »

BadDesign wrote: post #33
st0p wrote: post #17

None of this will work in IE7, IE8, IE9 or IE10. This will transform absolutely nothing on the web for many years to come. I can understand people getting hyped up about cool new tech like this, but the article has way too much hyperbole to take any of it seriously.

So what?! How much time it takes to install a different/newer browser? I tell you - less than a minute. There.

> How much time it takes to install a different/newer browser?

In a corporate environment? Anywhere from days to years.

Re: APIs that will transform the Web in 2013

#68

Post by bzbarsky »

azakai wrote: post #61

1. First I heard about GLSL custom CSS filters. Is this on track to being standardized? I suspect Microsoft would never support it, for example. 2. Chrome Apps? What does that have to do with the web? It's a Chrome thing, not a web thing (those apps don't run anywhere else). I guess the author is a Chrome fan based on the end of the article though so that figures. 3. No WebRTC, and no WebGL? Perhaps ironic I mention…

Yeah, it's amusing how the article talks about things that have been shipping in browsers other than Chrome for years (generators, say) and only talks about Chrome supporting them...

Re: APIs that will transform the Web in 2013

#69

Post by azakai »

bcoates wrote: post #65
azakai wrote: post #61

1. First I heard about GLSL custom CSS filters. Is this on track to being standardized? I suspect Microsoft would never support it, for example. 2. Chrome Apps? What does that have to do with the web? It's a Chrome thing, not a web thing (those apps don't run anywhere else). I guess the author is a Chrome fan based on the end of the article though so that figures. 3. No WebRTC, and no WebGL? Perhaps ironic I mention…

Isn't WebGL still a disaster that bears an uncanny resemblance to a C .h file mechanically transformed into a browser API?

No, not by any reasonable account.

Re: APIs that will transform the Web in 2013

#70

Post by yuhong »

hfz wrote: post #60
superasn wrote: post #37

CSS filters are already in Chrome and Safari, and allow advanced styling as as blurring, warping and modifying the color intensities of elements. Isn't it funny that the first browser to implement these "filters" was IE 4.0 [1]. And at that time using any of these filters was a bit frowned upon and amateurish. Now suddenly everyone is gung-ho about it and calling it the API that will transform the web in 2013. [1] ht…

Similar to how IE's box model was deemed incorrect until fast-forward today and people realized that their box model was simpler and easier to use compared to the standard. See: http://paulirish.com/2012/box-sizing-border-box-ftw/

http://hsivonen.iki.fi/almost-precedent/

There is a reason why WHATWG considers HTML a living standard.

Post reply on HN