Live data from Hacker News

Bringing emulation into the 21st century (2021)

blog.davetcode.co.uk

1–10 of 19 posts

Re: Bringing emulation into the 21st century (2021)

#3
post #2

This 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)

#4
post #2

This 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)

#5
post #3
post #2

This 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

Posted on April 1st :)

Re: Bringing emulation into the 21st century (2021)

#7
post #4
post #2

This 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! ;-)

"NodeJS developer refuses to believe that gigahertz means billion hertz" https://www.theolognion.com/nodejs-developer-refuses-to-beli...

Re: Bringing emulation into the 21st century (2021)

#8
post #2

This 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?

> This culminated in the implementation of an 8080 microprocessor utilising a modern, containerised, microservices based architecture running on kubernetes with frontends for a CP/M test harness and a full implementation of the original Space Invaders arcade machine.

I actually WTF'd.

Re: Bringing emulation into the 21st century (2021)

#9
post #4
post #2

This 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! ;-)

Oh they thought of that. Solution:

> Rewrite more things in rust.

Post reply on HN