Building Better Interfaces with SVG (2015)

Re:Building Better Interfaces with SVG (2015) by stupidcar on Sunday January 08, 2017 @07:00PM (#13352944)

I don't know, but I really, really don't hope we get to the point where every web application ships a bespoke, WebAssembly rendering engine and treats the browser as WebGL dumb terminal. That sounds like a complete dystopia.

Think loading times are bad on script-heavy websites now? Wait until every web app uses its own mix of graphics, font and layout libraries, all compiled from C/C++ to WebAssembly and shipped in a 100MB blob. And rendered without any integration with accessibility technologies, and with basic things like copy and paste disabled to stop you "stealing" content. No thanks.

[ Parent | on HN ]

Re:Building Better Interfaces with SVG (2015) by jstewartmobile on Sunday January 08, 2017 @07:33PM (#13353089)

That's probably going to happen anyway. Just sayin'.

[ Parent | on HN ]

Re:Building Better Interfaces with SVG (2015) by int_19h on Monday January 09, 2017 @12:15AM (#13354175)

That'll be the first step. Then people will notice all those crazy download times, and someone will figure out that things could be better if they could write a single reusable "container" app in WebAssembly and WebGL that could host nearly arbitrary content, described in some kind of high-level markup language that's reasonably concise...

[ Parent | on HN ]

Re:Building Better Interfaces with SVG (2015) by SixSigma on Monday January 09, 2017 @06:52AM (#13355666)

SVG markdown

[ Parent | on HN ]

Re:Building Better Interfaces with SVG (2015) by mtdewcmu on Sunday January 08, 2017 @10:26PM (#13353781)

It costs more to employ C/C++ developers than Javascript/HTML/CSS developers, so people are not going to recreate everything with bespoke C/C++.

[ Parent | on HN ]