Rendered at 17:56:46 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
djmips 19 minutes ago [-]
I would like to see this code instead compiled native instead of via the RISC-V interpreter.
proxysna 5 hours ago [-]
What a great write up, and a video too! Even though Minecraft stuff ofc was a bit of a bait, it would be interesting see the answer to "Can it run Doom?".
jandrese 32 minutes ago [-]
Feels kind of like when Usagi Eletric got "Doom" running on a vacuum tube computer with a teletype interface without support for even ASCII, but it was just an imitation of the background music.
Anything for the thumbnail.
zimpenfish 4 hours ago [-]
> a bit of a bait
"a bit" is doing a lot of work there. It was absolute nonsense. They were no closer to running a Minecraft server than I am to running UKGOV.
voidUpdate 4 hours ago [-]
They hosted a program that allowed minecraft clients to connect... I'd class that as a minecraft server, even if it wasn't a very good one
zimpenfish 1 hours ago [-]
> They hosted a program that allowed minecraft clients to connect...
Connect in the sense of receiving a login packet and saying "yes". That's it. Steps 1, 2, 3, 9, 10 of [0] (they didn't mention encryption or compression, I'm assuming they didn't implement it.)
They didn't mention anything about any of the steps past 10 - again, assuming they didn't implement them.
It's a trivial thing they've implemented - good work, sure, but a Minecraft server? Absolutely not.
Yeah, my thought exactly, execution lacked, but i do admire the attempt.
voidUpdate 4 hours ago [-]
It could probably run the code for doom, once recompiled for the risc-v emulator, but given that the only output is a paper teletype, displaying it would be a problem
toast0 3 hours ago [-]
> but given that the only output is a paper teletype, displaying it would be a problem
You are in a maze of twisty passages, all alike. A cacodaemon floats by, hissing.
Cthulhu_ 4 hours ago [-]
And given the NES emulator example, take half an hour per frame.
petterroea 2 hours ago [-]
Stupid question, would a quick&dirty LLVM backend for univac be possible to write, or are there inherent incompatibilities due to its weird architecture?
mmastrac 1 hours ago [-]
I'm not sure if LLVM would support ones-compliment (does GCC even support that any more?)
kaladin-jasnah 5 hours ago [-]
Hah, I heard about this at VCF East this year, but didn't get to check out the exhibit. There was another MC server demo running on old Macs IIRC. Shame the event was cut short due to a bomb threat.
Dwedit 3 hours ago [-]
"What's My Line" had in-show advertisements for the UNIVAC computer.
I watched the video when it came out, I've been a fan of his stuff for a while. It'd been a while since he uploaded and I was rewatching some of his videos the night before this was uploaded!
vaughnegut 4 hours ago [-]
Favourite article I've read in a while, what a delight. I wonder what kind of performance you could get if someone hand wrote a dedicated, modern C compiler for it.
voidUpdate 4 hours ago [-]
According to the article, it takes 40 univac instructions to run a single risc-v instruction, so potentially up to 40x the current performance. Though you'd probably need more instructions to do things than a single one, so probably less than that, say 10-20x? Especially if you made a custom compiler that made the best use of the hardware you could, since it's weird
commandlinefan 1 hours ago [-]
> it takes 40 univac instructions to run a single risc-v instruction
Which is wild, given:
> The computer’s original purpose was to be used by the Navy to read in radar signals and direct artillery
I'd really be fascinated to see how that was done on such a primitive machine, shame that's probably been lost.
mrgaro 2 minutes ago [-]
The radar "reading" was done by first plotting analog radar signals to the antique rotary radar displays. Then there would be human operators with a light pen, marking each radar signature on each radar turn.
So the Univac would receive input coordinates for each target and track those in memory each turn.
Anything for the thumbnail.
"a bit" is doing a lot of work there. It was absolute nonsense. They were no closer to running a Minecraft server than I am to running UKGOV.
Connect in the sense of receiving a login packet and saying "yes". That's it. Steps 1, 2, 3, 9, 10 of [0] (they didn't mention encryption or compression, I'm assuming they didn't implement it.)
They didn't mention anything about any of the steps past 10 - again, assuming they didn't implement them.
It's a trivial thing they've implemented - good work, sure, but a Minecraft server? Absolutely not.
[0] https://minecraft.wiki/w/Java_Edition_protocol/FAQ#What's_th...?
You are in a maze of twisty passages, all alike. A cacodaemon floats by, hissing.
https://www.youtube.com/watch?v=rEQlOrPs6fw
Which is wild, given:
> The computer’s original purpose was to be used by the Navy to read in radar signals and direct artillery
I'd really be fascinated to see how that was done on such a primitive machine, shame that's probably been lost.
So the Univac would receive input coordinates for each target and track those in memory each turn.