31–40 of 58 posts
Sad to see Linux turning into a web app. I thought they'd be smart enough to avoid this sort of trend. Hope they continue to support the desktop version.
Is there a server if you want to run your own WebSockets as a transport layer?
For more info, see the last few paragraph of the Networking section from our latest blog post: https://labs.leaningtech.com/blog/webvm-20#private-networkin...
Sad to see Linux turning into a web app. I thought they'd be smart enough to avoid this sort of trend. Hope they continue to support the desktop version.
Unless Linus himself is behind this project, I don't think you have anything to worry about.
Hello again HN. Lead dev of WebVM and CTO of Leaning Technologies here. Happy to answer any question from the community.
You mention having a "virtual block-based file system". How easily can people integrate other devices into the VM, including custom devices? For instance, if someone had a different network filesystem they wanted to use, which could be tunneled over WebSocket or WebTransport, how easily could they integrate that into this? What's the equivalent of virtio here?
It looks like the client-side bits are largely proprietary? Is CheerpX the primary thing you consider to be your competitive advantage, or is it more about all the layers you're putting on top of that for things like Flash and Java and Oracle Forms and converting local apps to web apps?
It'd be nice to be able to build atop the underlying VM and extend it for all sorts of purposes, the way KVM has been open enough to become a focal point for the modern cloud, and have just the enterprise-y bits and "convert your local app to a web app" framework running on top of that being proprietary.
Hello again HN. Lead dev of WebVM and CTO of Leaning Technologies here. Happy to answer any question from the community.
This is really impressive! You mention having a "virtual block-based file system". How easily can people integrate other devices into the VM, including custom devices? For instance, if someone had a different network filesystem they wanted to use, which could be tunneled over WebSocket or WebTransport, how easily could they integrate that into this? What's the equivalent of virtio here? It looks like the client-side…
CheerpX is indeed proprietary, but free-to-use for individuals and open source projects. We do want to see the community building on top of our tech. Our Flash product is build on top of CheerpX and the official Flash player plugin that needs to be licensed separately from Harman/Adobe. Java support is provided by a completely different product called CheerpJ, although lots of the ideas and parts of the JIT engines are shared with CheerpX.
At this stage we believe that keeping CheerpX proprietary serves our growth plans the best, this could of course change over time as adoption increases and we build further added-value products on top. On the other hand the WebVM integration is FOSS since it doubles as an extensive sample of what can you build with our technology.
Earlier quoted context omitted.
This is really impressive! You mention having a "virtual block-based file system". How easily can people integrate other devices into the VM, including custom devices? For instance, if someone had a different network filesystem they wanted to use, which could be tunneled over WebSocket or WebTransport, how easily could they integrate that into this? What's the equivalent of virtio here? It looks like the client-side…
We don't currently expose an API to integrate custom block devices, although it could be possible. We provide an integrated backend based on HTTP byte ranges that can work on any standard compliant HTTP server. See here for more info: https://cheerpx.io/docs/guides/File-System-support#block-dev... CheerpX is indeed proprietary, but free-to-use for individuals and open source projects. We do want to see the community…
I was thinking more about arbitrary custom devices, like custom network drivers (e.g. to connect to a server-side virtual network rather than tailscale) or custom filesystem drivers at either the block or FS layer.
> At this stage we believe that keeping CheerpX proprietary serves our growth plans the best, this could of course change over time as adoption increases and we build further added-value products on top.
I'd be very interested in chatting with you about our respective products' future plans.