Surprised Stripe isn't on here ;)
not that kind of API
APIs that will transform the Web in 2013
31–40 of 108 posts
Re: APIs that will transform the Web in 2013
#32No mention of Web Intent API?
This is cool. I didn't realize this was coming out of the Android camp and into general use.
Re: APIs that will transform the Web in 2013
#33None 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.
Re: APIs that will transform the Web in 2013
#34None 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.
the article has way too much hyperbole to take any of it seriously.
This statement is itself hyperbolic.
A lot of these advances are going to impact web applications. Sure if you're building a brochure site then you should probably stick to web technology circa 2000.
The article mentions 350MM chrome users, FF has about the same market share. That makes close of 3/4 of a billion web users who will automatically receive the updates that allow app developers to target these new features. That's a lot of potential customers.
Oh and for those who can't or don't know how to upgrade away from IE7-10 there's ChromeFrame. That covers the remaining portion of the web.
In other words... no, the article is not hyperbolic and feel free to take all of it seriously.
Re: APIs that will transform the Web in 2013
#35None 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.
IE should eventually support a lot of this also? IE10 has made some pretty big jumps. I guess they still haven't worked out having everyone on one version and automatically updating though.
Re: APIs that will transform the Web in 2013
#36None 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.
IE should eventually support a lot of this also? IE10 has made some pretty big jumps. I guess they still haven't worked out having everyone on one version and automatically updating though.
Quick, anyone know when Windows 9 comes out?
Re: APIs that will transform the Web in 2013
#37 CSS filters are already in Chrome and Safari, and allow advanced styling as as blurring, warping and modifying the color intensities of elements.
[1] http://msdn.microsoft.com/en-us/library/ms532849(v=vs.85).as...
Re: APIs that will transform the Web in 2013
#38ES6 may well be the death of Javascript. They've managed to turn Javascript into Java, which means web programming is about to turn into a buggy nightmare.
Even if what you're saying is true (which it isn't), it's completely optional. Don't want to use `let` scoping? Use `var` instead! etc.
Re: APIs that will transform the Web in 2013
#39Surprised Stripe isn't on here ;)
not that kind of API
Well, maybe. Alex works at Stripe. And wrote about having a browser API for payments.
Re: APIs that will transform the Web in 2013
#40Hard to see how ECMAScript 6 will transform the internet when everyone writing Javascript for the public web still has to support IE8.
Write the code in ES6 and compile it to ES5, then use Modernizer or some equivalent to detect which runtime is supported by the client's browser and serve the appropriate script.
Or just ignore IE8 and assume the "revenue loss" from anyone running that browser not being able to navigate your site is worth the loss of headache.
I always wonder why it is an assumption IE support is mandatory. As others in this thread have pointed out, Chrome / FF now have a combined 700 million and I'd assume between 50 - 70% of the browser marketshare. At some point, using backwards broken nonsense to support outdated browsers becomes a financially unfriendly situation, especially when you can't reproduce a lot of the newer goodness (like html5 localstorage or websockets) in older versions of IE.