I disagree with the sentiment and welcome the future. But I do agree the way the author skips over the reason this exists and the problematic nature of their readme is a red flag. Either they agree with the dogwhistles or are being intentionally obtuse to proclaim that it's "only about the code".
Definitely don't see this project having legs or at the very least not advancing very far.
Seems to just open the door for discrimination under false pretense. "well their code wasn't good. Nothing to do with their identity." We've seen it time and time again that it's confusing why so many reject reality.
That's a major benefit of ZFS for sure, but I think being copy on write is another major benefit for single disk systems. ZFS is the only one I know of that has a full feature set and is supported on every major OS.
This WWDC was the nail in the coffin for me. Apple has lost the plot and is back to self indulgent projects. Picked up a Pixel again and glad I don't have to deal with liquid glass in the future.
I feel similarly. This iPhone is the only Apple device I own outside of a shared Apple TV. I'm not in the Apple ecosystem so moving back to Pixel for me would be easy.
To me it seems like Google trying to mirror the iOS Advanced Data Protection and lockdown mode. Just ways to put security front and center to counter Apple's "we're the privacy company" schtick.
Reminds me of when Jony Ive had the run of the place and gave us the bending iPhone and MacBooks with no ports. All for the sake of "Designer Experience".
Apple designs stuff this way on purpose. They think it's neat to "discover" something that should be obvious. The new camera app is a perfect example of this. No indication that swiping up from the bottom brings up a menu for camera controls. The fact any of these obviously terrible design and implementation choices are praised is baffling.
I understand people not liking Recall. I'm one of them. But for something that is opt in now and even if opt later can still be disabled. So changing OS's because of that seems like an overreaction.
It's the straw that breaks the camel's back I think for most people.
Constant nagging by the operating system for Windows products (I have enabled onedrive personally, but for some reason it installed two file explorer quick access links, and the workarounds online fail to persist reboots) -- hijacking file extensions, hijacking program aliases (I just had to remove a windows store alias in my env variables for "python" despite having it already installed months prior), the constant cat and mouse to have local account-only possible, inability to remove edge/stop being pestered about it, and now recall (which is not truely opt-in since it gets installed whether you want it or not).
the crutch is that an update could silently re-enable it, in a way that you aren't notified, and it'd be too late to try disable after it captured content off your machine you didnt want captured.
Well it's the code that matters. Not what their beliefs are.
code is also garbage
Well it's the thought that's important.
reply