4 ms·

Emulated desktop Operating system written in a high level language, compiled to an intermediate assembly language, run on a virtual machine written in JavaScrip

by AyyEye 2y ago

Emulated desktop Operating system written in a high level language, compiled to an intermediate assembly language, run on a virtual machine written in JavaScript, executed in a javascript engine, run inside of a sandbox inside of a browser, inside of an operating system just like the proprietary one one being run at the bottom of the stack. All so you can "create text files" on a proprietary platform that won't work without the internet. What a time to be alive!

pipeline_peak 2y ago
I mean when you describe most modern consumer software products, they’re pretty much that bloated.
- owenfar 2y ago
  And most software today requires an internet connection anyways, even if it is installed natively...
- AyyEye 2y ago
  Most consumer (hard/soft/firm/wet)ware is pretty much all around bad with very few redeeming qualities these days. You can almost feel the contempt for the user built right into the design from marketing all the way to implementation.
owenfar 2y ago
Not 100% correct, but ok, you can say that as it stands. If you inspect the IndexedDB when logged in, you can see that everything is stored locally already. Offline mode was planned from the very beginning. It will and can already work offline if I spare a couple of days on it. But I didn't see it as a priority right now.
- permanent 2y ago
  Please do spare a couple of days on it. I think noone would really believe it until seeing it :)
- AyyEye 2y ago
  I'm just being snarky. Props for making something more polished than anything I've ever made.
jejeyyy77 2y ago
as a user, your first paragraph was just jibber jabber.
smt88 2y ago
VS Code's stack is approaching this level of abstraction/translation/insanity, but it's still performant and useful.
fasa99 2y ago
In the big picture we start with the server side - >cloud computer running a >linux machine running a >virtual machine running a >linux machine running a >virtual docker environment running a >instance of python running a >virtual python environment running a >codebase >serving a >operating system compiled to >assembly running on a >virtual machine compiled to >javascript JIT comiled to >assembly running on a >virtual sandbox running on a >virtual machine running on a >linux machine on a >home computer So I think we can all agree it's a mess. Magic numbers, frozen configurations, too many configurations that are different. One very elegant around making sure configurations and libraries are setup correctly - perhaps another layer or ten of virtualization?

by AyyEye 2y ago

pipeline_peak 2y ago

I mean when you describe most modern consumer software products, they’re pretty much that bloated.

owenfar 2y ago
And most software today requires an internet connection anyways, even if it is installed natively...
AyyEye 2y ago
Most consumer (hard/soft/firm/wet)ware is pretty much all around bad with very few redeeming qualities these days. You can almost feel the contempt for the user built right into the design from marketing all the way to implementation.

owenfar 2y ago

Not 100% correct, but ok, you can say that as it stands. If you inspect the IndexedDB when logged in, you can see that everything is stored locally already. Offline mode was planned from the very beginning. It will and can already work offline if I spare a couple of days on it. But I didn't see it as a priority right now.

permanent 2y ago
Please do spare a couple of days on it. I think noone would really believe it until seeing it :)
AyyEye 2y ago
I'm just being snarky. Props for making something more polished than anything I've ever made.

jejeyyy77 2y ago

as a user, your first paragraph was just jibber jabber.

smt88 2y ago

VS Code's stack is approaching this level of abstraction/translation/insanity, but it's still performant and useful.

fasa99 2y ago

In the big picture we start with the server side - >cloud computer running a >linux machine running a >virtual machine running a >linux machine running a >virtual docker environment running a >instance of python running a >virtual python environment running a >codebase >serving a >operating system compiled to >assembly running on a >virtual machine compiled to >javascript JIT comiled to >assembly running on a >virtual sandbox running on a >virtual machine running on a >linux machine on a >home computer So I think we can all agree it's a mess. Magic numbers, frozen configurations, too many configurations that are different. One very elegant around making sure configurations and libraries are setup correctly - perhaps another layer or ten of virtualization?