8 ms·
VM will always be shit at compilation tasks. All of the existing solutions out there (including Docker) will lead to slower builds, especially if you need to bu
by 0x8BADF00D 8y ago
VM will always be shit at compilation tasks. All of the existing solutions out there (including Docker) will lead to slower builds, especially if you need to build an embedded Linux distribution. Native is better, for those tasks.
The haters he’s replying to are literally splitting hairs.
Wow, they shave off 3 mins to run an interpreted language test suite. This is the ABSOLUTE state of the industry right now.
- jimktrains2 8y ago> VM will always be shit at compilation tasks. All of the existing solutions out there (including Docker) Docker isn't a VM; it runs with the same kernel and directly on the host processor like any application.
- 013a 8y agoExcept the filesystem. Which is what everyone seems to forget. And that's the big thing we're talking about here in reference to Ruby and tests being slow.
- edude03 8y agoThe file system is native too depending on what filesystem your host is running. If the host is running a Copy on Write filesystems like ZFS or BTRFS docker can use it natively.
- pmontra 8y agoEven if you mount the development directory on the host file system? This is probably necessary to be able to edit files. In the case of Ruby maybe you should mount also the language manager directory with all the gems and the interpreter.
- throwaway2048 8y agoUnless your host system isn't linux (like in this case)