3 ms·
For the past 5 years I've used a macbook to ssh in to a Linux VM as my development environment. It was great for the work that I was doing (distributed web syst
by jcalabro 4y ago
For the past 5 years I've used a macbook to ssh in to a Linux VM as my development environment. It was great for the work that I was doing (distributed web systems).
Now that I've changed jobs and I'm developing a desktop app again, I'm back on a physical Linux box under my desk, and I really miss the old experience. It was great to never care about a mac change tanking your productivity (i.e. I was totally unperturbed by the m1 switch), and it was also great not to have to run a Linux desktop environment, which it turns out is still a big pain.
- ricardou 4y agoI have had the same experience, although I've only been out of school for two years. So far my daily work stream has me doing ssh to a Linux box and then doing my work there. All the CI/CD, version control, building code, and storing the code is done remotely. So far it's been great (again, I've never had an alternative) and the power of virtualization has really come in handy. A couple of times in the past I accidentally borked my Linux box and started to figure out how to fix it, but then I had my d'oh moment: just scrap this one and get another! There's no "it works on my machine" and most importantly, I can work from anywhere, with a stable internet connection (even using a phone to do USB tethering worked fine), from a Mac, a Chromebook, windows, whatever computer. One caveat is that I program backends in C++ so a lot of the issues mentioned in the article don't really apply to me. Regardless, it's been great!