☆ Yσɠƚԋσʂ ☆@lemmy.ml to Programmer Humor@lemmy.mlEnglish · 1 年前Why indeedlemmy.mlimagemessage-square62linkfedilinkarrow-up1230arrow-down17cross-posted to: programmer_humor@programming.dev
arrow-up1223arrow-down1imageWhy indeedlemmy.ml☆ Yσɠƚԋσʂ ☆@lemmy.ml to Programmer Humor@lemmy.mlEnglish · 1 年前message-square62linkfedilinkcross-posted to: programmer_humor@programming.dev
minus-squareVenator@lemmy.nzlinkfedilinkarrow-up1·1 年前Nah its mostly nuget packages. And everything has more dependencies now, including all the dependencies 😅
minus-squarepastermil@sh.itjust.workslinkfedilinkarrow-up3·1 年前nuget packages? is that what we can node_modules these days?
minus-squareSleepless One@lemmy.mllinkfedilinkEnglisharrow-up1·1 年前C# is usually used server-side. How would nuget bloat affect client-side applications that users use?
minus-squareVenator@lemmy.nzlinkfedilinkarrow-up2·1 年前I 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 😅