This version of Vestibule is read only. It represents an archive of the community effort to produce content for Ruby Manor 4.

The Web of Tomorrow

updated over 7 years ago; latest suggestion over 7 years ago

The web is changing and new changes are coming.

How will the new RFCs will affect the web as we know it? What technologies will raise again? Is Ruby prepared for this changes?

I want to answer these questions and talk about new web technologies and how we need to change to adapt to this upcoming era.

From web sockets to WebRTC. From distributed to decentralised.

The storm is coming… are you ready?


  • The proposal author responds over 7 years ago

    I will not be explicity talking about the RFC, nor describing the protocol itself but it's more about the connotations and "side effects" of a new way of web communication.

    The three main topics are going to be:

    Camera/Mic access P2P audio/video communication P2P Raw data communication

  • 3c9da486f4ab709c368fdde6596c480a jbsf suggests over 7 years ago

    Watch out for covering too many RFCs. You might hold audience attention better by delivering a shorter talk focused on a single RFC, in somewhat greater depth. Or, if covering multiple RFCs, just take care to keep an interesting pace.

  • Acd62030df551952268e84c8fff26a5b James Adam suggests over 7 years ago

    I don't know very much about webRTC, so I don't know how interesting a talk that discusses it is going to be. I think you could improve this proposal with a couple of sentences explaining what it is, and integrating the feedback you've already provided to other suggestions by editing your proposal.

    One other way to make this proposal more compelling would be to include an outline of at least one hypothesis about how a specific RFC might affect the web as we know it, and Ruby specifically. You wouldn't need to go into much detail, but it will give a better flavour of what the presentation would be like, perhaps?

  • The proposal author responds over 7 years ago

    I'll be referring to the webRTC RFC:

    The "hard" part it's about the concurrency patterns that will involve. I'm not just trying to aboard the technology side of this but also the social impact.

    I'll be covering access to the camera, p2p video communication and p2p data communication.

  • B0636eff538e8371a7e5add37daadde7 Francis Fish suggests over 7 years ago

    Ruby doesn't need to be prepared for the changes, surely? The frameworks do - that's a question of making sure that the tooling is created to handle them.

    Can you give us some examples of what RFC's you mean and why it might be hard? I'd love a storm that means I don't have to know 5 languages to deploy even the simplest app, but I bet it will mean I need to know 8. :D

  • 11364e09c2ea04444314e94eead06e98 Roland Swingler suggests over 7 years ago

    Could you list out some of the specific technologies / protocols you would be covering?