https://www.bbc.com/future/article/20250501-the-haunted-video-game-that-traumatised-the-web #hauntedgaming #retrohorror #N64ghost #cursedtech #HackerNews #ngated
Today I learned: If you don't add (require 'server) before calling (daemonp), your Emacs daemon will silently hang.
The thing I don't actually want to learn at all, ever.
It took 3 hours to debug, I found solution completely accidentially: just forgot to remove it, when was playing with (server-running-p).
Wikipedia on disadvantages of sparse files:
"Loading executables on 32 bit Windows (exe or dll) which are sparse takes a much longer time since the file cannot be memory mapped in the limited 4 GB address space, and are not cached as there is no codepath for caching 32 bit sparse executables"
Who thought "I will make a dll that's full of 0 bytes, and let the filesystem handle it as a sparse file" could possibly be a solution to their problem?
So we have:
- RAMFS pretending to be mass storage
- a compatibility layer pretending to be BCPL over POSIX
- MorphOS reimplementing Amiga reimplementing BCPL
- vvfat pretending to be a disk with a fat partition on top of that
- a plugin pretending to be the X-Mass hardware
- the X-Mass hretending to be a spinning disk when it's an SSD
- unidos pretending to be amsdos
- amsdos making the disk access behave like a tapedrive
- finally, the user application running ontop of all this
https://github.com/lexbailey/terminal.docm
A terminal emulator implemented using Microsoft Word macros