Bringing Emulation into the 21st Century
blog.davetcode.co.uk
Bringing Emulation into the 21st Century
1–10 of 24 posts
Re: Bringing Emulation into the 21st Century
#2Yep. Modern software in a nutshell.
Re: Bringing Emulation into the 21st Century
#3Utterly brilliant. It's inspiring to see a modern microservices architecture approach used to such great effect. While the performance penalty seems somewhat steep at first blush, we know this problem solves itself as computers get faster. And in return we get a library of highly portable opcodes which can be efficiently re-purposed by other processor implementations.
Re: Bringing Emulation into the 21st Century
#4Some of this seems slightly tongue-in-cheek, especially this part:
"As can be seen from the screenshot above, space invaders as deployed onto an AKS cluster runs at ~1KHz which gives us ample time for debugging but does make actually playing it slightly difficult."
Nonetheless it does still seem like an interesting technical exercise creating a 'distributed emulator' implemented using services, even if it's too slow to be of much use. :)
Re: Bringing Emulation into the 21st Century
#5Utterly brilliant. It's inspiring to see a modern microservices architecture approach used to such great effect. While the performance penalty seems somewhat steep at first blush, we know this problem solves itself as computers get faster. And in return we get a library of highly portable opcodes which can be efficiently re-purposed by other processor implementations.
Agreed. This is the way of the future. Is there a subscription model? I'd like myself a CPU-as-a-service. $50-100 a month seems reasonable.
Using these "efficiently repurposable" building blocks we can even create new software! Ultimate composability. I'll rent you a couple of instructions and you can create whatever turing-completeness your heart desires for the low, low cost of $0.01 per instruction. (I will have to send all your data to our headquarters in Russia and China, but only occasionally.)
Did anyone patent this already? Time to jump on this.
Re: Bringing Emulation into the 21st Century
#6This satire is judging a professional-technical assault on civilization by the criteria of useful, self-contained tools. As you laugh at the spiritual abortions who wrangle kubernetes for a living, they laugh back, even louder, all the way to the bank.
Re: Bringing Emulation into the 21st Century
#7For those that didn't read/skim to the end:
> Alright, if you’ve got this far I’m sure you’ve realised that the whole project is something of a joke.
Re: Bringing Emulation into the 21st Century
#8[deleted]
Re: Bringing Emulation into the 21st Century
#9Utterly brilliant. It's inspiring to see a modern microservices architecture approach used to such great effect. While the performance penalty seems somewhat steep at first blush, we know this problem solves itself as computers get faster. And in return we get a library of highly portable opcodes which can be efficiently re-purposed by other processor implementations.
What interesting software could be emulated from when CPUs had clock rates in the 1-3 kHz range, the reasonable performance target for this advanced technology? According to Wikipedia, the ENIAC operated at about 5 kHz.
Re: Bringing Emulation into the 21st Century
#10I know this is a joke, but the idea feels very over engineered and unnecessary complication.
> emulation is still stuck firmly in the 20th century writing single threaded C++ of all things
I just don't know why you treat C++ as a 20th century language.
It has involved a lot and now we have C++20.