QNAP unforgivably uses a proprietary version of ZFS with their own extensions that are not compatible with mainline OpenZFS.
It can only zfs send/receive to other QNAP devices. While your data is protected like any other ZFS system, it is _NOT_ interoperable. You can not take a zpool out of a QNAP system and access it on another system with ZFS.
I discovered this painfully the hard way, and won't buy from them again, unless I plan to wipe the software and run something open.
There are very real reasons to use ZFS instead of the oldschool Linux block device sandwich.
mdadm+luks+lvm still do not quite provide the same set of features that ZFS alone does even without encryption. Namely in-line compression, and data checksumming, not to mention free snapshots.
ZFS is quite mature, the feature discussed in the article is not. As others have pointed out this could have been avoided by running ZFS on top of luks and would have hardly sacrificed any functionality.
It's funny how polarizing this is. Seemingly based on whatever system you grew up on, or are most accustomed to.
I find Mac's window management to be something of a joke, and can't imagine why anyone would want to replicate it. I do see the value of the global menu but everything else feels wholly unintuitive to me.
I can't stand that cmd+tab takes you to the last app, not the last window, and raises all that apps other windows as well. I literally never want that.
The parent's complaint about non-native docker is not solved by colima. It's not bloat from the desktop app it's the fact that you have to run a VM to run any sort of container runtime on a mac.
Took me a bit to find this, but you can click on a line number in multi-buffer to open that file at that location. I think their default assumption is for you to not use the mouse much.
If you're using vim mode g+[space] will open the file where your cursor is. I think it's alt+return in normal mode but either way there's a shortcut hint on the right side of the header for the file your cursor is currently in.
Each person on my team has a day of the week they own, and then we have a rotation for weekends, and negotiate holiday/pto trades. I guess it really only maps correctly for a 5 person team.
We previously had a week long rotation, and some folks were initially skeptical of the idea to change, saying they were worried they'd feel like they were "oncall all the time". But, they agreed to try it for a month. That was a bit over a year ago now, and no complaints.
I think it ends up being a lower stress configuration, because it just becomes part of your normal expected work-week routine, and generally isn't as mentally draining.
It does make end of year PTO/holiday time a bit more complex to work out, but so far my team has been okay with that tradeoff.
That seems completely backwards?
Debit interchange fees are usually lower aren't they? and if you run it with a pin as a debit there's almost no charge for the vendor.
Definitely weird, as everything I know about the incentives for that go in the other direction for a vendor.
I thought it was generally known they were operating at a loss?
even with the subs and api charges, they still let people use chatGPT for free with no monetization options. Sure they are collecting the data for training, but that's hard to quantify the value of.