I.e. things like installing and updating clang, cmake, etc
You can BYO ChromeOS devices too which make great thin terminals to a remote workstation or cloud VM. I have a whole bunch from dogfooding preproduction Chromebooks.
We had a Sparcstation somewhere in the office being used as a mail server and nothing else. I don't recall how but I managed to SMB or NFS mount a directory so that I could edit code on my piddly little desktop but compile it on the Sparc. First time Java really worked as advertised for me.
Saved me loads of time and let me iterate on ideas that I don't think I or my boss would have had the patience for otherwise.
I'm not entirely keen on language servers, but those would be another area where distributed computing could come in handy. I think what might be missing though is a multitenant version. Everyone on my team has a duplicate model of our dependencies loaded into Webstorm and it's a pig.
Aside, but I 100% believe most developers of user-facing programs should be forced to use their app on a slow computer/phone with a slow internet connection before being able to ship it.
I decided at the very start of my career, before Google, to use a laptop at the primary interface and only use workstation / dev environment / etc. remotely. That way I have the same working experience at my desk, at a cafe, on my desk at home. The only thing that changes is the number and size of monitors. It's worked out really well, and during the COVID era it only got better due to investments in the remote workflows.
I wouldn't even notice if my VM lost internet access and root.
It has been “the year” for Linux on the desktop for the last 10 years, even more so if you use Emacs as your WM.
SSH disconnects are still annoying. And mosh/tmux/screen don't do it for me.
> It seems so weird to me to want to use Linux on the desktop. This is not The Year.
It seems so weird to me everybody considering their Windows or Mac as desktop ;)
Why? I've used it for many years and still like it very much. I use Windows too, but I do most of my work in Linux. Why would this be weird?
I can only infer that you're suggesting people would only want to use Macbooks? Setting aside the fact that that is wrong, you don't make any argument as to why that would be.
gLinux laptops are OK I guess? I dunno. Every time I've tried to use Linux as my main interface, it's been crashy and confusing. Maybe it's gotten better since the last time I tried.
All my dev work, personal, and internet while I work. KVM to swap. External screens.
Strict separation of work and life. No key logging like the work system. No fillers.
>The report says Google's new pilot program "will disable Internet access on the select desktops, with the exception of internal web-based tools and Google-owned websites like Google Drive and Gmail.
https://arstechnica.com/gadgets/2023/07/to-defeat-hackers-go...
Because some people like to use remote desktop with it. And because some people's "build machine" is a VM, or a physical desktop in the office for some others.
Sounds more like Google isn't talking about workstations but the peoples normal computer they work one, just with limited internet access.
I used a cloud VM as my main machine, and still used internet all the time. I used github to sync my configuration (using a proxy would be out of date and no way to push), amongst other things.
I switched to a Chromebook in the pandemic and honestly it was fine. My workflow barely changed. I wasn't a vim fanatic at the time so I didn't really care.
You see an error message on your desktop, you want to search for it. What do you do?
possibly, not everybody is ok with using a not so good editor, no debugger integration and keeping their ssh and pgp keys somewhere else than a local machine.
This is Google. Who is using ssh keys for anything?
There's not even a current plan to continue limiting access after the trial period ends, much less a plan for expanding it to more machines.
Even just having hosts that are sometimes internet connected and sometimes on the airgap network will greatly weaken the isolation. Stuxnet could cross an airgap with just static media, allowing thousands of computers that sometimes connect to the internet across the airgap seems like a fatal weakness.
For those that don't know: air gapped means completely disconnected, as in literally pull the network cable out the back and never back in again. File transfers have to happen using some physical medium (traditionally write-once CDs/DVDs). You can have an air gapped network so long as the machines are just connected to each other and there's no physical route whatsoever to the internet.
My workstation is just an SSH server that I do builds on, everything else is on my laptop. I can’t remember the last time I used the internet on my workstation. I install packages but those come via a mirror, I scp files back and forth but that’s internal only.
Lots of people aren’t on this workflow yet, but I don’t think anyone is suggesting airgapping the main interface people are using.