Coder Murph (@codermurph) header
Coder Murph (@codermurph) profile picture

Washington DC to Tromsø Norway. Computer Science PhD student. Possibly in over my head. Non-technical alt: @sleepymurph

Tromsø, Norway
Joined December 2010
Each result is a section of a reference and there are hits for each section of each separate reference for each model processor they make and I had to go to Wikipedia to research their naming conventions to even make a guess as to what model I might want to try looking at
1
16
My MACshake brings all the hoes to the lane
1
25
trying to help a friend with their squarespace site like
4
41
I got so frustrated with the combinatorial explosion of functions in <string.h> that I spent two days making a database to keep them straight lol
1
123
Accidentally opened the dev console while I was on Discord. I gotta admit this is clever.
2
57
No! Bad twitter! Bad!
45
Ok I finally sat down and mapped out the Intel processor modes for myself.
1
47
I love how, right after inventing the general integer semaphore, Dijkstra goes on to admit that actually all you really need is a binary semaphore (*cough* lock *cough*) and you can implement all the other stuff. But he keeps the general one because it can be handy.
1
1
19
Dijkstra showed that if you can just have atomic increment (V/up/signal) and atomic compare-and-decrement (P/down/wait), then with that primitive you can build all the of the things they were trying to build, and not only that but you can reason that it is correct. This is locks.
1
1
22
Dekker is credited with figuring out how to use separate "critical" flags for each process plus a "turn" variable as a tiebreaker. You could also just turn off interrupts. But I imagine programmers then forgot to turn off interrupts the way programmers today forget to use locks.
1
1
16
In his paper, Dijkstra explains two new features of ALGOL 60 so that readers can follow the syntax in his examples: the *array* and the *for loop*. Or as Dijkstra puts it "the so-called 'for clause.'" This is how far back we're talking here.
1
1
19
People were just kinda flailing at synchronization. They had the concept of *critical sections* but they didn't really know how to use them or how to implement them properly. That was the scene when Dijkstra walked in like "railroad signals tho?" and blew everyone's damn minds.
1
2
32
I'm glad I picked up the book though because the intro gives some context that really helped things click for me. This was the 60s and dudes who are now absolute legends of CS had no idea what they were doing. I mean even PETER NAUR thought software was in crisis.
1
1
32