51 karma · joined February 11, 2022
Ctrl-X/C/V were originally Macintosh (and maybe Xerox before that?) and then were adopted by Windows in the 3.1 era so Word for Windows would match up better with Word for Mac. But PC not having a Command key, and the Windows key not being a thing yet, they were applied to Control instead. Which of course overlapped with the other major use of Ctrl-C as "interrupt" starting back into early UNIX machines (and adopted by DOS) but... being a graphical environment they apparently didn't consider that important at the time.
Just means their interface and workflow is bad and needs to be improved though, not that the doctor needs to be removed from the process altogether.
Don't fall for the trap that all of this is inevitable, you have to try and resist it first.
Not particularly happy with Google for other reasons either. There are some days I want to go back to the days of Windows Mobile ROM kitchens and PalmOS. At least it wasn't such a monoculture back then.
Lots of info on the 51xx series of machines is here: https://www.minuszerodegrees.net/index.htm
Wear parts shouldn't be irreplaceable. That's like having a car you have to throw away when the brake pads or tires are worn out, because they're welded in place, AND have a computer making sure they don't get replaced anyway by someone who knows how to weld.
Found it: https://archive.org/details/Getting_Started_with_TRS-80_Basi...
/api/v1/employees/100 - direct path to a resource. 404 if it doesn't exist.
/some_photo.jpg - direct path to a file/resource. 404 if it doesn't exist.
/photo/100 - direct path to resource: photo ID 100. 404 if it doesn't exist.
/photo?id=100 - search for a photo with ID "100". Return a code 200 with an empty results set if that ID is not found. (With optional application-specific error feedback in the response body.) 404 if /photo doesn't exist at all.