Runtime.js – JavaScript library OS(medium.com)
medium.com
Runtime.js – JavaScript library OS
https://medium.com/@iefserge/runtime-js-javascript-library-os-823ada1cc3c
7 comments
A cool example: http://roscidus.com/blog/blog/2015/04/28/cuekeeper-gitting-t...
Thanks for pointing this out--it brought my attention to the author's Irmin backend, based on the browser's implementation of IndexedDB:
https://github.com/talex5/irmin-indexeddb
That said, trying out this demo [1] of Cuekeeper gives an IndexedDB error message on Firefox 40.0.3 on Linux; perhaps IndexedDB is somehow not enabled.
[1] http://roscidus.com/blog/cuekeeper/
https://github.com/talex5/irmin-indexeddb
That said, trying out this demo [1] of Cuekeeper gives an IndexedDB error message on Firefox 40.0.3 on Linux; perhaps IndexedDB is somehow not enabled.
[1] http://roscidus.com/blog/cuekeeper/
On additional huge benefit to having a statically typed reflection-less language for a unikernel would be that dead code elimination becomes rather a lot easier. (You'd need whole-program analysis, but that's pretty doable for the ML's of the world, see e.g. MLton.)
I'm confused. If you're writing OCaml in the first place, why not just directly run it on MirageOS?
The obvious benefit of a JS VM unikernel is that you get to write your application in JavaScript...
The obvious benefit of a JS VM unikernel is that you get to write your application in JavaScript...
It's not clear to me and I don't have any experience with unikernels, so please accept my grain of salt and I apologize if I misspeak.
If you're starting with MirageOS, then obviously makes sense to just run MirageOS a bare-metal hypervisor. But if you're starting with the assumption that you will be running in a JS VM, then you have two options: build a unikernel in JS, or compile one to JS. The later option (MirageOS compiled to JS) also happens to leave open the possibility of easily being ran on a bare metal hypervisor with the unikernel implementation itself also running on bare metal (without a language level virtual machine) - because OCaml executes without a language level virtual machine (it's more like C++ in that sense).
> The obvious benefit of a JS VM unikernel is that you get to write your application in JavaScript...
What are some reasons why that would be a good thing in the case of unikernels? (I'm genuinely asking) The type system and invariants that it enforces are one of the things that makes OCaml based unikernels such a compelling idea to me. JavaScript, although I obviously find it useful for many things, doesn't seem to have as much appeal in this case.
Relevant to security: See MirageOS's Bitcoin Pinata project: http://amirchaudhry.com/bitcoin-pinata/
Edit: Again, it's still cool to see this project, and it's a great way to get more people experimenting with the idea of unikernels.
If you're starting with MirageOS, then obviously makes sense to just run MirageOS a bare-metal hypervisor. But if you're starting with the assumption that you will be running in a JS VM, then you have two options: build a unikernel in JS, or compile one to JS. The later option (MirageOS compiled to JS) also happens to leave open the possibility of easily being ran on a bare metal hypervisor with the unikernel implementation itself also running on bare metal (without a language level virtual machine) - because OCaml executes without a language level virtual machine (it's more like C++ in that sense).
> The obvious benefit of a JS VM unikernel is that you get to write your application in JavaScript...
What are some reasons why that would be a good thing in the case of unikernels? (I'm genuinely asking) The type system and invariants that it enforces are one of the things that makes OCaml based unikernels such a compelling idea to me. JavaScript, although I obviously find it useful for many things, doesn't seem to have as much appeal in this case.
Relevant to security: See MirageOS's Bitcoin Pinata project: http://amirchaudhry.com/bitcoin-pinata/
Edit: Again, it's still cool to see this project, and it's a great way to get more people experimenting with the idea of unikernels.
> What are some reasons why [using JS] would be a good thing in the case of unikernels?
The same reason it would be a good thing to use JS under any circumstances: there's already a huge supply of developers familiar with it and its ecosystem, it's available on pretty much every platform (now including at least one dedicated unikernel environment), it's a natural fit for web application development, and so on.
It's clear why unikernels and OCaml go together so nicely: immutability is a concept central to them both.
That said, the affordances of using a unikernel seems fairly orthogonal to the choice of language, IMO.
The same reason it would be a good thing to use JS under any circumstances: there's already a huge supply of developers familiar with it and its ecosystem, it's available on pretty much every platform (now including at least one dedicated unikernel environment), it's a natural fit for web application development, and so on.
It's clear why unikernels and OCaml go together so nicely: immutability is a concept central to them both.
That said, the affordances of using a unikernel seems fairly orthogonal to the choice of language, IMO.
> it's available on pretty much every platform
And now so is OCaml, Elm, PureScript, C++, and anything else that compiles to JS.
> it's a natural fit for web application development, and so on.
Now that other languages are beginning to compile to JS, they are also becoming increasingly natural for web app development.
> there's already a huge supply of developers familiar with it and its ecosystem.
This is definitely true.
And now so is OCaml, Elm, PureScript, C++, and anything else that compiles to JS.
> it's a natural fit for web application development, and so on.
Now that other languages are beginning to compile to JS, they are also becoming increasingly natural for web app development.
> there's already a huge supply of developers familiar with it and its ecosystem.
This is definitely true.
This library reminds me of some of the "future" introduced in this (satirical, yet insightful) talk: https://www.destroyallsoftware.com/talks/the-birth-and-death...
Discussion: https://news.ycombinator.com/item?id=7605687
This is extremely cool, by the way.
This is extremely cool, by the way.
Relevant, as always: https://xkcd.com/1508/
I'm not sure if this will be relevant or useful information, but I understand that a GSoC project added Lua to SYSLINUX. I'm not sure what the specifics of the memory access/stack structure is; the idea is to let you run Lua scripts directly in your bootloader, and it can also open an interactive REPL.
Strangely, the effort was made to get Lua functioning, but not much has been practically done with it. Stuff like VESA support was even thrown around, but the whole thing was eventually abandoned(?!).
I see so many possibilities for something like this, generally speaking... and FYI, the code does apparently work.
Strangely, the effort was made to get Lua functioning, but not much has been practically done with it. Stuff like VESA support was even thrown around, but the whole thing was eventually abandoned(?!).
I see so many possibilities for something like this, generally speaking... and FYI, the code does apparently work.
I wonder if this could be used as an IoT/RPi OS, maybe swaping v8 for https://github.com/cesanta/v7 to make the footprint even more lightweight.
this is a great idea, thanks. I wish v7 had the same c++ API as v8 so it could be easily swapped though.
How does this work with node.js based binary/native dependencies? Also, is it possible to customize the built image with libraries, etc?
This seems really cool and a welcome replacement for the mess that is Docker.
This seems really cool and a welcome replacement for the mess that is Docker.
Quote from [1]: "Application, its dependencies and the core library are bundled up using Browserify, then packed into ramdisk image for kernel to use."
Since runtime.js uses browserify which itself is not able to handle binary/non-JS dependencies - i would say "no".
But this is just a conclusion and not an answer-by-knowledge.
[1] https://github.com/runtimejs/runtime
EDIT:
Did a quick test with bcrypt.
It failed - in contrast to a pure-JS "hello world" test.
Again, not a proof, but a stronger hint.
Since runtime.js uses browserify which itself is not able to handle binary/non-JS dependencies - i would say "no".
But this is just a conclusion and not an answer-by-knowledge.
[1] https://github.com/runtimejs/runtime
EDIT:
Did a quick test with bcrypt.
It failed - in contrast to a pure-JS "hello world" test.
Again, not a proof, but a stronger hint.
this is correct, binary dependencies are not supported. The possible way to solve this is to compile non-js code into Asm.js/WASM or directly into js. I think this makes system a bit more stable (null-pointer error in the kernel mode will crash the OS for example) and makes V8 updates much more easier.
[deleted]
From my understanding, I would say "yes." This project is trying to present itself in the same vein as Unikernels which are out to solve a similar problem as Docker but at a different level of abstraction.
>device drivers with javascript
>assemler in browser
what next?)
>assemler in browser
what next?)
I'm curious, if you wanted your unikernel to be running in a JS VM (I'm not sure what the primary motivation would be[deployment?]) why not take the approach of just compiling the type-safe MirageOS into JavaScript (possible because MirageOS/OCaml can also compile into JS). Unikernels are attractive because of, among other reasons, increased security. It's pretty well understood that a powerful type system (such as Mirage's use of OCaml) would be useful in reducing accidental security vulnerabilities as well. Come to think of it, I'd much rather trust mission critical server infrastructure to OCaml that compiled to JavaScript, over JavaScript. At the end of the day, you'd still be able to use it from within js via `require('OS')`, but its implementation would have had more bugs/vulnerabilities prevented by the type system.