3 ms·
> But developers can ssh to the cloud, and develop there, right? Then why do they insist on 32GB i9 laptops running MacOS or Linux? One must assume that there
by AnIdiotOnTheNet 8y ago
> But developers can ssh to the cloud, and develop there, right?
Then why do they insist on 32GB i9 laptops running MacOS or Linux? One must assume that there is some practical purpose, unless one is rather cynical and believes that maybe the just like shinnies.
- scarface74 8y agoThere is nothing stopping you from developing on x86 and SSHing to a remote ARM computer for final validation. Cross compilation has been a thing for decades.
- blattimwind 8y agoLinus' point is literally that the pains associated with cross developing/compilation are what brought x86 to power and keeps it there.
- scarface74 8y agoOn the level of Linux it might be hard, but thousands of iOS developers do it all of the time. On the application level if you are just doing C, my experience with writing cross platform C, if it works on one platform and breaks on the other, there is probably a bug in your software that is only surfacing on one platform usually around depending on undefined behavior or relying implementation defined behavior. But my “experience” with native cross platform programming is two decades old - x86 and whatever the old DEC VAX and Stratus VOS platforms were running.
- Tor3 8y ago.. develop remotely? I can, if I wish. I have an extremely high bandwidth link to servers. But there's still latency, and that makes all the difference. So in practice I always develop locally. I use Git and VNC and sshfs-mounted filesystems to access the remote, but my tools and editors are always local. I can build remotely, but not work remotely. And I still like to build locally all the same, during the actual development.
- AnIdiotOnTheNet 8y agoI find it hilarious that this is the developer attitude for their own work, but then they turn around and expect users to just suck it up and accept latency because cloud!
- Tor3 8y agoIt's a difference in using a text editor remotely, compared to doing just about anything else remotely. I can log in and build remotely, and execute remotely, use remote git servers, even run GUIs remotely (testing my application through a VNC). But using a text editor remotely, with a few hundred millisecs rtt.. now, that is very different.