I’m already annoyed by the end of public static final string that the variable name doesn’t even bother me in these sorts of langauages. All things should be public, static, & final, by default so they aren’t necessary to write. You should only have to write what unsafeties you are opting into.
Nope. Read it a bit deeper as the failures are for ZFS, BtrFS, Bcachefs, & Ext4.
Gajim, Dino, Conversations support multi-account clients. Threading doesn’t tend to work the same way tho.
https://github.com/openzfs/zfs/discussions/14793
It seems to be an issue in the last year-ish but across a range of WD/Sandisk drives. They build controllers in house &, if the support is to be believed, don’t test or support Linux/BSD.
ncccmmmmppp (however its spelled)
Thanks fish shell for suggesting me the right name with just “nc” ’cause I can’t remember it either
It was usually recommended to lock to inputs anyhow with all the fetchers requiring a hash which I hated having to manually update & like the UX flakes provides (I really wish they supported more than Git & Mercurial tho). You can still have different evals tho if you point to latest.tar.zstd or other non-hashed thing like a branch where the referred to can change & it won’t reproduce. I haven’t used channels in years, but doesn’t that just refer to the running system, not using Nix to build projects?
Saving the dependency is pretty big since each flake you import will bring along its jungle of dependencies now in your downstream project. I can’t think of a use case where < 10 lines is worth a dependency—especially since as you noted, lib has the glue right there for you to put it all together.
I dunno, I don’t trust a guides still recommending flake-utils. You can make the same four loop in like 4 lines of Nix which is a smaller diff & doesn’t pollute your downstream consumers with a useless dependency. Flakes also don’t eliminate pointless builds, fileset or filtering the src can & the only tool with file tracking on by default is the Git VCS specifically (which also involves the intent to add flags which is the other side of annoying).
It’s also not altruistic to pay more for to subsidize in the manner you are alluding too since it misses the larger picture of how these wide free tiers have allowed contemporary services to gobble up users to impress investors with growth despite loss-leading products (in code forges look at the publicly-traded GitLab free model vs. SourceHut where everyone pays a small amount to keep servers running (post-beta plan)).
My affordable provider encrypts their servers & the account storage just fine without needing to reinvent the old, tested protocol (might just be a ZFS pool encryption passphrase). But it isn’t security/privacy that’s in question but the accessibility of this standardized protocols with years of tooling built around it & a business model that I don’t think is sustainable.
Oh I don’t use Microsoft GitHub for almost anything personal, but some language ecosystems only allow packages on the platform …& the issues, discussions, pull request model has lock-in to where you can’t submit a bug, propose a new idea, or even submit a patch unless the maintainer set up something third-party. Due to so many projects with lock-in, to generally participate in free software you must have an account.
Those alternatives are good, and they are more than feature complete. I sometimes choose alternative DVCS for non-work stuff as well. Can’t be forced or forked to Microsoft GitHub if you are not using Git. 🫡
toastal
joined 4 years ago
Learn to love OpenStreetMap