4 ms·
>How many bugs and wasted CPU cycles and instances of human frustration (not to mention bad design) have resulted from that one small shortcut about 40 years a
by coldtea 4y ago
>How many bugs and wasted CPU cycles and instances of human frustration (not to mention bad design) have resulted from that one small shortcut about 40 years ago?
Not many? In the sense that, considering several UNIX and C design issues and footguns, the dotfiles are the least of our worries (compare e.g. to C buffer overflows or shell escaping rules, to name but two)...
I also don't particularly like the repeated ditches at "lazy programmers" - isn't the whole "New Jersey" style [1] heavy on laziness?
In fact, if those "lazy programmers" were given OS level-APIs and libs doing the right thing about dotfiles, they wouldn't have recoded them on their own in their programs...
[1] https://en.wikipedia.org/wiki/Worse_is_better#New_Jersey_style https://en.wikipedia.org/wiki/Worse_is_better#New_Jersey_sty...
- doctor_eval 4y agoThat link is awesome. Thanks.
- pantulis 4y agoIt's not my intention to second guess Ken, but at least in terms of performance I'd say that the current user home directory structure would bet a hit in the buffer cache since Unix got filesystem buffer caches. In terms of wasted CPU cycles, it's another story but hey these are the days of using npm packages to basically do a string comparison.
- ParetoOptimal 4y agoNot a fan of worse is better. I have some rough thoughts on expressing why: > This leads one of the major cognitive biases in software development where people speak of tradeoffs without establishing they are Pareto Optimal, and wrongly arriving at the conclusion “nothing more can be done without a huge effort”. https://www.paretooptimal.dev/pareto-optimality-and-software-development/ https://www.paretooptimal.dev/pareto-optimality-and-software...
- coldtea 4y ago>Not a fan of worse is better. That's ironic given your handle on HN :) >This leads one of the major cognitive biases in software development where people speak of tradeoffs without establishing they are Pareto Optimal, and wrongly arriving at the conclusion “nothing more can be done without a huge effort”. Well, part of the idea is to do the "pareto optimal" work not just implementation-wise, but also in checking whether the tradeoffs are pareto optimal (pareto-ception). Thus, avoid "analysis paralysis"
- jstanley 4y ago> Here Bob has ignored Pareto Optimality for the context of phone security and convenience because he could enable automatic updates at no (well little) cost to convenience This is just not true. Software updates break things all the time. Having software updated behind your back is incredibly inconvenient.
- imwillofficial 4y agoAuto updating does so much for security it seems a no brainer. Is there a way to improve testing while gaining the benefits of auto updates?
- hansvm 4y agoSomething about automatic updates feels off: So software has bugs, and sometimes those bugs are bad, so we want to do something to mitigate that risk -- the risk that we might have something as serious as RCE in our software. To reduce the chances of somebody exploiting that hypothetical remote code execution vulnerability we have special code running on our machines that reaches out to download new code and executes it, blindly trusting that every Jo Schmo who's ever written software we were comfortable using once would never take advantage of that position. The fact that automatic updates sometimes have some benefits right now seems almost accidental when their fundamental operating principle is to open exactly the same sort of backdoor they're trying to protect against.
- imwillofficial 4y agoExperience has shown us that setting up a secure update mechanism is less risky than not updating your applications regularly. Is this always the case? Nope. But for most cases, updating often against newly exposed threats is worth the vulnerability that auto update introduces.
- coldtea 4y agoNot everybody has security as first priority. Not to mention the update could introduce security issues itself.