With tight deadlines, there frequently isn't the time to not be working concurrently on the same doc, especially when it comes to anything technical.
3,414 karma · joined February 8, 2018
Autistic and ADHD. Not terribly socially apt, likely sorry if we are having a disagreement in the comments and would buy you a drink.
With tight deadlines, there frequently isn't the time to not be working concurrently on the same doc, especially when it comes to anything technical.
The statement being made is "Very anti-HN thinking to be posted here."
Rather than present useless analogies, engage with what's actually been presented. I didn't ask about your grandmother.
I get daily outreach from fly-by-night operations in other countries using LLMs and templates to crap out the above, complete with client logos and project examples that don't belong to them. Where is the "proof"?
If you're aiming at devs, why would they use this over the likes of GitHub Pages or Cloudflare Pages?
Probably ongoing support. It was no iPhone in terms of units sold.
I'm sure someone could probably vibe code a FOSS repo for this in an afternoon if it's as capable as the average comment here seems to claim (hasn't been my experience, but would love to solve a problem and be proven wrong).
See Dunning-Kruger.
HN also drank the crypto-crap and NFT Kool-Aid. It's nice to see people able to not follow the groupthink.
I know some brilliant people, but, well, putting it kindly, they're as useful as a chocolate teapot outside of their specific area of academic expertise.
Yes, Unraid can crash-and-burn in quite a lot of different ways. Ask me how I know! Why I'm all-in on ZFS now.
The magic of ZFS repairs isn't in RAID itself, IMO, it's in being able to take your cold replicated dataset, e.g., from LTO, an external disk, remote server etc, and repair any issues without needing to resilver, stress the whole array, interrupt access, or hurt performance.
RAID can correct issues, yes, but ZFS as a filesystem can repair itself from redundant datasets. Likewise, you can mount the snapshots like Apple Time Machine and get back specific versions of individual files.
I wish HN didn't limit comment depth as these are great questions and this is heavily under-discussed, but it's arguably the best reason to run ZFS, IMO.
Another way of putting this—you don't need a RAID array, you can do individual ZFS disks and still replicate and repair them. There's no limits to how many replicas or mediums you use either. It's quite amazing for self-healing problems with your datasets.
But if the file system is corrupt then you're hosed and end up with a `lost+found`. It sounds great until it fails, and then you realize why ZFS with replication makes sense. Unraid doesn't do automatic repairs from replicated ZFS datasets yet either even if you use individual ZFS disks within your Unraid array.
The cache pool is recommended to be mirrored for this reason (not many people see why I find this to be amusing).