You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Explain and allow for different DOM implementations to be used. Explain what types of devices scram can run on if it uses Electron, versus if it uses jsdom or another library. Provide much more detail on the types of devices and how to use scram on those devices. I think it will be a good idea to call scram as its own binary...
The text was updated successfully, but these errors were encountered:
Yes, this makes sense. I don't think we'll ever need Electron though. Node.js as a platform can be supported through something like basicHTML: Should be obsolete in lieu of basicHTML: https://github.com/WebReflection/basicHTML, and then other implementations can be supported with an implementation similar to basicHTML. In fact, perhaps we will be able to compile basicHTML to web assembly and use it on much more resourse-constrained devices, and perhaps if Rust can import web assembly libraries, we can really share all of this implementation. Follow basicHTML and WebAssembly, perhaps an AssemblyScript implementation will be the easiest thing to do at first. Though, we should probably keep all of these repositories separate, who knows.
Explain and allow for different DOM implementations to be used. Explain what types of devices scram can run on if it uses Electron, versus if it uses jsdom or another library. Provide much more detail on the types of devices and how to use scram on those devices. I think it will be a good idea to call scram as its own binary...
The text was updated successfully, but these errors were encountered: