bahmanm@lemmy.ml to Linux@lemmy.mlEnglish · 3 months agoMy fellow software engineer, It's the year 2024...mastodon.socialexternal-linkmessage-square122fedilinkarrow-up1290arrow-down117file-text
arrow-up1273arrow-down1external-linkMy fellow software engineer, It's the year 2024...mastodon.socialbahmanm@lemmy.ml to Linux@lemmy.mlEnglish · 3 months agomessage-square122fedilinkfile-text
minus-squaredinckel@lemmy.worldlinkfedilinkarrow-up2·3 months agoI really didn’t like this either. It’s quite surprising, because the rest of Go tooling is quite nice. Not having a venv, or at least something like pnpm-style node_modules is weird
minus-squarejollyrogue@lemmy.mllinkfedilinkarrow-up1·3 months agoWhy would go have a virtual environment or dep tree like node_modules equivalent, it’s not interpreted or dynamically linked. With modules, dependencies can be vendored.
minus-squaredinckel@lemmy.worldlinkfedilinkarrow-up1·3 months agoObviously it’s not, but you have to download all this shit somewhere before compilation. That’s the whole point
I really didn’t like this either. It’s quite surprising, because the rest of Go tooling is quite nice. Not having a venv, or at least something like pnpm-style node_modules is weird
Why would go have a virtual environment or dep tree like node_modules equivalent, it’s not interpreted or dynamically linked.
With modules, dependencies can be vendored.
Obviously it’s not, but you have to download all this shit somewhere before compilation. That’s the whole point