4 ms·

Devbook allows you to integrate the "interactive code experience" natively into your docs. It's not just embedding an iframe. We can also handle use-cases like

by mlejva 5y ago

Devbook allows you to integrate the "interactive code experience" natively into your docs. It's not just embedding an iframe. We can also handle use-cases like CLIs better since you can add a full emulated terminal [0] (like RunOps did on their landing page [1]) to your website and control it with JavaScript. [0] https://github.com/devbookhq/ui https://github.com/devbookhq/ui [1] https://runops.io/ https://runops.io/

encryptluks2 5y ago
But at 18-20 seconds for a VM that is non-starter. Can't you just run it in a container or WASM in the browser? I personally would rather have it external so that it runs in a container in my actual terminal.
- mlejva 5y ago
  That will get better. We are 18-20 seconds without of much optimization as of right now. We have internal demos being able to start under 1 second. > Can't you just run it in a container or WASM in the browser? Great thing about VMs is the security, quick snapshotting, and resource oversubscription. > WASM in the browser I personally love WASM and am very excited about it. There are however a lot of use-cases where WASM doesn't cut it. Having full environments with a file system and being able to start any Linux binary is very useful. Especially when you want to show some real-life examples with your API.
  - Cloudef 5y ago
    >There are however a lot of use-cases where WASM doesn't cut it. >Having full environments with a file system and being able to start any Linux binary is very useful. https://humphd.github.io/browser-shell/ https://humphd.github.io/browser-shell/ That said, not practical if the OS image needs to be huge.
- tolmasky 5y ago
  RunKit provides this functionality and it’s more or less instant (every version of every package on npm is already pre-installed, you won’t feel the boot up time, just the code in question’s actual execution time). Also, it’s free and has been free since it was introduced about 5 years ago. The code lives on your site so the “degraded experience” if we’re ever down is just “falljng back” to the unrunnable code. Try it yourself and see if the speed is acceptable: https://runkit.com/docs/embed https://runkit.com/docs/embed
  - mlejva 5y ago
    Hey Francisco, thank you for building RunKit!:) We have goals on our roadmap which will make the experience much better and near instant. The time and our execution will tell.

by mlejva 5y ago

encryptluks2 5y ago

But at 18-20 seconds for a VM that is non-starter. Can't you just run it in a container or WASM in the browser? I personally would rather have it external so that it runs in a container in my actual terminal.

mlejva 5y ago
That will get better. We are 18-20 seconds without of much optimization as of right now. We have internal demos being able to start under 1 second. > Can't you just run it in a container or WASM in the browser? Great thing about VMs is the security, quick snapshotting, and resource oversubscription. > WASM in the browser I personally love WASM and am very excited about it. There are however a lot of use-cases where WASM doesn't cut it. Having full environments with a file system and being able to start any Linux binary is very useful. Especially when you want to show some real-life examples with your API.
- Cloudef 5y ago
  >There are however a lot of use-cases where WASM doesn't cut it. >Having full environments with a file system and being able to start any Linux binary is very useful. https://humphd.github.io/browser-shell/ https://humphd.github.io/browser-shell/ That said, not practical if the OS image needs to be huge.
tolmasky 5y ago
RunKit provides this functionality and it’s more or less instant (every version of every package on npm is already pre-installed, you won’t feel the boot up time, just the code in question’s actual execution time). Also, it’s free and has been free since it was introduced about 5 years ago. The code lives on your site so the “degraded experience” if we’re ever down is just “falljng back” to the unrunnable code. Try it yourself and see if the speed is acceptable: https://runkit.com/docs/embed https://runkit.com/docs/embed
- mlejva 5y ago
  Hey Francisco, thank you for building RunKit!:) We have goals on our roadmap which will make the experience much better and near instant. The time and our execution will tell.