☆ Yσɠƚԋσʂ ☆@lemmy.ml to Programmer Humor@lemmy.mlEnglish · 2 months agoWhy indeedlemmy.mlimagemessage-square65fedilinkarrow-up1229cross-posted to: [email protected]
arrow-up1229imageWhy indeedlemmy.ml☆ Yσɠƚԋσʂ ☆@lemmy.ml to Programmer Humor@lemmy.mlEnglish · 2 months agomessage-square65fedilinkcross-posted to: [email protected]
minus-squareVenator@lemmy.nzlinkfedilinkarrow-up1·2 months agoNah its mostly nuget packages. And everything has more dependencies now, including all the dependencies 😅
minus-squarepastermil@sh.itjust.workslinkfedilinkarrow-up3·2 months agonuget packages? is that what we can node_modules these days?
minus-squareYellowTraveller@lemm.eelinkfedilinkarrow-up1·2 months agoNuget is dotnet’s package manager
minus-squarepastermil@sh.itjust.workslinkfedilinkarrow-up1·2 months agoLmao, I guess I wasn’t too far off.
minus-squareSleepless One@lemmy.mllinkfedilinkEnglisharrow-up1·2 months agoC# is usually used server-side. How would nuget bloat affect client-side applications that users use?
minus-squareVenator@lemmy.nzlinkfedilinkarrow-up2·2 months agoI meant node packages 😅. C# can be used in front end too though, but probably quite rarely used 😅
Nah its mostly nuget packages. And everything has more dependencies now, including all the dependencies 😅
nuget packages? is that what we can node_modules these days?
Nuget is dotnet’s package manager
Lmao, I guess I wasn’t too far off.
C# is usually used server-side. How would nuget bloat affect client-side applications that users use?
I meant node packages 😅. C# can be used in front end too though, but probably quite rarely used 😅