miniblog.

← Back to all posts
Sep 19, 2014 at 20:41
"an unavoidable tradeoff between feature-richness and usability" great Yegge article that I hadn't seen before:
steve yegge - nonesuch-beast
The Nonesuch Beast Stevey's Drunken Blog Rants™ I keep running into the same problem. This problem, or maybe it's a class of problems, is hard to talk about because of its inherent complexity. But not being able to articulate the problem well hasn't actually deterred it from coming to bite me

Related Posts

Aug 7, 2021 at 20:38
If function f1 is unused, and f2 is only called from f1, Rust complains that both f1 and f2 are unused. I find this confusing: it's useful to know that I can remove both functions, but removing f2 alone gives a compile error. Not sure what the best tradeoff is though.
Feb 9, 2020 at 15:54
Lessons learned from writing a linter/static analysis tool for shell scripts: https://www.vidarholen.net/contents/blog/?p=859 (Preserve positions, use error codes and document them, and there's a tradeoff between beginner mistakes and advanced mistakes!)
Dec 11, 2019 at 22:00
Dependency management in Go: https://research.swtch.com/vgo-principles There's a tradeoff between work for libraries (declare your minimum version/any incompatibilities) vs work for programs (investigate when dependencies aren't compatible). If programs are more common, should we empower them?