tldr version: http://tldr.io/tldrs/50b6a7a7bb22039977000ced
I enjoy writing client or server Javascript (yeah, really!), but some of these new features (such as generators) are something I very much look forward to.
APIs that will transform the Web in 2013
51–60 of 108 posts
Re: APIs that will transform the Web in 2013
#52I think the funniest part of this is expecting web folks to write good GLSL code. That's going to be a laugh riot. Especially, since, you know, they can't make useful guarantees on things like available uniforms, varyings, samplers, etc.
Re: APIs that will transform the Web in 2013
#53None 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.
Mobile is eating the world, and a lot of people, myself included, are using online instead of native apps. I have already cursed the gods for the horrible input type support across many browsers.
I think "doesn't work in IE" could turn into a problem, if certain web services won't work on IE Mobile. It might be the best incentive Microsoft has ever had to make step it up.
Re: APIs that will transform the Web in 2013
#54Earlier quoted context omitted.
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?
Possibly never. The next version is near, though: http://www.theverge.com/2012/11/28/3693368/windows-blue-upda....
Re: APIs that will transform the Web in 2013
#55None 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.
You'd be surprised by how many people won't do that. In my opinion, it's your job as a designer / developer to make sure your product works for as many people as reasonably possible, and not expect users to jump through hoops (no matter how small) to use it.
Re: APIs that will transform the Web in 2013
#56Earlier quoted context omitted.
So what?! How much time it takes to install a different/newer browser? I tell you - less than a minute. There.
You'd be surprised by how many people won't do that. In my opinion, it's your job as a designer / developer to make sure your product works for as many people as reasonably possible, and not expect users to jump through hoops (no matter how small) to use it.
I definitely agree (to a point...I don't test with IE6 or IE7 anymore unless budget and time is specifically allocated for them), but "make sure your product works for as many people as reasonably possible" is not to be confused with "make sure your product works the same for as many people as reasonably possible".
I'm happy to serve static images to older browsers with an unintrusive note telling them what they're missing and how they can get it.
Re: APIs that will transform the Web in 2013
#57Earlier quoted context omitted.
You'd be surprised by how many people won't do that. In my opinion, it's your job as a designer / developer to make sure your product works for as many people as reasonably possible, and not expect users to jump through hoops (no matter how small) to use it.
I definitely agree (to a point...I don't test with IE6 or IE7 anymore unless budget and time is specifically allocated for them), but "make sure your product works for as many people as reasonably possible" is not to be confused with "make sure your product works the same for as many people as reasonably possible". I'm happy to serve static images to older browsers with an unintrusive note telling them what they're m…
Oh I agree that graceful degradation is a very viable option for older browsers.
Re: APIs that will transform the Web in 2013
#58None 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 recei…
> 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.
Most people who can't or don't know how to upgrade away from IE7-10 won't be able to manage installing a plugin either. That aside, I don't consider a beta plugin to be an acceptable answer to this question in any context.
Re: APIs that will transform the Web in 2013
#59Earlier quoted context omitted.
> I always wonder why it is an assumption IE support is mandatory. Because for many, the use of IE is mandatory. Depending on what service we're talking about, a lot of the IE traffic is going to come from people who work at companies that require the use of their approved/installed software. Every time there's a post about IE there are few people who come out of the woodwork to comment about how they only use Window…
Depending on the service, it may be that they shouldn't use it while at work in the first place. But that's an aside, there's a simple technical solution. Every time there's a post about IE, and every time someone thinks (or believes themselves to be an example that) there's a single person on the planet who has to live with IE >= 6 when they don't want to, someone in the thread mentions Chrome Frame.
Depending on the service, it may be that they shouldn't use it while at work in the first place.
Sure. But if you run an online store it doesn't exactly benefit you to tell people when they should shop with you and when they shouldn't. Supporting IE may well mean higher sales.
Re: APIs that will transform the Web in 2013
#60CSS 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/