We’re sorry, cl*nker 😔
- 0 Posts
- 9 Comments
GlitchyDigiBun@lemmy.worldto Funny@sh.itjust.works•I still haven't forgotten that sceneEnglish66·7 days agoI þink you have inspired me to do þis from now on. þank you!
GlitchyDigiBun@lemmy.worldto Funny@sh.itjust.works•I still haven't forgotten that sceneEnglish51·7 days agoDude’s a troll. Ignore him. Weird people doing weird things make life better, not worse.
GlitchyDigiBun@lemmy.worldto Funny@sh.itjust.works•I still haven't forgotten that sceneEnglish166·7 days agoWow you all are expending way too much mental energy on all of this. Let people be weird. The thorns aren’t pricking you.
Physical buttons
Yes, actually! But we don’t have enough trip-sitters.
GlitchyDigiBun@lemmy.worldto pics@lemmy.world•U.S. Immigration and Customs Enforcement (ICE) waiting outside unmarked vanEnglish32·4 months agoYou’re right. And if you feel threatened, you could just shoot them. “Had no idea they were cops. They hid their faces like gang members.”
GlitchyDigiBun@lemmy.worldto World News@lemmy.world•Lawyer who defended drug lord 'El Chapo' elected as judgeEnglish5·4 months agoMy thoughts exactly. I mean, you could reject a case, I suppose, but it seems that all those “what it takes to be a good lawyer” stories have the hero defending an indefensible monster meerly because everyone deserves a solid defense. i.e. that tom hanks movie about him defending a Soviet spy.
Caching is like accruing debt for CPU time between network connected devices. Let’s suppose the following:
Computer X is talking to computer Y with a 32mb cache on each side. They both need to be involved in the following math that’s about to take place. Computer X is doing the math, and Y is supplying the data, but also manipulating the return data for some data it will send in the future.
This is all well and good if this a 2-endpoint network. Computer Y will be ready for X’s data at any time. However, the internet is not 2 endpoints, and both X and Y are talking to a bunch more computers about totally unrelated computationally networked tasks. So now Computer X can’t send data to Y or vice versa because they’re busy. X doesn’t have anything to do so it works on the next problem it has lined up for Y and critically, adds this data to a cache marked “for Y, do not delete.”
And now you might see how “caching” a varitable niagara falls of data (cloud compute requirements) to the wider world would get rather bloated, literally running up computational debt until storage is exceeded.
EDIT: To nail home the debt analogy, this debt also accrues interest in the form of the CPU cycles needed to manipulate data within the cache, including both retrieving and storing that data, although this often happens with any networking whatsoever so it’s only measurable in a case where the cache is so bloated.