3 ms·

Yeess. Recommendation, drop everything & go read Matt Webb on the computing that could have been, talking SAGE & multi-user workspaces[1]! > Right now we’re in

Yeess. Recommendation, drop everything & go read Matt Webb on the computing that could have been, talking SAGE & multi-user workspaces[1]! > Right now we’re in the era of personal computers. Collaboration, social use of tools, togetherness: all of these are hacks on top of something that, at its core, was designed for the individual first. > But there’s a particular photograph of group computing from the 1950s, from before the PC was invented... I wonder how much if at all Engelbart was aware of SAGE. Webb poonts out Engelbart got started working on computers out of SAGE. > As an aside, the whole "meta-verse" craze might pull these ideas through to the mainstream again. Heck yeah, right on. Even if the immersive modes fail, I really hope some embodiment survives. Constructing space & environments in which being & event can occur, manifesting processes... I have a lot of hope we can start to better ground & make real computing. [1] https://interconnected.org/home/2021/12/21/sage https://interconnected.org/home/2021/12/21/sage https://news.ycombinator.com/item?id=31665364 https://news.ycombinator.com/item?id=31665364 (12 points, 10 hours ago, 2 comments) https://news.ycombinator.com/item?id=31535139 https://news.ycombinator.com/item?id=31535139 (14 points, 12 days ago, 1 comment)

TedDoesntTalk 4y ago
I mean, have you played any massively multiplayer online game in the last 20 years?
- rektide 4y ago
  Now we just need to start presenting computing inside these environments! Those projects of using Doom to kill processes... http://psdoom.sourceforge.net/ http://psdoom.sourceforge.net/
  - spicybright 4y ago
    > In the original implementation of the program, 'pid monsters' could be killed not only by the program's user, but also by other 'pid monsters' and normal Doom monsters on the level. The reasoning behind this behavior was that "on very heavily-loaded machines, it is not uncommon for the OS to kill random processes." Unfortunately, the number of monsters in a given area must be depressingly small in order for them to avoid both intentional infighting and friendly fire. Since monsters would tend to kill each other off until only a few remained in the area, the user was severely hampered in the ability to orderly control processes on the machine. Therefore, the default behavior of psDooM is to ensure the player is the only character in the game who can wound and kill 'pid monsters'. This avoids accidental process deaths from monster infighting. Unfortunately, it doesn't prevent accidental process deaths from a user's poor aim. ;-} The original behavior of 'pid monsters' being as vunerable as other monsters may be enabled with a command line flag. That's amazing lol

TedDoesntTalk 4y ago

I mean, have you played any massively multiplayer online game in the last 20 years?

rektide 4y ago
Now we just need to start presenting computing inside these environments! Those projects of using Doom to kill processes... http://psdoom.sourceforge.net/ http://psdoom.sourceforge.net/
- spicybright 4y ago
  > In the original implementation of the program, 'pid monsters' could be killed not only by the program's user, but also by other 'pid monsters' and normal Doom monsters on the level. The reasoning behind this behavior was that "on very heavily-loaded machines, it is not uncommon for the OS to kill random processes." Unfortunately, the number of monsters in a given area must be depressingly small in order for them to avoid both intentional infighting and friendly fire. Since monsters would tend to kill each other off until only a few remained in the area, the user was severely hampered in the ability to orderly control processes on the machine. Therefore, the default behavior of psDooM is to ensure the player is the only character in the game who can wound and kill 'pid monsters'. This avoids accidental process deaths from monster infighting. Unfortunately, it doesn't prevent accidental process deaths from a user's poor aim. ;-} The original behavior of 'pid monsters' being as vunerable as other monsters may be enabled with a command line flag. That's amazing lol