"#Nix's design encourages a separation of build planning from build execution: evaluation of the Nix language produces derivations, and then then those derivations are built. This usually a great thing. It's enforced the separation of the more complex Nix expression language from the simpler derivation language" https://github.com/NixOS/rfcs/blob/master/rfcs/0092-plan-dynamism.md
has anyone seen a really good analysis of the problems with git's command line UI? Would love to read it. for example:
git checkout is dangerous and has too many different jobs (though git switch is trying to fix that!)
for a tool that's supposed to make changes easy to undo, you actually need to learn a LOT of ways to undo
(not looking for git tutorials, explanations of git’s underlying model, or explanations of why you think git's UI is actually good, just an analysis of the problems)
@b0rk The syntaxes <commit1>..<commit2> and <commit1>...<commit2> do different things in git diff and git log. Perhaps having a different notation for the diff case would have been bettter.
George Morrow, discussing the truth behind AI on a 1986 "Computer Chronicles" episode:
"How could such names as 'expert systems' or 'artificial intelligence' ever have been coined in the first place? Well my theory was that in the late 50s, when university-based computer research was largely funded by the military, these names were invented to impress the granting agencies. As often as not, this type of research had little, if any, connection with reality. And the more ambitious the sound of the project, the better chance it had to be funded.
"Now much of today's AI-type software is quite novel and very useful. But none of these products will be able to live up to the image that the term 'artificial intelligence' invokes."
Pro tip: if a disclosure button toggles between "show more" to "show less" or similar, you don't need aria-expanded. The state is already indicated. (This comes up again and again in audits.) #ariaSerious#aria#webdev#a11y#tips
