Live data from Hacker News

os.js: JavaScript Cloud/Web Desktop Platform

os.js.org

91–100 of 100 posts

Re: os.js: JavaScript Cloud/Web Desktop Platform

#93
post #89

Nice to see my project on hackernews :D Thanks for checking it out guys. It-s something I enjoy working on in my spare-time

It's been a while since I've checked up on the project. How's everything going? Have you gotten any adoption? Did the backend stuff ever get completely ported over to node from PHP?

Yes, there is a company that will make use of OS.js in a commercial product. More news about that will surface this year, so stay tuned! :)

And the Node backend is pretty much identical to the PHP one now... and PHP will probably be deprecated in the near future (at least from the main repository)

Re: os.js: JavaScript Cloud/Web Desktop Platform

#94
When I worked in a telecom company, there were a lot of servers where a GUI was exposed which mimicked a Gnome 2 environment (through Citrix if I remember correctly). It was painfully slow and really a time waster. I wonder if this is faster than that. If it is, so many companies can use it.

Re: os.js: JavaScript Cloud/Web Desktop Platform

#95
post #13

Pretty impressive UI/UX. If that's possible using "web technologies" (JS + HTML + CSS, I gather), shouldn't it be possible to create such things on mobile? All the mobile-optimized web stuff I see still feels sub-optimal.

The hard parts of doing this for mobile is implementing things like touch and scrolling. You get these with a webview, but they don't feel like their native equivalents.

Re: os.js: JavaScript Cloud/Web Desktop Platform

#96
post #13

Pretty impressive UI/UX. If that's possible using "web technologies" (JS + HTML + CSS, I gather), shouldn't it be possible to create such things on mobile? All the mobile-optimized web stuff I see still feels sub-optimal.

> All the mobile-optimized web stuff I see still feels sub-optimal. That's probably because all of the mobile browsers are terribly inefficient when compared to desktop browsers. It makes creating a mobile experience that's fluid and fast.

Aren't the JS/HTML/CSS engines pretty much identical?

Re: os.js: JavaScript Cloud/Web Desktop Platform

#98

Too bad browser JS is single-threaded. If you switch windows the background application stops. Kind of limits its ability as a desktop replacement no matter how much effort they put into it.

There's no reason you can't have multiple "apps" running at the same time, you just don't have preemption ( https://en.wikipedia.org/wiki/Preemption_(computing) ) so it's possible for one application to tie up the CPU indefinitely. That's definitely not whats happening in this case, since the UI is still responsive. Alternatively, to get true isolation and preemptive multitasking you could have a sort of "window serv…

You don't need web workers, you just need to host each app in a sandboxed iframe. Then it can render however it wants with normal DOM access and have script and DOM isolation from the OS and other apps. You would need some sort of IPC system on top of postMessage, and probably some way to send theme data down into the frame and get things like content sizes back out.

I don't think same-origin iframed apps would be out-of-process in Chrome yet, but I do think Chrome is supposed to get out-of-process frames eventually. That would prevent an apps from exploiting a browser bug to take down the whole tab.

Re: os.js: JavaScript Cloud/Web Desktop Platform

#99

What about an X11 server?

Just an X11-client would be interesting. It would theoretically allow you to transparently offload UNIX applications to a remote server.

Im no linux person (gawd no) and so dont know EXACTLY what you mean, but is this the sort of thing you meant?.....

https://www.youtube.com/watch?v=Hd73b-Twf4I

Mentioned....

https://www.reddit.com/r/javascript/comments/3yo754/osjs_a_j...

https://www.reddit.com/r/javascript/comments/3yo754/osjs_a_j...

Re: os.js: JavaScript Cloud/Web Desktop Platform

#100

Earlier quoted context omitted.

A few use cases: 1/ Make a modular backoffice for CMS based website. Make an app to manage users, an app to manage content, an app to upload and manage gallery of media etc. 2/ Make a distributed OS. All services can scale and use backend power beyond what a single node can provide. If you need to burst in the cloud due to a heavy process for instance. 3/ Could use it to provide a separation between the OS and the GU…

> 4/ What about reducing the cost of HW it needs to run? Chromebook style. How so? At least for me the window moving is slightly laggy and is probably going to worse on low-end systems.

It's quite snappy on my own Samsung Chromebook. However, I did grasp the irony of running a web OS inside of another web OS.
Post reply on HN