> This means the driver doesn't "search" for empty space. It calculates where data goes using math.
From my understanding, we're still searching for empty space? We just have an easily computable sequence of spots to check. E.g., if our stride is 7 blocks, then instead of going linearly with a stateful search, we can easily compute where we check. It's hard to pull this apart from the README. The README looks a bit LLM generated (clued in by OP's comment as well), which contributes to the difficulty versus a more thoughtful writeup. Interesting idea, it's just hard to tell exactly what's going on.
Additional info: Final Cut Pro is going to keep getting updates, but certain features (presumably AI related) are not going to be included with the one time purchase and are gated to the subscription [1].
The individual one time purchase versions are still available for all the apps. Final Cut, Logic, Motion, Compressor, and MainStage are offered in a bundle for education by Apple as a $199.99 one time purchase (no education status is verified) [1]. Pixelmator Pro is available as a one time purchase as well for $49.99 [2]. Not included in the Creator Studio is the Lightroom alternative Photomator, which is available as a one time purchase of $119.99. You could recreate just the Creator Studio as a one time $250 purchase, or the entire suite (including Photomator) for $370.
Not available for one time purchase are the AI features and templates available for the free apps (Keynote, Pages, Numbers, Freeform).
Personally, I'm glad that one time purchases are still options for the core pro suite: long term they do hold value compared to paying Adobe a subscription (or dealing with the high seas on macOS). However, I don't see things like the education bundle sticking around much longer, so purchase it sooner rather than later.
Yeah, to add some context for people reading this, jj fix works best for edits local to the diff, and it’s meant for edits mostly. With some trickery you could run some analysis, but it’s not what jj fix is meant for right now.
To bring up jujutsu, `jj fix` (https://docs.jj-vcs.dev/latest/cli-reference/#jj-fix) is a more refined way of ensuring formatting in commits. It runs a formatting command with the diff in stdin and uses the results printed to stdout. It can simplify merges and rebases history to ensure all your commits remain formatted (so if you enable a new formatting option, it can remove the need for a special format/style fix commit in your mutable set). Hard to go back to pre-commit hooks after using jj fix (also hard to use git after using jj ;) ).
I agree, my experience is anecdotal. Generally never heard much from Loudoun residents about noise (Loudoun is where most of the N. VA data centers are), it's more of a complaint you hear online from people in other parts of the country that are having data centers built near them. Again, anecdotal.
Ashburn/Loudoun resident here, lived right next to us-east-1 for 10+ years. No, the noise is not impactful. The data centers are very quiet on the outside. More noise comes from Dulles Airport nearby. Main problem is 1. visuals. They are horrendous blobs to look at. 2. land/electricity values. Gone up a lot in the past few years. Happy to answer any questions.