☆ Yσɠƚԋσʂ ☆@lemmy.ml to Programmer Humor@lemmy.mlEnglish · 22 hours agoWhy indeedlemmy.mlimagemessage-square51fedilinkarrow-up1175arrow-down15cross-posted to: programmer_humor@programming.dev
arrow-up1170arrow-down1imageWhy indeedlemmy.ml☆ Yσɠƚԋσʂ ☆@lemmy.ml to Programmer Humor@lemmy.mlEnglish · 22 hours agomessage-square51fedilinkcross-posted to: programmer_humor@programming.dev
minus-squareVenator@lemmy.nzlinkfedilinkarrow-up1·21 hours agoNah its mostly nuget packages. And everything has more dependencies now, including all the dependencies 😅
minus-squarepastermil@sh.itjust.workslinkfedilinkarrow-up3·20 hours agonuget packages? is that what we can node_modules these days?
minus-squareYellowTraveller@lemm.eelinkfedilinkarrow-up1·19 hours agoNuget is dotnet’s package manager
minus-squareSleepless One@lemmy.mllinkfedilinkEnglisharrow-up1·17 hours agoC# is usually used server-side. How would nuget bloat affect client-side applications that users use?
minus-squareVenator@lemmy.nzlinkfedilinkarrow-up2·10 hours 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
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 😅