Readit NewsI used the original Planet Computers device with psion-like keyboard, the Gemini, as my daily driver for a few years. The keyboard was no gimmick - it really felt like a quasi mini-laptop. A brilliant device, even considering the weak cpu (as compared to similarly priced phones)
Such a shame ...
(btw, had a psion 2, psion 3, psion 5 & sharp zaurus back in the day, so you can say I'm a sucker for these things)
https://store.planetcom.co.uk/products/astro-slide
I suppose this means that they still have a firm intention to produce eventually, hopefully even with an updated chipset given that the original parts are lost ("ODM is effectively unwilling to release remaining produced stock and the pre-purchased chipsets"!) Obviously you know all that, fellow backer, but just in case anyone else is interested in this debacle:
https://www.indiegogo.com/projects/astro-slide-5g-transforme...
At this point I think of it as the Delorean of handheld computers...
https://www.zdnet.com/product/cosmo-communicator/
[Edited for typos]
AIX only runs on non-mainstream hardware (POWER), plus IBM isn’t as open as Oracle is with providing access to it. This makes it significantly harder to support than Solaris is
Added to that, Solaris and Linux are closer to begin with. Historically, Linux copied a number of its APIs from Solaris; AIX was far less of an influence. Years ago, I had to port some psuedoterminal management code from Linux to both Solaris and AIX. I only had to make some minor changes to the Linux code to make it work on Solaris; the changes I had to make to get it to work on AIX were much more extensive
I've been able to debug PostgreSQL issues reported by [closed] Solaris users by booting illumos inside a virtual machine on my laptop in minutes...
I want to keep AIX support, for, well mainly irrational nostalgic reasons -- PostgreSQL used to run on pretty much the entire Unix family tree, and I wrote lots of code on AIX for a decade. But they make it hard. I don't know why an OS vendor wouldn't make an image of an OS available to developers as conveniently as possible (it is even possible to boot recent AIX versions on QEMU if you have the patience... the hypothesis is that they might have done work to make that possible, 'cause it didn't work in earlier versions; but you can't get an image of OS, so shrug).
https://www.postgresql.org/message-id/flat/CY5PR11MB63921AB0...
I know Windows has IOCP and also now an IORing implementation of its own (Less familiar with macOS capabilities other than POSIX AIO).
https://learn.microsoft.com/en-us/windows/win32/api/ioringap...
Update: Most of the comments below seem to be missing the fact that Windows now also has an IORing implementation, as I mentioned above. Comparison article here:
https://windows-internals.com/ioring-vs-io_uring-a-compariso...
Main learnings: the IOCP version can't do asynchronous flush! Which we want. The IoRing version can! But it can't do scatter/gather AKA vector I/O yet! Which is an essential feature for buffer pool implementation. So actually I am basically waiting for IoRing to add support for that before taking it too seriously (I can see they are working on it because the ops are present in an enum, it's just that the build functions are missing).
So my guess is that in a year or so we should be able to run all PostgreSQL disk I/O through IoRing on Windows. Maybe?
Another complications is that it really wants to be multithreaded (consuming completions for IOs started in another process requires a lot of hoop jumping, I made it work but...) This will resolve itself naturally with ongoing work to make PostgreSQL multithreaded.
The next problem is that IoRing doesn't support sockets! So in future work on async networking (early prototypes exist) we will likely also need IOCP for that part.