If most devs are web devs then I can believe it. Ain’t no way I’m building a video editor on the cloud though.

@dreamsofcode_io Who said anything about the cloud?

I assume to move it away from one’s laptop would be to move it towards a remote machine that is always available. Unless that’s a dedicated workstation (which would require someone to have the workstation, and still encounters similar problems), then the logical conclusion is the cloud. Of course, it’s an assumption, but then the original tweet was vague enough to lend itself to being assumed.

Yeah, I can see the point. However, moving to a home lab over a laptop feels like the most sensible solution, where you have total access to that machine and still are not frying your laptop with compute, then your laptop becomes just a headless way to test the results and send new instructions to base. But, pretty sure Theo is referring to home labs rather than cloud

That’s something I’ve been playing with a lot in my own work although it’s still got some problems for my own domain. I think anything web based it’s a good approach, especially being able to easily review the output over tailscale/wireguard. Native/desktop (especially needing hardware decoders) is a little harder. I do use a JetKVM for remote access, but it’s still not the best experience.

I’ve been doing remote mobile native work over this, essentially commanding from the same device I’m testing, tailscaled everything and then installing the bundle on the device, and iterating over and over that way. Would expect desktop to be pretty similar, although with worse tooling around it probably, but you can just send the bundle over the wire and test that way