ikidd@lemmy.world to Linux@lemmy.mlEnglish · 4 days agoThree Years of Nix and NixOS: The Good, the Bad, and the Uglypierrezemb.frexternal-linkmessage-square51fedilinkarrow-up1132arrow-down15 cross-posted to: linux@programming.devlinux@programming.dev
arrow-up1127arrow-down1external-linkThree Years of Nix and NixOS: The Good, the Bad, and the Uglypierrezemb.frikidd@lemmy.world to Linux@lemmy.mlEnglish · 4 days agomessage-square51fedilink cross-posted to: linux@programming.devlinux@programming.dev
minus-squareFlipper@feddit.orglinkfedilinkarrow-up3·4 days agoIt also is an option to ensure everyone has the same dev environment.
minus-squareatzanteol@sh.itjust.workslinkfedilinkEnglisharrow-up12arrow-down3·4 days agoMeh. So is docker.
minus-squareMihies@programming.devlinkfedilinkarrow-up3arrow-down3·4 days agoThe docker is not bare metal though.
minus-squareutopiah@lemmy.mllinkfedilinkarrow-up4·4 days agoDoes it matter if the overhead is practically irrelevant?
minus-squareMihies@programming.devlinkfedilinkarrow-up1·4 days agoIt could if there are issues accessing hardware directly. Overhead is, as you said, not that important.
It also is an option to ensure everyone has the same dev environment.
Meh. So is docker.
The docker is not bare metal though.
sigh, yes it is.
Does it matter if the overhead is practically irrelevant?
It could if there are issues accessing hardware directly. Overhead is, as you said, not that important.
Isn’t it what passthrough is for?