APIs that will transform the Web in 2013

Re:APIs that will transform the Web in 2013 by superasn on Wednesday November 28, 2012 @05:37PM (#4845181)

    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] http://msdn.microsoft.com/en-us/library/ms532849(v=vs.85).as...

[ Parent | on HN ]

Re:APIs that will transform the Web in 2013 by timmclean on Wednesday November 28, 2012 @06:13PM (#4845348)

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);

[ Parent | on HN ]

Re:APIs that will transform the Web in 2013 by yuhong on Wednesday November 28, 2012 @08:55PM (#4845879)

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?

[ Parent | on HN ]

Re:APIs that will transform the Web in 2013 by ilink on Thursday November 29, 2012 @12:35AM (#4846412)

GLSL isn't exactly beautiful all the time...

[ Parent | on HN ]

Re:APIs that will transform the Web in 2013 by est on Thursday November 29, 2012 @03:53AM (#4846821)

You can always write this in IE.

    filter: Blur(pixelradius=2);

[ Parent | on HN ]

Re:APIs that will transform the Web in 2013 by hfz on Wednesday November 28, 2012 @08:32PM (#4845833)

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/

[ Parent | on HN ]

Re:APIs that will transform the Web in 2013 by yuhong on Wednesday November 28, 2012 @09:22PM (#4845946)

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

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

[ Parent | on HN ]

Re:APIs that will transform the Web in 2013 by huhtenberg on Thursday November 29, 2012 @05:28AM (#4847020)

Sure, but IE screwed up more things than it got right. Way more.

[ Parent | on HN ]

Re:APIs that will transform the Web in 2013 by yuhong on Wednesday November 28, 2012 @08:57PM (#4845885)

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

[ Parent | on HN ]

Re:APIs that will transform the Web in 2013 by est on Thursday November 29, 2012 @03:57AM (#4846832)

IE7 got rid of DirectAnimation, which is basically DirectX in IE, since IE4.

And now there's WebGL.

And other features like

- DirectMusic (MIDI support)

- VRML (which is basically SVG)

- dHTML+TIME (animiation support)

- page transition effects

- render doc/ppt/xls in html

- .htc as web components

[ Parent | on HN ]

Re:APIs that will transform the Web in 2013 by icebraining on Thursday November 29, 2012 @07:06AM (#4847277)

VRML (which is basically SVG)

Not really; VRML was a 3D modeling language, while SVG is for 2D images/animations.

[ Parent | on HN ]

Re:APIs that will transform the Web in 2013 by riffraff on Thursday November 29, 2012 @10:01AM (#4847995)

I guess that was VML http://www.w3.org/TR/1998/NOTE-VML-19980513

[ Parent | on HN ]