I have the compiler on GitHub [1] - I just started working on it again after a 2-year hiatus (to finish my PhD).
As for language-server, I'm currently sketching out some plans to use SMLnj's "Visible Compiler" feature, since that seems the easiest path forward. I have a half-baked language-server based on MLton's def-use output, but it's too unstable to share. I am planning to make some progress on the language-server in the next couple weeks.
Also Oracle OCI has OKE, which is Oracle Kubernetes Engine. It works nicely and the quality of service has been very good in my experience over the past four years.
Why is it a bold assertion? Looks like the Oracle folks just need to submit a PR to the CAPI docs to include a link to their provider which is available now.
It's usually quite hard to find people who don't work at Oracle who speak positively about Oracle Cloud.
We tried to use it at work, it was the second-biggest disaster of a cloud provider we've ever encountered (Huawei is the first). Stuff is just broken so often it's hard to ever feel like you can trust it.
ZFS and BTRFS have nice online scrubbing features, but nearly every filesystem these days is journaling, including NTFS and XFS (and its contemporaries). Journaling means every block has a checksum. Sure, FAT32 doesn't have that, but no one should ever have the expectation of data integrity on FAT32. You can run checkdisk on journaling filesystems to scrub for errors.
Many journal filesystems use a checksum for log entries, but that is certainly not covering every block of the filesystem with a checksum. And that checksum only comes into play during log recoveries. Once a block is committed to disk there is no checksum in play (unless the fs has special support for it).
Some newer journaling filesystems support metadata checksumming, but that is not some requirement to be journaling. XFS has not always supported metadata checksumming, and it’s a relatively recent addition to ext4 (like last decade). NTFS doesn’t do checksums on even metadata. This is one reason why ReFS is a thing.
FAT is a requirement of UEFI though, isn't it? So if you can boot from the drive, you can't rely on it to have the filesystem integrity preserved at the disk level.
Journaling means that there is a two phase commit to the metadata of the file system. This helps avoid file system corruption on unclean shutdown and speed up recovery after an unclean shutdown. But it has nothing to do with data checksums. You can’t perform any scrub like behavior to validate your on, e.g., ext4 just because it has a journal.
To elaborate, you specify design rules for your PCB design and layout based off what your chosen fabrication company's abilities are. Each company's fab process is slightly different and will have varying requirements or specifications you must meet in order to have a successfully produced board.
Things like minimum/maximum trace widths, minimum/maximum via size, via types (buried, blind, tented, etc), pad size, solder mask tolerances, component separation distances, etc.
This often means you need to choose a fab before you design your board... and changing to a different fab later on might mean you have to redesign part/all of your board (particularly if you are pushing tolerances). Each fab has different abilities and requirements.
You shouldn't really target a particular fab, you should target a sort of "class" averaged from the capabilities of multiple fabricators. Services that shop your order around basically do this for you, if they bother to quote standard rules at all.
This will save you from redesign work, though realistically it's saving you from vendor lock-in and price gouging. Sierra can manufacture pretty much anything... but who can afford them?
I also saw this (Naur's piece) linked to in that thread; thank you for submitting it, and it's rather a shame it didn't get many upvotes. It is definitely front-page worthy. I just sat down to read it, tonight.
And wow, what a treat it was. I thought I knew what is argument was going to be (that theory building is the primary task of programmers) — but the plot twist I did not see coming was the argument that it is inherently a part of the programmer's mind, and cannot be separated from the mind! And wow, was it well argued. Went in for a lesson in engineering, and got schooled in philosophy too.
I heard its name frequently around the time before nginx came to its fame. Maybe 15 years ago. However, I never heard any major players use it after that.
It sounds like a cool project and I'd love to see it! And even have the option to open a PR and help ;)