Live data from Hacker News

Running a Minecraft Server and more on a 1960s UNIVAC Computer

farlow.dev

11–20 of 39 posts

Re: Running a Minecraft Server and more on a 1960s UNIVAC Computer

#11
post #3

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?".

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

And given the NES emulator example, take half an hour per frame.

Re: Running a Minecraft Server and more on a 1960s UNIVAC Computer

#12

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.

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

Re: Running a Minecraft Server and more on a 1960s UNIVAC Computer

#14
post #3

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?".

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

> 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.

Re: Running a Minecraft Server and more on a 1960s UNIVAC Computer

#17

Stupid question, would a quick&dirty LLVM backend for univac be possible to write, or are there inherent incompatibilities due to its weird architecture?

I'm not sure if LLVM would support ones-compliment (does GCC even support that any more?)

Re: Running a Minecraft Server and more on a 1960s UNIVAC Computer

#18

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.

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

> 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.

Re: Running a Minecraft Server and more on a 1960s UNIVAC Computer

#19

Earlier quoted context omitted.

> 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.

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

> 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.

[0] https://minecraft.wiki/w/Java_Edition_protocol/FAQ#What's_th...?

Re: Running a Minecraft Server and more on a 1960s UNIVAC Computer

#20

Earlier quoted context omitted.

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

> 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 wor…

Not enough dedotated wam for all that.
Post reply on HN