[ryall]

I do this except the Linux is on a separate box and the dev envs are docker containers.

Decided to spend my money on decent, upgradeable hardware instead of shelling out 5k for another MB Pro. My next MacBook will probably be the most low-end I can get.

VSCode's remote/docker support is a godsend. Seems like we're heading back to the dumb terminal paradigm.

[kristiandupont]

I did this too and that is very pleasant as well. But the new Air performs well and has no fan and the feeling is, quite frankly, the same.

[ryall]

And the way you're doing it sounds like you avoid the docker mount slowdown issue. Sounds like quite a good solution

[cassianoleal]

Do you have your projects cloned in the remote host?

I ask because I was excited about this prospect only to learn that I could only use Remote: Containers if codebase and container are on the same machine as the project workspace is just volume-mounted in the container.

[connor4312]

There are more options here. For example, you can attach to fully remote containers: https://code.visualstudio.com/docs/remote/containers-advance... or just attach to existing local containers that you can set up however you'd like.

[cassianoleal]

Yeah I have been using local containers and I really like the workflow.

I wasn't aware of that setup you linked. I'll give that a go, thanks!

[ryall]

Yeah I dusted off an old licence I had for resilio sync and use that to sync with my local machine.

You can get around this by running git clone inside your container as part of the startup process. But 1. It can add quite a delay to starting a container depending on the size of your codebase, and 2. Not all of my code is necessarily committed and pushed.

For me, syncing works well but I can see how it would not suit every use case

[cassianoleal]

Fair enough. I don't want to clone from within the container because I like the idea of being able to nuke it at any time and just start over from local code.

Probably similar reasons to what you mean by not having all code committed and pushed.

[haffi112]

Do you recommend any tutorials online to get such a setup?

[ryall]

I've been considering writing one myself, admittedly it's not an easy road at first, and a step by step guide would've helped a lot.

[tnorthcutt]

Wondering the same thing. I'd like to explore a setup like this but trying to cobble it together myself without a good guide is daunting.

[txdv]

Except that the terminal is thousands and thousands times more powerful than the machine you connected to with the terminal back in the days.

[KMnO4]

I train ML models on my Macbook (Intel GPU) by SSHing into a machine with a Tesla A100.

In this case it really is more than thousands of times more powerful.

[danlugo92]

Can't get that with AWS though? Some kind of spinup-able VPS?

Like a normal VPS but you can get dat 64 cores + 64gb ram only the day you need them and otherwise pay a low monthly fee.

[0x426577617265]

I have a Dell R720 that I bought fairly cheaply ~$600 came with 192GB of RAM. I shoved some SSDs in it with a GPU. Sits in my garage. If I'm not home I can still remote into my terminal via wireguard. Good deals can be found using lab gopher:

https://labgopher.com/servers/Dell_R720/

Granted it's not 64cores, but still fast.

[danlugo92]

I saw some VPS providers offer hourly billing, which can get me a 64cores + 64gb ram at like $30 a month. I'm going to go with that. I actually don't have landline/fiber internet at home so your solution wouldn't work for me, but I'll keep it in mind I didn't know about such deals!

[dmos62]

> the dumb terminal paradigm

Hehem. The paradigm you're referencing is letting you do what you want to do (because it's a powerful paradigm). We need more of that if anything.