Last weekend I was writing some quick notes in the Notes app, and I could not get it to stop performing nonsensical completions in blinking yellow text. Apple Intelligence disabled, predictive text disabled, various combinations of backspace escape etc. Nothing worked. How hard is it to code a Notes app that doesn't mess with you?
I had to factory reset my Mac because inexplicably Siri, Spell Check, and Apple Intelligence were "disabled by my admin." I have no MDM. I am my admin. I spent roughly a month delving through logs trying to resolve it.
I really wish homebrew supported this feature. There are a bunch of terminal tools I have installed through it (and wouldn't make sense to sandbox) that are basically one-person projects, and I imagine subject to supply chain compromises. I don't urgently need the very latest versions for any of them, as they are unlikely to have exploitable security vulnerabilities on my machine (due to not being involved with any network facing service).
I do kind of think the solution to this issue lies at the OS level. It should provide a high degree of UI and workflow standardization (via first party apps, libraries and guidelines). Obviously it's an incredibly high bar to meet for volunteer efforts, but the user experience starts at the OS level. Instead of even installing a program like "Handbrake" or "Magicbrake" the OS should have a program called "Video Converter" which does what it says on the tin. There should also be a small on-device model which can parse commands like: "Convert a video so it can play on facebook" and deep link into the Video Converter app with the proper settings. Application-level branding should also basically not exist, it's too much noise. The user should have complete control over theming and typography. There has to be a standard interaction paradigm like the classic menubar but updated for modern needs. We need a sane discoverable default shell language with commands that map to GUI functionality within apps, and the user should never be troubled with the eccentricities of 1970s teletype machines.
Agree, the feature of commutative patches just seems obviously superior? Not sure why there's a critical mass to adopt jj over Pijul apart from jj's git backend.
I think this gets at one of my original comments in this thread: I think the reason of commutative patches has communication issues. The benefits touted are very abstract. The problems I’m aware of it solving are mostly theoretical problems for working devs, and so the message hasn’t landed. If I were interested in advocating for these tools, I’d be trying to find a message that does resonate.
I think git compat is the absolute #1 priority for working devs to even consider seriously checking version control tools out. I wouldn’t have tried jj if I couldn’t run it on my work git repo and I didn’t try pijul on my work repo for this reason. It hurts my inner geek who’d like to try using it for something professionally.
> The real innovation of a lot of these alternative DVCS systems is that they free the state of the source from being dependent on the history that got you there. Such that applying patches A & B in that order is the same as applying B' & A' -- it results in the same tree. Git, on the other hand, hashes the actual list of changes to the state identifier, which is why rebasing results in a different git hash id.
Anybody who's wrestled with reordering/rebasing git history or has done git archaology is able to understand this benefit.
From Pijul's site:
> Pijul is the first distributed version control system to be based on a sound mathematical theory of changes
After years of grudgingly tolerating using a deployed prototype for a VCS, yes, I want the mathematically sound alternative.
All that being said, I do wish you the best, because truly, I am tired of git and JJ does seems like an improvement.
Do I benefit from getting the same hash no matter what order I put the patches? In fact getting the same tree either way feels like information loss. Even if I only merge, won't I lose track of what the actual state was when each commit was made?
Most of my wrestling is with merge conflicts and a consistent tree doesn't help with that.
I can easily imagine a world where you could install an open source PWA from an archive file into its own security sandbox without any further hoops to jump through, and it continues to just work indefinitely because the web has very good backwards compatibility guarantees. Instead, we have to get licensed and notarized by the monopolies and they keep you on a constant treadmill of drudgery just to stay up to date. Or you install somebody else's monopoly-approved "legitimate business" app which steals or leaks your data. Sad!
> the web has very good backwards compatibility guarantees
Kinda... Google and folks have been cracking down on security pretty hard, to the point where certain things would probably stop working if you weren't maintaining the security of the endpoint or something correctly. There are APIs (more and more everyday it seems...) that only work with "secure contexts" like HTTPS, and they're working actively on tightening HTTPS requirements (like shortening certificate lifetimes, valid ciphers etc). Sure, this helps improve security, but not without breaking compatibility.
I think this is amazing work and I'm looking forward to trying it out and maybe adopting long term, but I can't help but think they're selling themselves short with the default theme. Personally find the electric blue pretty grating. Would be nice to see more examples of "calm" theming with more neutral tones, or even a preset alternative default for that.
If you're an amateur and really want to spend this much money, get a good enough knife (e.g. the classic victorinox) and a chef's choice electric sharpener, and you won't have any more issues.
I've read multiple reviews saying the chefs choice sharpeners are basically useless. Having owned 2 of them I can confirm they seem to do almost nothing after the first few times using them.
A few YT knife channels have done deep dives showing why they stop working soon after purchase, the details escape me but I have to agree with the end result....
