Lobste.rs

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Match the subtitle to the correct movie. Use a series of clues if you get stuck. You’ve got five lives; can you make it through five levels? An endlessly replayable casual game, built in nextjs. Comments

Comments

Comments

Comments

Comments

Comments

Comments

The article explores two ways to manage failure in Haskell. One approach involves passing potential errors forward using types like Maybe or Either, making the possibility of failure explicit. The other takes the opposite route, designing input types that prevent failure in the first place. Using custom types like NonZero or NonEmpty allows developers to avoid many checks later in the code, leading to cleaner, safer programs that rely on strong type guarantees. The idea is to catch problems as early as possible, often right at the boundaries of the system. As a Go developer, it’s always interesting to try to balance very nice concepts from functional-oriented languages and the imperative world without making a mess of it. Comments

Comments

Comments

Looking for ideas on personal data backup. Both the software side and the hardware side. Since almost all personal data nowadays defaults to being hosted online - even data you generally have local copies of anyway - few people seem to ever consciously think about backups, including people working in tech who have better-than-average understanding of privacy and data sovereignty. So I’m wondering how users of this forum handle this. By “personal data” - I mean any data you have access to on your owned devices/online accounts but does not relate to your day job. Your notes, calendar, email, side projects source code/database, pictures, bookmarks, documents. Also data you’ve downloaded/mirrored but is not personal to you because you can’t rely on it being online forever or you just want fast local access to it. What do you consider backup worthy? Do you dump it in some cloud service? You have an elaborate NAS setup running 24x7? Or just some drives you plug in once in a while and run a backup script? What about encryption? Are your backups incremental? Do you prune old versions? Have you ever had to restore from backups? Do you test restoring without needing to? How often? How do you handle different rules for different types of data?

Comments

Comments

Comments

Comments

Comments

Comments

Comments