6 ms·
How about a web spec for creating sandboxed native UI? Would go nicely with WASM.
by iLoch 10y ago
How about a web spec for creating sandboxed native UI? Would go nicely with WASM.
- themihai 10y agoThere is already one(i.e. HTML5 input types) but it's quite incomplete and poorly supported so we have to reinvent the wheel with CSS and JS which makes the web apps inconsistent and slow. The main issue is that the internet must be backwards compatible and browser vendors are reluctant to provide shiny features due the maintenance costs. Hopefully WASM will fix the performance issue and the internet speed will get fast enough to compile and serve mature frameworks such Cocoa.
- duaneb 10y agoIs there a way to bypass HTML completely?
- pjmlp 10y agoYes, you have poor souls re-inventing desktop UI toolkits by making the web page a gigantic canvas or webgl content.
- symlinkk 10y agowhich is technically still embedded in an HTML document
- pjmlp 10y agoYes, hence why I mentioned poor souls, trying to bend a document platform into something that is natural in native code.
- duaneb 10y agoYea, but that still involves calling through HTML/DOM to access basic graphics contexts.
- pjmlp 10y agoYes, hence why I mentioned poor souls, trying to bend a document platform into something that is natural in native code.
- st3v3r 10y agoYes. Make a native app.
- rhelmer 10y agoThere is a design doc describing non-Web embedding for WASM: https://github.com/WebAssembly/design/blob/master/NonWeb.md https://github.com/WebAssembly/design/blob/master/NonWeb.md That doesn't mention HTML but focuses on avoiding JS entirely, so presumably there'd be some more direct way to invoke the program (but don't take my word for it ;) )