3 ms·
I haven't actually done development within a VM. How practical is it? What's a good way to get started? (In this case, on a Mac.)
by skybrian 5y ago
I haven't actually done development within a VM. How practical is it? What's a good way to get started? (In this case, on a Mac.)
- mikece 5y agoWhen I was still a consultant I spun up new VMs for each client engagement -- both macOS and Windows -- using Parallels. When the engagement was over I would dump that to an external HDD. It meant over-spending on my MacBook Pro to have the SSD and RAM space to support multiple VMs but there was never any question of client work corrupting my system (or vice versa) or needing to wipe and reload my machine after a client engagement.
- nukemaster 5y agoYou just do everything over ssh. It's one of the reasons everyone still like CLI/VT tools so much.
- mhoad 5y agoCodespaces is great in my experience. VSCode devcontainers is another very similar approach that will keep it on your machine but at least containerize the development environment raising the bar fairly significantly for a rogue package to do serious damage on your machine.
- deleted 5y ago[deleted]