That snapshots feature looks useful. Right now it's only used for recovery, but if there was a way to write metadata to them (thumbnail for example) an end-user could browse through them.
That will be possible in the future. The shell is also open source (https://github.com/HeyPuter/phoenix) so we'd also gladly accept any contributions that add the capability to execute wasm files from the filesystem.
> isn't a decentralized system That's right, logically centralized and physically distributed (on our cloud infrastructure). The open-source kernel will likely include a filesystem driver for local disk instead of cloud…
As an avid user of i3wm, the "YAWML" that you described isn't my favorite. The good news is we're working on architectural changes that will make it easier to develop alternative desktop environments that use the same…
A proper mobile UI is something we're looking towards adding. It's been coming up in conversation more frequently lately and we'll probably announce on Discord when we start developing that.
Hi, I maintain that backend (which we call a "kernel"). For now, yes this is correct. Our goal is to open-source a kernel as well. We have a couple hurdles: we need to ensure the code architecture makes productive…
Isn't one of the merits of ESM that it can import either? I believe this is supposed to work: import theDefaultExport from '@heyputer/kv.js';
That snapshots feature looks useful. Right now it's only used for recovery, but if there was a way to write metadata to them (thumbnail for example) an end-user could browse through them.
That will be possible in the future. The shell is also open source (https://github.com/HeyPuter/phoenix) so we'd also gladly accept any contributions that add the capability to execute wasm files from the filesystem.
> isn't a decentralized system That's right, logically centralized and physically distributed (on our cloud infrastructure). The open-source kernel will likely include a filesystem driver for local disk instead of cloud…
As an avid user of i3wm, the "YAWML" that you described isn't my favorite. The good news is we're working on architectural changes that will make it easier to develop alternative desktop environments that use the same…
A proper mobile UI is something we're looking towards adding. It's been coming up in conversation more frequently lately and we'll probably announce on Discord when we start developing that.
Hi, I maintain that backend (which we call a "kernel"). For now, yes this is correct. Our goal is to open-source a kernel as well. We have a couple hurdles: we need to ensure the code architecture makes productive…
Isn't one of the merits of ESM that it can import either? I believe this is supposed to work: import theDefaultExport from '@heyputer/kv.js';