The AI instructions in the `specs.md` file gave me a couple clues, e.g. `at` is the directory where the worktree should be created.
And it's clearly using btrfs subvolumes for managing a collection of related Git working trees; there's a concept of "parent" and "child" worktrees.
I don't yet understand why it's better than worktrees, other than being theoretically instant to create new ones (which could, I suppose, be a noticeable speedup if your repo is very very large).
But yeah, some more hand-written instructions in the README would definitely be helpful. I'd be particularly interested to learn whether some of the common "gotchas" one can run into with worktrees are solved by Rift or not. (E.g., I've never needed to move my "root" git repo, but apparently that causes problems because the worktrees then can't find the root repo; does Rift deal with that situation correctly?)
I'm just one datapoint, but my Framework 16 (bought a little over a year ago with no OS, has only ever had Linux installed on it) has never given me trouble with firmware updates. I've updated the BIOS twice, and other firmware, all through `fwupdmgr` with no issues. I bought the AMD chip rather than Intel, it's possible that that was why I had no issues, but I don't actually know.
I'd call that pretty recent :) – fwupdmgr wasn't supported (not as in 'you're on your own', but 'blobs not published to registry') until a few years ago. EFI shell update wasn't available early on. When I say I'm trying to, I'm actually struggling to establish if it's even possible without at least using Windows to jump to a certain version after which I can use EFI/fwupdmgr.
Since logging into the backdoor account produced a `#` prompt instead of `$`, it was uid 0, so the last will and testament was either in `/root` or in `/`, depending on how the non-backdoor root account was set up.
Plus, if Flynn was running those commands while logged in as "backdoor" rather than while logged in as "root", the text displayed on-screen specifically says that the backdoor account doesn't have a home directory configured so it would treat `/` as the home directory. Which would mean the computer now has a `/last_will_and_testament.txt` file. That's pretty prominent and attention-drawing. It's going to be found by anyone who investigates that computer.
Tron Legacy was, I think, only the second film soundtrack I ever purchased (first one being Lord of the Rings). It's still among my favorite music to listen to while coding; something about it just puts me in the "flow" frame of mind right away.
And you can't know ahead of time, when you're training the model, what business domains it will be used for. Someone may decide to use it to optimize the watering and fertilizer cycles of their automated potato-growing setup, and suddenly the "how to grow a potato" texts that went into training the model are actually the very things that make the difference between success and failure for the code the model spits out.
Considering the first thing I saw in the thread was https://news.ycombinator.com/item?id=48244891 where the values returned from sp's sine function was compared to the correct values, I'm going to take any such opinions with a few grains of salt. Because the correct sine for the number they tested (31337 radians) is 0.3772 (0.3771522646 according to my calculator), sp's implementation returned 0.4385. That's not even close to right.
Not OP, but I'm guessing by running the code on itself, i.e. turning the code into a QR code (or a series of them), then scanning those QR codes on the phone and reassembling them using a text-editing app on the phone.
Slight correction: Jews were religiously prohibited from charging interest... to other Jews. (As I understand it, and someone please correct me if I'm wrong: not being Jewish myself, my information is second- or third-hand for most of this). Which is part of why they ended up being moneylenders to the non-Jews they lived among. Another part was that, as people who often had to pack up and move, fleeing from armed groups (who may or may not have had the official sanction of the local authorities, but usually did have their unofficial sanction), Jews tended to gravitate towards professions where most of their wealth was portable. Farming? Nope, get chased off your land and your profession is gone. Blacksmithing? Your tools and your stock-in-trade are too heavy to move quickly. Also nope, not if you expect to need to run for your lives at very short notice. But moneylending, or selling gold and jewelry? That works. Grab one or two chests and throw them onto the cart, and you've preserved most of the core of your business, even if the mob torches the shop and any tools that were impractical to move.
So Jews ended up gravitating towards being jewelers, bankers, moneylenders, and so on. All of which, yes, did feed into stereotypes.
There have also been long(-SH) periods of times where they were banned from any form of guild participation or membership, which drove them to this - i.e. in Bohemia, at least around the 15th century, re-selling wares that no one else wanted to buy (in the book I have read this in, bloodied clothing and weaponry from battle was one example) was one of their means to survive.
And it's clearly using btrfs subvolumes for managing a collection of related Git working trees; there's a concept of "parent" and "child" worktrees.
I don't yet understand why it's better than worktrees, other than being theoretically instant to create new ones (which could, I suppose, be a noticeable speedup if your repo is very very large).
But yeah, some more hand-written instructions in the README would definitely be helpful. I'd be particularly interested to learn whether some of the common "gotchas" one can run into with worktrees are solved by Rift or not. (E.g., I've never needed to move my "root" git repo, but apparently that causes problems because the worktrees then can't find the root repo; does Rift deal with that situation correctly?)
reply