Gargron shared a status by alicetragedy

Laura ✨🎨

alicetragedy@mastodon.social

Here’s a thought on the current heatwave that is absolutely destroying humankind across Europe atm: maybe we should push for a regulation to allow people — ALL people — to stop working in temperatures above 30C. The economy would collapse and finally politicians would take fighting the climate crisis as a priority, rather than leaning into the bullshit narrative that “summer is summer” from their air-conditioned ivory towers.

2 hours ago

Eugen Rochko

Gargron@mastodon.social

@fesshole What a horrible day to read fesshole.

25 minutes ago

Gargron shared a status by parismarx

Paris Marx

parismarx@mastodon.online

honestly i welcome the data center lobby just openly saying climate goals needed to be trashed so the tech industry can build ai — intense heat waves, record forest fires, worsening natural disasters be damned

https://www.politico.eu/article/europe-choose-ai-climate-goals-data-center-chief-warns/

#tech #ai #datacenters #climate #heatwave

13 hours ago

Gargron shared a status by fedilucie

lucie :neocat_floof:

fedilucie@rivals.space

$Meme sous le format "STOP DOING": STOP DOING SYNCHRONISATION - THREADS WERE NOT SUPPOSED TO BE interrupted - YEARS of SEMAPHORES yet NO REAL-W - wanted to shared something anyway for a laugh? We ORLD USE FOUND for anything other than LOCKS had a tool for that: It was called "BEING NICE" - "Yes please let me get WRITE access to a ressource. Please I have been spinning on my lock" - Statements dreamed up by the utterly Deranged LOOK at what Programmers have been demanding your Respect for all this time, with all the computers & languages we built for them (THIS is REAL CODE, made by REAL programmers) pub unsafe auto trait Send { } _Bool atomic_compare_exchange_weak_implicit( volatile A obj*, C* expected, C desired, memory_order succ, memory_order fail ); They have played us for absolute fools ??????? ???????"Hello !?????????? would like to WARNING: ThreadSanitizer: lock-order-inversion (potential deadlock) (pid= Cycle in lock order graph: M0 (0x000000000000) => M4 (0x000000000000) = Mutex M4 acquired here while holding mutex M0 in thread T1:$