Bringing emulation into the 21st century (2021)
blog.davetcode.co.uk
Bringing emulation into the 21st century (2021)
1–10 of 19 posts
Re: Bringing emulation into the 21st century (2021)
#2I got suspicious at this line:
> Secure by default (mTLS on all function calls)
I thought to myself, what does HTTPS/TLS have to do with writing an emulator, normally a local-only piece of software?
Re: Bringing emulation into the 21st century (2021)
#3This is satire, in case anyone is wondering. I got suspicious at this line: > Secure by default (mTLS on all function calls) I thought to myself, what does HTTPS/TLS have to do with writing an emulator, normally a local-only piece of software?
Re: Bringing emulation into the 21st century (2021)
#4This is satire, in case anyone is wondering. I got suspicious at this line: > Secure by default (mTLS on all function calls) I thought to myself, what does HTTPS/TLS have to do with writing an emulator, normally a local-only piece of software?
> Alright, if you’ve got this far I’m sure you’ve realised that the whole project is something of a joke. That said it is also an interesting intellectual exercise to consider whether it’s remotely possible to achieve >=2MHz with the architecture delivered.
2MHz with an architecture, which is up to 21st century hypes, that would be some! ;-)
Re: Bringing emulation into the 21st century (2021)
#5This is satire, in case anyone is wondering. I got suspicious at this line: > Secure by default (mTLS on all function calls) I thought to myself, what does HTTPS/TLS have to do with writing an emulator, normally a local-only piece of software?
Haha, I came here to make an "Is this a joke?" response
Re: Bringing emulation into the 21st century (2021)
#6Re: Bringing emulation into the 21st century (2021)
#7This is satire, in case anyone is wondering. I got suspicious at this line: > Secure by default (mTLS on all function calls) I thought to myself, what does HTTPS/TLS have to do with writing an emulator, normally a local-only piece of software?
Also mind: > Alright, if you’ve got this far I’m sure you’ve realised that the whole project is something of a joke. That said it is also an interesting intellectual exercise to consider whether it’s remotely possible to achieve >=2MHz with the architecture delivered. 2MHz with an architecture, which is up to 21st century hypes, that would be some! ;-)
Re: Bringing emulation into the 21st century (2021)
#8This is satire, in case anyone is wondering. I got suspicious at this line: > Secure by default (mTLS on all function calls) I thought to myself, what does HTTPS/TLS have to do with writing an emulator, normally a local-only piece of software?
I actually WTF'd.
Re: Bringing emulation into the 21st century (2021)
#9This is satire, in case anyone is wondering. I got suspicious at this line: > Secure by default (mTLS on all function calls) I thought to myself, what does HTTPS/TLS have to do with writing an emulator, normally a local-only piece of software?
Also mind: > Alright, if you’ve got this far I’m sure you’ve realised that the whole project is something of a joke. That said it is also an interesting intellectual exercise to consider whether it’s remotely possible to achieve >=2MHz with the architecture delivered. 2MHz with an architecture, which is up to 21st century hypes, that would be some! ;-)
> Rewrite more things in rust.
Re: Bringing emulation into the 21st century (2021)
#10Do we even need code anymore? I'm pretty sure that Ansible + YAML is turing complete, right? /s