10 points | by jnord 6 hours ago
7 comments
I just got served a big chunk of JSON, not even pretty-printed, with the text in there... somewhere. Difficulty level: quite high, even in reader mode.
(same on macOS+Firefox and iPhone+Safari)
I think it's a caching issue. I got it to render properly by adding a cache-busting query string to the URL:
https://dfarq.homeip.net/nec-v20-cpu-a-bit-of-pep-for-an-xt/...
I thought it was an error message but I can't tell from my phone using Brave.
Appears to be fixed now.
(If not - zoom way in, and it's relatively readable.)
You're not alone.
I knew it was possible to run CP/M programs (and CP/M itself) on my PC with its V20, but I never found out how.
Not mentioned - the NEC V30 CPU, which was the V20's 8086-replacement near-twin:
https://en.wikipedia.org/wiki/NEC_V20#Variants_and_successor...
IIR, the V30 provided a notably better improvement (over the 8086), because the 16-bit memory bus meant it was less often starved for bandwidth.
I just got served a big chunk of JSON, not even pretty-printed, with the text in there... somewhere. Difficulty level: quite high, even in reader mode.
(same on macOS+Firefox and iPhone+Safari)
I think it's a caching issue. I got it to render properly by adding a cache-busting query string to the URL:
https://dfarq.homeip.net/nec-v20-cpu-a-bit-of-pep-for-an-xt/...
I thought it was an error message but I can't tell from my phone using Brave.
Appears to be fixed now.
(If not - zoom way in, and it's relatively readable.)
You're not alone.
I knew it was possible to run CP/M programs (and CP/M itself) on my PC with its V20, but I never found out how.
Not mentioned - the NEC V30 CPU, which was the V20's 8086-replacement near-twin:
https://en.wikipedia.org/wiki/NEC_V20#Variants_and_successor...
IIR, the V30 provided a notably better improvement (over the 8086), because the 16-bit memory bus meant it was less often starved for bandwidth.