Cloud desktops aren't as good as you'd think

Re:Cloud desktops aren't as good as you'd think by yjftsjthsd-h on Thursday October 06, 2022 @12:13PM (#33110131)

> Each virtual desktop is split in half between the IDE (vim in my case) and a terminal session for the code under development in that IDE. That's it. No silly weather or chat widgets (all that lives in my local laptop's traditional desktop).

I don't disagree, but if your editor is vim and you run/test in a terminal, why not do the whole thing in tmux in SSH?

[ Parent | on HN ]

Re:Cloud desktops aren't as good as you'd think by danans on Thursday October 06, 2022 @01:09PM (#33110978)

> you run/test in a terminal

Some of the software has a GUI, and some of the tools (i.e. unit test runners) display their output in a locally (to the remote desktop) running web app viewed via a browser.

If I were doing strictly text-based work, I might use tmux, but to be honest i3 scales down so well to the text-only use case that I probably wouldn't bother, since there is no upside to doing so.

[ Parent | on HN ]

Re:Cloud desktops aren't as good as you'd think by aleksiy123 on Thursday October 06, 2022 @03:55PM (#33113214)

For tools with webapp output. You can use a proxy to access it in your local browser.

Something like ngrok would work well.

The advantage of having tools with APIs

[ Parent | on HN ]

Re:Cloud desktops aren't as good as you'd think by danans on Thursday October 06, 2022 @05:52PM (#33114574)

Sure, but it's a lot easier just to open a browser in the remote desktop session. It's not like the FPS of the browser matters much when looking at unit test results.

[ Parent | on HN ]