3 ms·
I don't see a point to this. Even the post itself it looks half-complete and somewhat broken and of low quality. In fact it appears that this post was subject
by rvz 2mo ago
I don't see a point to this. Even the post itself it looks half-complete and somewhat broken and of low quality.
In fact it appears that this post was subject to an upvote ring to quickly reach the front page with little of value in itself.
So I am very suspect of this post.
- raboukhalil 2mo agoWow tough crowd, can you expand on why it looks broken and low quality?
- dummydummy1234 2mo agoFrom my perspective it does not tell me how it works, or the give examples of why you would use it? Is it a actual Linux kernel + filesystem under the hood? Or did you just use the standard utilities compiled for wasm, how does network access work (assume it doesn't because of coors) Can you run non-wasm programs? How do entry points work - what about ctrl-c and interrupts for long running programs. You do not discuss any of this and it seems half baked. (This coming from someone who has explored how to do this for a vscode in browser editor playground)
- tosti 2mo agoI'm gonna let you in on a little secret and it's called F12.
- ranger_danger 2mo agoPlease don't get discouraged, people who are rude are just projecting their own troubles onto others. The documentation/tutorial concept is a great idea in my opinion. Whenever I see a new command-line tool advertised, I always wish I could try it right away without having to download/compile it, which isn't always easy.