I didn't realize that Space Invaders was so complicated.
Bringing Emulation into the 21st Century
11–20 of 24 posts
Re: Bringing Emulation into the 21st Century
#12I've been considering a project to build a basic emulator (Game Boy, maybe?) entirely in Redux, with React for pixel rendering. I'm sure the performance will be awful, but it would be an interesting exercise.
Re: Bringing Emulation into the 21st Century
#13For 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.
What really would have sealed the deal was implementing this in WASM, translating it into Verilog, then burning it into an FPGA
Re: Bringing Emulation into the 21st Century
#14I 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.
That's the joke, though: that C++ is looked down on with distain and treated as an obsolete language by some members of the younger generation of programmers.
Re: Bringing Emulation into the 21st Century
#15I 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.
[deleted]
Re: Bringing Emulation into the 21st Century
#16I wonder what performance gains we could obtain by running locally all services on loopback. The network latency should be the same of kernel itself.
Re: Bringing Emulation into the 21st Century
#17Utterly 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 t…
To anyone who might be confused, the parent and gradparent posts (mine) are intended to be comedic, consistent with the tone and spirit of the article itself.
Re: Bringing Emulation into the 21st Century
#18Utterly 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.
I'm so glad somebody gets it! Sometimes you have to hold onto your ideals of architectural purity in the face of minor performance hiccups.
(This is my project and I'm really happy it made its way on here)
Re: Bringing Emulation into the 21st Century
#19Utterly 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.
I'm so glad somebody gets it! Sometimes you have to hold onto your ideals of architectural purity in the face of minor performance hiccups. (This is my project and I'm really happy it made its way on here)
I actually laughed out loud when I got to the part where each opcode was its own microservice, implemented in a dozen different languages. Well done.
Re: Bringing Emulation into the 21st Century
#20I wonder what performance gains we could obtain by running locally all services on loopback. The network latency should be the same of kernel itself.
loopback + gRPC