possimpible
jupyterlab-google-drive
| possimpible | jupyterlab-google-drive | |
|---|---|---|
| 5 | 1 | |
| 199 | 391 | |
| 0.0% | - | |
| 0.0 | 0.0 | |
| over 1 year ago | 10 months ago | |
| TypeScript | TypeScript | |
| - | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
possimpible
-
WebVM: Server-less x86 virtual machines in the browser
Hey dude, I've been screwing around implementing plan9 semantics in a OS like system for the browser (https://github.com/intigos/possimpible). I'm interested in using a x86 emulator inside a webwoker that I'm using for processes so I can run x86 code. How hard is something like this? Can you give me some pointers on how to start working on this? Thanks!
- Possimpible: A Kernel Running on the Browser
- Show HN: Possimpible: A Kernel Running on the Browser
-
Unix in the Browser Tab
Wow I'm literally implementing this right now!!
I was stuck at parents for xmas and I picked Tannenbaum “distributed systems” and “Modern operating systems”, which gave me an idea of running a "kernel" on a browser. It was more of an academic exercise than anything else, but my intention was to have a the following:
Being able to unload and reload javascript. The initial idea was to write the website inside the website, but at the core level it requires having something akin to process isolation for javascript. It also requires the dom to be isolated.
Implementing 9p2000, and share resources across browsers. I’ve been reading about the ideas of plan 9 and i would like to implement something that allows me to connect point to point to other browsers and mount their FS into mine so we can share resources.
One of the cool results that I got was that since the dom is not directly changed (each process/worker has its own partial dom and every time that it changes it a delta is sent back to the main thread for sync) it allows javascript to be running somewhere else (another browser, back end server) and sync’ed back (much like vadaain, but more agnostic).
Most of the code was inspired by the linux kernel (which gave me a reason to go learn its internals) and is kinda nasty at some points but is written in typescript as some of you have already mentioned. Someone might find it interesting even if just for the educational purpose of it
https://github.com/intigos/possimpible
jupyterlab-google-drive
-
WebVM: Server-less x86 virtual machines in the browser
Also, I'm not sure if jupyterlab/jupyterlab-google-drive works in JupyterLite yet? Is it yet possible to save notebooks and other files from JupyterLite running in WASM in the browser to one or more cloud storage providers?
https://github.com/jupyterlab/jupyterlab-google-drive
What are some alternatives?
webvm - Virtual Machine for the Web
sql.js-httpvfs - Hosting read-only SQLite databases on static file hosters like Github Pages
xpra-html5 - HTML5 client for Xpra
Pion WebRTC - Pure Go implementation of the WebRTC API
gotty - Share your terminal as a web application
v86 - x86 PC emulator and x86-to-wasm JIT, running in the browser
servefolder.dev - Serve a local folder of files in your browser for easy testing without having to run a server.
wasi-libc - WASI libc implementation for WebAssembly
nabla-linux - Experimental Linux Virtual Machine based on UML and noMMU