1,139 karma · joined April 7, 2018
You need language-level support for your packaging for this, so that the compiler or runtime can bind a call to foo.bar() to foo 1.0 when the call happens in x, and foo 2.0 when it happens in y.
- soldiers need to be fed
- attacks on undefended locations are more likely to succeed
- if you can set your enemy on fire, do so, people really don’t like being on fire
- Where are the log files for $service stored?
- What do the values of $one_letter_code in this message format/log line mean?
- What do I grep for to diagnose $problem?
More generally, when I find that I have memorised how to look something up (search slack for $foo to find the instructions, type $bar in the browser address bar to bring up the wiki page with the host name I need), I try to just memorise the fact directly, to reduce friction.
(Of course, as we see time and again, the real portability solution is for users to standardise on a single platform)
Why did they assume that? 4k pages are a feature of the memory management unit of the cpu. Optional support for large pages came to x86 with pentium in the mid-1990’s. Presumably all x86 cpus out there today have large page support, but the assumption of the 4k default is deeply ingrained.
SHELL=‘/bin/bash -vx’
in your make invocation - the shell will then vomit all commands it runs to stdout.
Economic statistics for Russia and Ukraine would like a word.