WebSocket Applications and Vision for the Future

We rarely talk about the actual mechanics of how we develop webapps, but in this session from HTML5DevConf, we'll get into some new techniques people use to improve their experience. Iterating faster, avoiding bugs through tools, and improved automated testing are great ideas, now let's take a look at how to really incorporate them into a functional and realistic developer workflow.

[RogerGay]

Good points on rethinking browser apps and moving processing out to the browser. On that thought; I want Frames back ... not depreciated. I've been using Frames for years to section off active areas for ... let's just say different "components" of a web-page application and it's very nice. The old criticisms that led to their demise are simply no longer valid. For example, it doesn't matter that search engines can't keep track of dynamic content. New coding is too much like the very old way.

[BlastOffLabWebDesign]

Great, the future looks bright with WebSocket

[domaincontroller]

05:34 any barriers to adoption 08:23 browser support, polyfill 09:26 we do have proxy, naked websockets, work reliable, so complicated that nobody can figure out 10:24 if you know the users 11:06 we don't use websockets, proxy are a big problem, especially when payload is json 12:21 developer experience 14:16 speedy, http/2

[johnyma]

SocketIO didn't get enough love when they were talking about polyfils when in reality that solves 99% of the Websocket adoption problem by providing graceful fallback to various protocols

[RichardBronosky]

This video is less than a quarter of the full 43 minute presentation that can be found by following the link in the description and then hunting for "WebSocket Applications and Vision for the Future" or just adding to the marakana dot com domain.