This is pretty cool, it brings back memories. Thanks for posting.
I used to manage Tru64 (Alpha) and OpenVMS (VAX and Alpha). Mostly Oracle DB and whatever they called their App development suite (horrible, horrible software) for a University's ERP system (called Banner) and infrastructure (Multinet on OpenVMS/VAX for DNS, DHCP, mail, etc). After that I moved on to AIX on Power5 for Oracle on HACMP and Veritas Cluster. Such a different world from what we have now.
I have an old AlphaServer ES47 running OpenVMS and Power5 560Q running AIX in my garage
When I last got the VMS nostalgia bite, I picked up a DS10, on account of the power and space advantages over the ES line, not having a garage and all.
I forget that what I miss was not the system, but the community on the system. Solo VMS is a lonely experience.
> I forget that what I miss was not the system, but the community on the system.
Same. I had VMS running on an AS200 next to a beautiful X terminal, just like the computer lab at school. But my dad wasn't sitting next to me, hunting and pecking away at his old C.Itoh terminal. None of the usual suspects were across the table, locked into their favorite MUDD. And so on. I miss them all so much.
Cluster that sucker. I got a pair of MicroVAX 3900s in a VMScluster, actually using the same disk image, just like they'd use the same physical disk in the old days. ALLOCLASS, bb.
Somewhere, the OpenSimH docs say it'll corrupt the image, so ymmv.
I also have an ES47 (running Linux)! Would you send me an email to my username at gmail? I've been working on a remote management tool for the ES47 that allows controlling the fan speeds that you might be interested in.
But you don't have to handle errors in Go. With multi-return you just don't bother with the "err" value and happily proceed with whatever is in the first return position.
IMHO, only languages with exceptions or Sum types that encode that a return is either a value or an Err (but not both) actually do what Golang says it does (make you handle errors).
I mean, let's do it. But it seems more straightforward to tax wealth as capital gains when it's used as collateral for liquid assets (low interest loans, lines of credit, buying twitter).
The worst thing about UEFI HTTP boot is the utter lack of information to debug anything that's gone wrong. Whether that's the DHCP filename option is some wrong format for whatever stupid mode the UEFI is in, or there's some dhcp relay issue. It literally tells you almost nothing besides "can't get NBP file size".
The error messages seem to be written by people on a happy path who don't know how utterly broken almost everything about networking and DHCP even is.
And this is all IPv4! The IPv6 stuff is even more cryptic with different DHCP options and dealing with RAs and managed-flag, other-flag, etc.
It's infuriating. And I work on a team that writes code to generate all these things for automating bare metal for a living.
It's probably a good idea to follow the path of this article and get everything working in a VM first where booting is faster and it's easier to sniff packets. Once you have vanilla OVMF working you can try booting real servers.
I agree with you, but haven't really left yet since there's still a good amount of discourse outside AI related topics. Seems a significant amount of contributors here are all to eager to fall over themselves putting themselves, their juniors, children, and colleagues out of work, long term.
My personal stance is that the genie is out of the bottle, and there's likely no putting it back. Kind of like nuclear weapons: I wish they didn't exist, but since they do I'd rather be on the side that has them.
Honestly it's an incredible technology the likes of which I never thought I would see in my lifetime. It's definitely not perfect, but it is improving at a frightening pace. Some days I am optimistic for how it might shape the future, and other days I am scared.
If goverments wanted to make a credible effort to limit how they are used, I would support that. But I'm not terribly optimistic that can or will happen.
I'm going to sound like a lunatic, but the best bug tracking software I've ever used was Apple's Radar internally. I wish they'd open source it. I've also had a bunch of fever dreams about re-implementing it as a product.
Quality in general seems to be going downhill, too.
Frequently the desktop app and the safari extension won't be in sync and missing a recently added password, or doesn't show up on my other devices hours later. I still have no idea how the extension vs desktop app actually work together, or if they do at all.
Sometimes 1password (safari extension) is "locked" - but the desktop app isn't locked? and No amount of clicking the little 1password icon, that's supposed to unlock it does anything. Just a completely no-op button. Quitting safari _and_ the desktop app seems to be what's required to fix it.
I've been thinking about just moving back to native macOS keychain, but I haven't bothered to check on linux+windows support.
I'm using Strongbox (uses a KeePass-compatible database) which integrates into Apple's AutoFill API and appears automatically in all input fields - just like Keychain. No extension needed.
The publishing process for Safari extensions is painful, but otherwise it's not meaningfully different from Chromium extensions and there's no good reason for it to work worse in Safari.
Way fewer people are going to look at obscure things, so a lower percentage of issues will likely have been found. There is less fame and fotune in spending security research time on obscure software. Most small libraries won't be covered by any bug bounty programs either for example.
Even accepting the premise, is it not immediately obvious to you that folks will be spending more money and effort aiming AI at higher-impact targets? This isn’t all-or-nothing.
Half joking.