☆ Yσɠƚԋσʂ ☆@lemmy.ml to Programmer Humor@lemmy.mlEnglish · 14 days agoWhy indeedlemmy.mlexternal-linkmessage-square63fedilinkarrow-up11arrow-down10cross-posted to: programmer_humor@programming.dev
arrow-up11arrow-down1external-linkWhy indeedlemmy.ml☆ Yσɠƚԋσʂ ☆@lemmy.ml to Programmer Humor@lemmy.mlEnglish · 14 days agomessage-square63fedilinkcross-posted to: programmer_humor@programming.dev
minus-squareVenator@lemmy.nzlinkfedilinkarrow-up0·14 days agoNah its mostly nuget packages. And everything has more dependencies now, including all the dependencies 😅
minus-squarepastermil@sh.itjust.workslinkfedilinkarrow-up0·14 days agonuget packages? is that what we can node_modules these days?
minus-squareYellowTraveller@lemm.eelinkfedilinkarrow-up0·14 days agoNuget is dotnet’s package manager
minus-squareSleepless One@lemmy.mllinkfedilinkEnglisharrow-up0·14 days agoC# is usually used server-side. How would nuget bloat affect client-side applications that users use?
minus-squareVenator@lemmy.nzlinkfedilinkarrow-up0·14 days 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 😅