groctel@lemmy.world to Programmer Humor@programming.devEnglish · 2 months agoreason enough to fail the interviewlemmy.worldimagemessage-square155linkfedilinkarrow-up1906arrow-down114
arrow-up1892arrow-down1imagereason enough to fail the interviewlemmy.worldgroctel@lemmy.world to Programmer Humor@programming.devEnglish · 2 months agomessage-square155linkfedilink
minus-squarehperrin@lemmy.calinkfedilinkEnglisharrow-up8arrow-down1·2 months agoThis wholly depends on where this code is running. If it’s running on the server, you want the best algorithm for most cases, to try to minimize work and power consumption, and maximize capacity. If it’s running on the client, just use whatever.
minus-squareClusterfcklinkfedilinkarrow-up24·2 months agoTHIS IS WHY SOFTWARE DOWNLOADS ARE 75 GB WHEN 20 YEARS AGO THEY WERE ONLY 200 MB.
minus-squarexthexder@l.sw0.comlinkfedilinkarrow-up15·2 months ago If it’s running on the client, just use whatever. Because who cares if it’s the user that has to buy more RAM or gets terrible battery life, that’s not our problem. /s This is why we can’t have nice things.
minus-squarehperrin@lemmy.calinkfedilinkEnglisharrow-up8·2 months agoI agree. I guess it wasn’t obvious that I was being sarcastic.
minus-squarebruh@nord.publinkfedilinkEnglisharrow-up1·1 month agoyou should have used ‘/s’. a lot of people got confused it seems
This wholly depends on where this code is running. If it’s running on the server, you want the best algorithm for most cases, to try to minimize work and power consumption, and maximize capacity. If it’s running on the client, just use whatever.
THIS IS WHY SOFTWARE DOWNLOADS ARE 75 GB WHEN 20 YEARS AGO THEY WERE ONLY 200 MB.
Because who cares if it’s the user that has to buy more RAM or gets terrible battery life, that’s not our problem. /s
This is why we can’t have nice things.
I agree. I guess it wasn’t obvious that I was being sarcastic.
you should have used ‘/s’. a lot of people got confused it seems