←back to thread

414 points henry_flower | 1 comments | | HN request time: 0s | source
Show context
digitalsushi ◴[] No.43108644[source]
Spock levels of fascinating from me. I want to learn how to compile a pdp11 emulator on my mac.
replies(4): >>43108726 #>>43108732 #>>43108743 #>>43109755 #
snovymgodym ◴[] No.43108726[source]
https://opensimh.org/

Works great on Apple Silicon

replies(1): >>43108833 #
haunter ◴[] No.43108833[source]
What’s the difference between an emulator and a simulator in this context?
replies(3): >>43108965 #>>43108980 #>>43119814 #
bityard ◴[] No.43108965{3}[source]
There is LOADS of gray area, overlap, and room for one's own philosophical interpretation... But typically simulators attempt to reproduce the details of how a particular machine worked for academic or engineering purposes, while emulators are concerned mainly with only getting the desired output. (Everything else being an implementation detail.)

E.g. since the MAME project considers itself living documentation of arcade hardware, it would be more properly classified as a simulator. While the goal of most other video game emulators is just to play the games.

replies(3): >>43109176 #>>43115056 #>>43116663 #
Imustaskforhelp ◴[] No.43116663{4}[source]
I don't want to offend you , but this has made me even wonder more what the difference is.

It just feels that one is emulator if its philosophy is "it just works" and simulator if "well sit down kids I am going to give you proper documentation and how it was built back in my days"

but I wonder what that means for programs themselves...

I wonder if simulator==emulator is more truer than what javascript true conditions allow.

replies(1): >>43126091 #
1. kragen ◴[] No.43126091{5}[source]
It's fuzzy.