Hmm.. but isn't a JITted emulator on a modern PC actually much faster nowadays? Just asking.
For those of us who prefer the real-deal this is a way of using original kit, but also making it faster + more ram + storage etc.
The Amiga hardware scene is very much alive and kicking and there's new products coming out all the time.
Original hardware with modern FPGA-based expansions is a lot better in terms of retaining the feel of the Amiga and not compromising on performance.
That said I am looking forward to the V4 standalone and A1200 V4 cards, both being instabuys for me.
"Updated emulation core from WinUAE 3300b2."
Since then, WinUAE has had _6_ major releases, the changelog is visible on the front page and you can simply go there and read it, the list of features I consider killer is too big:
Old school computer are pretty slow, but they react faster than our modern computers.
There was this comparison of "time to first character" or something like that - when you press a button, how long is it until you see a character on screen? IIRC old school computers like Apple II and Amigas won over Intel Core i* monsters.
edit: https://www.pcgamer.com/the-latency-problem-why-modern-gamin...
I still miss the Amiga magic and wish we had something similar now, not just boring x86/64..
The Amiga was technically better, in a way that can't easily be emulated. The Amiga video hardware could generate an interrupt at the end of the video frame output. As a result, an application could do all its work for the current frame, then call a "wait for vsync" function. That made it yield to the OS scheduler. When the interrupt fired, the scheduler would handle it and reschedule the app VERY QUICKLY. It was almost like a real-time OS. It knew that video generating was time critical.
I don't think you can't do that on Windows or Linux. The video hardware _might_ support interrupt generation but it isn't wired into the OS in the same way. You might get close to being able to use the "wait for vsync" in full screen DirectX apps, but even then it's a nightmare of video driver lies and OS scheduler complexity instead of a nice clean, simple, reliable feature all applications can use.
I'd be interested to know if Wayland solves this problem.
Heck, back in the day, even though I loved my Amiga, I preferred the editor of Turbo C to more sluggish, font rendering editors on the Amiga. DOS in text mode was unconditionally fast.
Maybe VR will drive the technology back to low latency. Latency in VR equals users throwing up.
I might now try to recreate the classic Amiga Bezier lines screen saver.
The next day my machine had rebooted itself (presumably to apply an update) and now the stutter is gone.
That's the kind of thing that didn't happen on an Amiga :-)