Preferences

> Google has an internal-only virtual desktop tool for thin clients called "CloudTop" that it would like employees to transition to

This is the end.

All thin client/remote desktop solutions that I have used are laggy enough to piss off a programmer, while fast enough to fool a manager.

It's the perfect killing blow to productivity and morale.


Cloud tops are quite good. I’ve enjoyed using them.

Run a mbp as your carry around, and then everything else runs on an overbuilt server vm with a direct connection to shared storage.

I’m able to sync to head + rebuild 100k+ files in < 5 mins

What's the audio latency? I've found remote desktop to be a bad experience as a blind developer. At a prior job we used thin clients which had decent audio performance from my desk in the office. Once Covid hit and we had to connect from home audio latency was awful and it took me an act of god to get a corporate provided laptop.
They are more like a super well connected SSH client. I think you could probably get X11 / audio up on it but I’ve never had the need to.

Development on an internal fork of VS code (web page) which sets up all the build tooling for you to use your cloud top as your build eng. Includes ML based completion as well which is nice.

So if you have used VS code I’d imagine the accessibility is similar as audio is rendered locally?

I highly doubt I'll ever get a job at Google but that's good to know. I use VS code as my main IDE and Microsoft has done a lot of work to make it accessible.
You probably didn't work for a company that has a global network that is capable of running Youtube levels of traffic around the planet with the latency requirements of Google Ads.

I used to consult, and got at one point hired to explain to higher management, at a small but important "regulatory" government department, why 256kbps ADSL sucked for rdesktop (which was on a private ATM channel from the incumbent telco, very expensive, and also very bad, it was still ADSL over an ATM backbone, in 2005, supposedly it was more secure ...). Note 256kbps = 32 KB/sec. I'm not sure how much they paid, but the page describing the product at the telco said to call to make an appointment for sales to visit you to get some pricing info. Oh, and the backend connection for this had to be done in duplicate, with endpoints in 2 different countries. I'm pretty sure just the backend connections cost a decent house a month at minimum.

Needless to say, over 32 KB/sec, rdesktop is pretty much unusable. Not that said incumbent telco actually delivered 32 KB/sec, merely because they paid through the nose.

So I wrote a 40 page document, written in 12 days, for a just-barely-not-6-figure-bill. They had an excellent restaurant. Steak for 4 euro, and every week a different theme. Even the spaghetti bolognaise was excellent. Didn't do anything for the rest of 2 months, going in several times with my access badge just for the restaurant (to "discuss followup"). This went very slowly because of the top 3 levels of management, who had to approve everything, 2 were government appointed positions. These people never even came in because their performance and future at the company was only tied to their party's performance in elections, which had absolutely nothing to do with what this department was regulating.

Google can probably provide incredible remote desktops. Small companies can't, due to cost (not of the connection, hardware cost. Remote desktops, to be good, need to be machines running large VMs. That means modern i9s with 64G of ram MINIMUM). I'm not sure what Google uses, but ... Large companies and government can't, due to "best practices" preventing timely upgrades. This happens because they require everything be explained, risk-assessed, verified by external consultants, signed in triplicate, sent in, sent back, queried, lost, found, subjected to public inquiry, lost again, and finally buried in soft peat for three months and recycled as firelighters.

How good is it when working from outside the office, on a rate from "painful" to "unusable"?
I’ve literally never had issues. So like 9/10. Works perfectly when on coffee shop wifi. Google tooling works perfectly with it.
Latency nowadays isn’t bad or even noticeable.

I worked for a company during Covid where I had to remotely connect to a Windows machine, and from there, connect to a Linux machine.

The only issue I had was keyboard mapping, specially because I was using a macbook. I had to remap a few keys, but even then, a few hotkeys didn’t work.

It’s not perfect, but it’s getting better and I can see many companies will force us all to this in 10 years time.

About 3 months ago I went full thin-client using similar internal tools. 90+% of my workflow is using terminals and editors that work brilliantly over an SSH tunnel. For the stuff that can't be done on a remote computer (flashing boards, physical hardware), I have a couple scripts that allow me to do that locally. The whole thing has turned out to be less work than the physical tower under my desk.
But we're not talking about the same thing here. I do also work 99% in the terminal, and SSH is perfectly okay.

But my window manager is running locally.

In a thin client/remote desktop setup the WM is running remotely. From my experience, this makes the mouse and keyboard ever so slightly laggy that's it's very annoying.

I'm under the impression that the vast majority of people use their cloudtop over ssh and a remote vscode connection. I only ever use a remote gui for a few minutes every X weeks to do chrome-based auth for an nonstandard workflow.
Common problems in my experience: * Build performance is crap every morning as the file cache is purged from RAM overnight and needs to refetched from remote disks * Build performance is largely determined by how much cpu and RAM others VMs on the server are using concurrently. Sometimes it's really good when it's underutilized, but sometimes it can be pretty bad as you are no longer using more resources than you were allocated * Trying to interact with it via a GUI (chrome remote desktop for instance) is quite laggy. This doesn't bother me as I am already on the ssh + tmux gravy train.

I really appreciate the consistency of dedicated hardware and really don't want to give it up.

This item has no comments currently.

Keyboard Shortcuts

Story Lists

j
Next story
k
Previous story
Shift+j
Last story
Shift+k
First story
o Enter
Go to story URL
c
Go to comments
u
Go to author

Navigation

Shift+t
Go to top stories
Shift+n
Go to new stories
Shift+b
Go to best stories
Shift+a
Go to Ask HN
Shift+s
Go to Show HN

Miscellaneous

?
Show this modal