4 ms·
Of course it isn't, but limiting installation instructions to the creation of a single well-defined Docker container makes a whole lot of sense in terms of avoi
by willbudd 3y ago
Of course it isn't, but limiting installation instructions to the creation of a single well-defined Docker container makes a whole lot of sense in terms of avoiding reproducibility headaches.
And by extension, with regard to make development inside a container a pleasant experience, VS Code is currently the only game in town. And I say that as someone who spent two decades getting comfortable with vim.
- Kiro 3y agoWhat's the benefit of developing inside the container instead of just linking the filesystem?
- neatze 3y agoI don't want to install anything on my system, want to keep clean and as minimal as possible, containers full fill my OCD in this regard, I run most app's now in containers too, it is best linux setup I ever had in my life :)
- willbudd 3y agoI have no idea what you mean by "just linking the filesystem".
- makeitdouble 3y agoNot having to screw with your system's dependecies and spend time making sure everything is aligned with the expected environment. Ansible like tools could help you make the setup repeatable, but being containerized also avoids all the processor architecture and system libraries gotchas.
- kortex 3y agoROS is verrrrrrry opinionated and a pain to set up in an orthogonal way to other ROS installs. It's also tied very heavily to ubuntu/debian. Putting it all into containers makes many things so much easier (it makes a few things harder, or at least it did on ros1, hopefully that's been ironed out in ros2)