4 ms·

> I mean, if all that mattered were specs, we would all be running desktops at full desktop-class TDP. As someone doing just that (I do 99% of my work on my de

> I mean, if all that mattered were specs, we would all be running desktops at full desktop-class TDP. As someone doing just that (I do 99% of my work on my desktop machine), to this day I don't understand folks doing heavy development work on a laptop. If you need portability, remote into a desktop class machine. Sure there are times when you just can't (airplane, or camping in the middle of nowhere, etc) but those times are exceedingly rare.

brundolf 5y ago
A lot of people don't work completely from a terminal, and remote-desktop can be a pretty mixed experience. Also, this way companies don't have to issue each person two different devices (and have IT manage twice as many devices, with two different form-factors).
freeopinion 5y ago
"Remote into a desktop"? That sounds like a horrible experience to me. I've never understood why anybody would remote control a pc for anything. If you need to code on the road, just code directly on whatever device you were going to use to remote control from. How does remote controlling some other computer make this computer's experience better? You still are stuck with this keyboard, this trackpad, this display, etc.
- GiorgioG 5y ago
  Based on your comments, you've never had the opportunity/need to do so. I have and I can attest that I would much rather remote into a powerful desktop PC to write code than use a mobile processor. Maybe the software you build and its dev tooling allows you t to be effective with a mobile processor, but for my needs it's not good enough.
yellowapple 5y ago
Those times are less rare than you'd think. I've been in plenty of situations where I've needed to develop something in an environment with sketchy/nonexistent network access. Not to mention that even in ideal conditions you're now maintaining two separate machines instead of one, and not to mention that if you're doing all your development over VNC or RDP or something you're now introducing some rather annoying latency between your fingers and your eyes. Having done development work by remoting into another machine (specifically, RDPing into a "dev" server to use vendor-specific IDEs/tooling), I can't say it was an even remotely pleasant experience. I would've sooner preferred doing that work directly on my own machine, or at the very least in a VM if a specific OS and configuration is necessary.

brundolf 5y ago

A lot of people don't work completely from a terminal, and remote-desktop can be a pretty mixed experience. Also, this way companies don't have to issue each person two different devices (and have IT manage twice as many devices, with two different form-factors).

freeopinion 5y ago

"Remote into a desktop"? That sounds like a horrible experience to me. I've never understood why anybody would remote control a pc for anything. If you need to code on the road, just code directly on whatever device you were going to use to remote control from. How does remote controlling some other computer make this computer's experience better? You still are stuck with this keyboard, this trackpad, this display, etc.

GiorgioG 5y ago
Based on your comments, you've never had the opportunity/need to do so. I have and I can attest that I would much rather remote into a powerful desktop PC to write code than use a mobile processor. Maybe the software you build and its dev tooling allows you t to be effective with a mobile processor, but for my needs it's not good enough.

yellowapple 5y ago

Those times are less rare than you'd think. I've been in plenty of situations where I've needed to develop something in an environment with sketchy/nonexistent network access. Not to mention that even in ideal conditions you're now maintaining two separate machines instead of one, and not to mention that if you're doing all your development over VNC or RDP or something you're now introducing some rather annoying latency between your fingers and your eyes. Having done development work by remoting into another machine (specifically, RDPing into a "dev" server to use vendor-specific IDEs/tooling), I can't say it was an even remotely pleasant experience. I would've sooner preferred doing that work directly on my own machine, or at the very least in a VM if a specific OS and configuration is necessary.