mihaip
The fundamental issue is that there’s two acceleration curves being applied (the guest OS’s and NeXTStep’s). I experimented with the unadjustedMovement option (https://developer.mozilla.org/en-US/docs/Web/API/Element/req...) but it didn’t seem to help (and if anything, made things feel even harder to control)
If you'd like to play the NeXT version of DOOM and explore a few other apps, they're in the "Infinite HD" drive (you can get to different drives by clicking on the computer icon in the Workspace file viewer).
The Internet Archive also has some collections: https://archive.org/details/classicpcgames and https://archive.org/details/softwarelibrary_msdos_games
The solution we ended up with was partially a matter of the minimum change to fix the issue, and partly because we have a lot of platforms to cover with a small team, so the fewer platform-specific concepts we have (frameworks in this case), the easier it is to maintain.
This is an in-progress port of the SheepShaver emulator to WebAssembly/Emscripten, https://github.com/mihaip/infinite-mac/issues/34 is tracking the remaining work.
If you're interested in running older Mac software in the browser, the BasiliskII-based sites at https://system7.app/ and https://macos8.app/ may be better bets. They will boot faster and have fewer compatibility issues (especially System 7).
The main thing that Mac OS 9/SheepShaver brings is PowerPC support. There is also a variant of System 7 for PowerPC with more esoteric mid-90s Apple projects like OpenDoc and QuickDraw GX installed available at https://system7.app/?domain=system7-ppc.app.
There are also a couple of variants that boot either System 7.5.3 or KanjiTalk 7.5.3 (the Japanese version of MacOS): https://system7.app/ and https://kanjitalk7.app/
RetroGit: digests of your GitHub commits from years past
The tool uses the "high-fidelity" Atom output mode for getting at item bodies. That preserves namespaced XML elements and other extra data from the feed. It uses JSON for everything else, and will fall back to regular Atom output if the high fidelity mode is not well-formed (it was added in late 2010, as things were winding down, and thus never got a lot of testing).
If the XML parse errors are listing any item IDs, feel free to email them to me (mihai at persistent dot info) and I'll see if there's any workaround from my side.
Edit: If it's "XML parse error when fetching items, retrying with high-fidelity turned off" messages that you're seeing, then those are harmless (assuming no follow-up exceptions). The retry must have succeeded.