Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The problem I see with a remote filesystem is that you’ll still need tools for editor integrations - language servers, formatters, linters, etc.

Sure, you can install those locally too, but by then you are losing many of the benefits of a cloud environment.



Go try VSCode remote. These are all solved problems. The extensions run headlessly on the server, and the client does little more than render the interface. Switching between machines is seamless with settings sync, workspace recommended extensions, etc.

You won’t find many people who started using VSC remote dev and then abandoned it to go back to local. Once you’ve got it working, which is a pretty easy feat, it’s a no brainer, obvious win.


This is what I've started doing, and I'm definitely a life-long convert.

I still experience a few glitches (extensions randomly stop working, Intellisense sometimes dies, and auto-detecting architecture for launching mobile apps sometimes fails) but I'm sure those will be ironed out.


Yes, I am aware. I was responding to this bit:

> This seems preferable - the editor runs on your local machine with low latency, but you still run tests on the cloud machine.


Ah I see – apologies, I read your comment too quickly.

Something I miss with remote development is being able to use graphical Git clients like Sublime Merge on my working directory. I don’t want to setup SSHFS just to make that work, and I’m sure performance wouldn’t be great anyway.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: