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

71–80 of 108 posts

Re: APIs that will transform the Web in 2013

#71

Post by skyhook_mockups »

awj wrote: post #58
skyhook_mockups wrote: post #34

Earlier quoted context omitted.

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.

As my original post said this all applies to webapplications. If you're building a consumer facing brochure site then you neither want nor need most of these new web features.

Have you actually used or tried to deploy ChromeFrame? Its plenty ready for prime time, and features:

1. A 60sec installation

2. No browser restart required

3. No admin rights necessary

4. IE6+

5. Autoupdate just like regular chrome

Even the most technophobic user can follow 2 links to be able to use an app they really want to use.

And remember this is all about applications, not your average brochure site.

Re: APIs that will transform the Web in 2013

#72

Post by jQueryIsAwesome »

fudged71 wrote: post #48
purephase wrote: post #32

Earlier quoted context omitted.

This is cool. I didn't realize this was coming out of the Android camp and into general use.

I was ecstatic when I'd first heard of it! The main draw I have towards Android rather than iOS is the ease of use of the interaction between apps. If the web can have the same benefit that I see on mobile, then there could be some explosively innovative interactions possible. Web-to-web interactions right now are mostly just copy-paste and saving things to your desktop to upload again. It would be incredibly innovat…

It would be really cool, but the reality is that websites that uses similar kind of data are usually direct competitors and work as closed gardens (Facebook vs Google+, Vimeo vs Youtube, Bing vs Google). But I do hope that at least multimedia tags will be able be dragged and accepted by other websites (drag a video tag to YouTube, drag a pdf to dropbox, etc)

Re: APIs that will transform the Web in 2013

#73

Post by bcoates »

taitems wrote: post #38
transfire wrote: post #24

ES6 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.

Languages don't work that way. Anyone touching the language has to deal with the whole thing.

Tooling ES6 code is more complicated, learning the language is much more complicated (it was nicely minimalist compared to other mainstream languages). At least they mostly stuck to mucking with the syntax--saying they turned it into Java is crazy until they introduce Java's broken threading.

Re: APIs that will transform the Web in 2013

#74

Post by paulgb »

jbigelow76 wrote: post #26
highwind wrote: post #4

Once thing I still have hard time understanding is Chrome App Store and Google Chrome Apps. I'm guessing it's something akin to Adobe Air, but has there been any success stories with Air? Also, I feel like Chrome App Store goes against the idea of open web.

I'm tempted to go make fake HN accounts just so I can come back and up vote this more. I can understand, if not personally endorse, the need for "apps" on smart phones where access to functionality like the accelerometer is not available through APIs used to create browser based apps, but Google's insistence on trying to push app stores in the browser will just lead to pointless balkanization of the open web.

It doesn't subtract from your point, but both iOS and Android do in fact have native-quality browser accelerometer support.

Re: APIs that will transform the Web in 2013

#75

Post by danbeam »

transfire wrote: post #24

ES6 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.

lol, my favorite part was when you thought a totally hacked together, duck-typed, uncompiled language would produce less buggy code than Java!

Re: APIs that will transform the Web in 2013

#76

Post by magicalist »

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…

To answer (1):

http://www.w3.org/TR/filter-effects/

I don't really see them making a large impact in 2013, but we may see them on by default in a shipping browser...we'll see.

Working group(s) discussion has been happening for quite a while now, though. Microsoft has indeed already stated that they would prefer not to specify the particular shading language that needs to be used. There was quite a long discussion on that point, as you can imagine:

http://lists.w3.org/Archives/Public/public-fx/2012JulSep/007...

Re: APIs that will transform the Web in 2013

#77

Post by rurounijones »

magicalist wrote: post #76
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…

To answer (1): http://www.w3.org/TR/filter-effects/ I don't really see them making a large impact in 2013, but we may see them on by default in a shipping browser...we'll see. Working group(s) discussion has been happening for quite a while now, though. Microsoft has indeed already stated that they would prefer not to specify the particular shading language that needs to be used. There was quite a long discussion on…

Wow that second link makes for some seriously entertaining reading. Recommended for anyone who hasn't seen an industry standards body forum before.

Warning: It may shatter (or confirm) your preconceptions quite strongly

Re: APIs that will transform the Web in 2013

#79

Post by magicalist »

rurounijones wrote: post #77
magicalist wrote: post #76

Earlier quoted context omitted.

To answer (1): http://www.w3.org/TR/filter-effects/ I don't really see them making a large impact in 2013, but we may see them on by default in a shipping browser...we'll see. Working group(s) discussion has been happening for quite a while now, though. Microsoft has indeed already stated that they would prefer not to specify the particular shading language that needs to be used. There was quite a long discussion on…

Wow that second link makes for some seriously entertaining reading. Recommended for anyone who hasn't seen an industry standards body forum before. Warning: It may shatter (or confirm) your preconceptions quite strongly

It was a really poor showing, and not at all productive. Keep in mind, though, that the mailing lists for the SVG and CSS working groups are open to the public, so while it was bound to get contentious, the completely unhelpful flaming was not coming from an actual member of those groups (at least not at the start). If anyone is interested in participating in these kinds of discussions, please keep in mind that reenacting your own take on Eternal September is not helpful in any way. Acclimatize. Entrenchment and flame wars only gets us html5 and EcmaScript 4.

Re: APIs that will transform the Web in 2013

#80

Post by fudged71 »

jQueryIsAwesome wrote: post #72
fudged71 wrote: post #48

Earlier quoted context omitted.

I was ecstatic when I'd first heard of it! The main draw I have towards Android rather than iOS is the ease of use of the interaction between apps. If the web can have the same benefit that I see on mobile, then there could be some explosively innovative interactions possible. Web-to-web interactions right now are mostly just copy-paste and saving things to your desktop to upload again. It would be incredibly innovat…

It would be really cool, but the reality is that websites that uses similar kind of data are usually direct competitors and work as closed gardens (Facebook vs Google+, Vimeo vs Youtube, Bing vs Google). But I do hope that at least multimedia tags will be able be dragged and accepted by other websites (drag a video tag to YouTube, drag a pdf to dropbox, etc)

Hmm, I see it as the opposite. Why wouldn't Facebook want to register themselves as a sharing output for images and text? They want us to share as much as possible, and this would just make it easier for users.

Otherwise, you'd see sharing menus across the web with "Google+, Twitter, etc." on them and no Facebook. Not a position I think they would want to be in.

Post reply on HN