@strypey @carcinopithecus @alcinnz @ohyran @ckeen @arunisaac

Throw in SVG and you can do gorgeous (semi-)interactive data visualization, too – or even build weird custom GUIs…

And heck, even partial page updates – the one thing actually giving JS a right to exist – could just be built into HTTP/HTML.

@phryk @strypey @carcinopithecus @ohyran @ckeen @arunisaac I'm in the middle of writing up what I see for replacing JavaScript in future browsers, but certainly the primary one would be to allow links and forms to insert their responses anywhere in their page!


Much like Intercooler.js implements.

And maybe I'll make some more progress on that this weekend. Perhaps throw in a note about SVG.

@alcinnz For SVG, an interesting point would be mandating support for <foreignElement> as that allows you to insert HTML into your SVG (very useful for properly formatted descriptions in data visualizations for example).

Currently Firefox supports it while Chrome doesn't.


@alcinnz Another point would be actually including support for push functionality.

The way I always thought it'd make sense to implement this is adding an extra attribute that acts as id for the data displayed in an element.

So you define a data container like <div data-id="fnord">some stuff in here</div>

The server then sends something like {'fnord': '<em>New</em> stuff!'} and the browser would substitute the content of every element with data-id="fnord" for the corresponding value .

@phryk I'm currently looking at poll rather than push, which could enable opt-in to the extra networking and might be simpler to implement.

But ultimately I don't see it making much difference.

Sign in to participate in the conversation

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!