bahmanm@lemmy.ml to Linux@lemmy.mlEnglish · 4 months agoMy fellow software engineer, It's the year 2024...mastodon.socialexternal-linkmessage-square122fedilinkarrow-up1301arrow-down117file-textcross-posted to: [email protected]
arrow-up1284arrow-down1external-linkMy fellow software engineer, It's the year 2024...mastodon.socialbahmanm@lemmy.ml to Linux@lemmy.mlEnglish · 4 months agomessage-square122fedilinkfile-textcross-posted to: [email protected]
minus-squareatzanteol@sh.itjust.workslinkfedilinkEnglisharrow-up13arrow-down1·edit-24 months agoGo pisses me off with that. I separate projects the way I want but go wants every project written in go in one big directory?
minus-squaredinckel@lemmy.worldlinkfedilinkarrow-up2·4 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·4 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·4 months agoObviously it’s not, but you have to download all this shit somewhere before compilation. That’s the whole point
Go pisses me off with that. I separate projects the way I want but go wants every project written in go in one big directory?
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