In case you want a webring, but don't feel like setting up your own server to run it, I run a webring hosting service that you might find useful: https://webri.ng/
The Sequential Prophet X is another modern synth with a full-blown x86 PC running inside it. You can see the mainboard in this video: https://www.youtube.com/watch?v=Q8QDCocnt0M
Really awesome work! A simple OS for retro x86 hardware is a really cool project! I wish I still had some era-appropriate hardware I could test-drive it on.
When the author says 'I tend to run older hardware', how old do they mean? I'm typing this message right now on my Thinkpad x220 from 2011, which is unfortunately too old to run Zed because its internal Intel HD graphics card doesn't support Vulkan. I'd be an everyday user if not for this.
One of the coolest projects I've seen in a while! Amazing work! In case anyone missed the write-up^1, it's very well-written. I really enjoyed the chapter about designing the instruction set.
A lot of effort goes into accurately emulating historic processors in the MAME project, as well as other vintage hardware. It's generally accurate enough that MAME is regularly used to emulate vintage hardware when reverse-engineering devices.
Very cool! Would you believe I was actually just listening to some of the old Ultima game soundtracks when I saw this?
I wonder if they considered writing their disassembly in the 'pre-C++98 dialect of C++' used in the original, and targeting the original compiler. I've done some disassembly of binaries which ran on vintage systems, and I would've targeted the original toolchain if I could have. It's an interesting philosophical question.
Thinking about what would be going through Bill Kerman's little head as he approaches the rocket having just seen poor Jebediah Kerman vaporised on the launch pad was pretty funny. I don't think this same gallows humour extends to kittens.
If I set a folder colour in Finder on my work MacBook, and then plug that USB drive into my personal computer which uses Thunar as a file browser on Debian, nothing would happen.
To me it seems more sensible to store information relevant only to this OS in a specific cache somewhere within that OS. It would even make cache-like functionality such as evicting old entries super easy.
In case anyone doesn't know, Oxyrhynchus is a major source of archaeological discoveries. Particularly ancient (Ptolemaic/Roman Egypt) papyrus fragments recovered from an ancient landfill on the outskirts of the city. Notably some of the earliest-known Christian textual artefacts were found there (the actual earliest fragments came from elsewhere in Egypt). It turns out that Egypt's hot and dry climate provides the perfect environment for their long-term preservation.
> Its unlikely that another platform would be able to reach this state...
Is this really true? The computer ecosystem is more open now than ever. The original PC BIOS (which PC-compatible manufacturers needed to implement) was never an open, documented standard. It was a proprietary, closed system made by IBM. It's pretty fair to say that IBM didn't anticipate a PC/x86 ecosystem developing around their product. They even sued companies who made their own compatible BIOSes (like Corona). Intel didn't really have much to do with the success of the product at that point in time either, much less Microsoft.
In contrast, every widely-used modern system for hardware abstraction (UEFI/ACPI/DeviceTree/OpenSBI/etc) are open, royalty-free standards that anyone can use. Their implementation in ARM is newer, and inconsistent, but that's only because of how hugely diverse the ARM ecosystem is.
Some of my first experiments with Ada were based on this tutorial series! Great to see it on the front-page of HN.
Since this was published, it's become a lot easier to set up an ARM toolchain using Alire, Ada's package manager. AdaCore have also created some new tools for auto-generating the startup code for ARM systems: https://www.adacore.com/blog/ada-on-any-arm-cortex-m-device-...
Hello! I don't have a website for your webring, but I do run the webri.ng service (https://webri.ng), where you can host your webring! Just thought I'd mention it in case it's useful to you.
Speaking as an Australian that works on React CRUD applications because there's nothing else in the market, I've been reading through this thread thinking the exact same thing.
Something about these JS-heavy sites I haven't seen discussed: They don't archive well.
Websites that load a big JS bundle, then use that to fetch the actual page content don't get archived properly by The Wayback Machine. That might not be a problem for corporate content, but lots of interesting content has already been lost to time because of this.
Blog: https://ajxs.me