o11c

41 ms·

541.
by o11c 1y ago
This fails to address the main concern I run into in practice: can you recover if some resources timed out while downloading? This often fails in all sorts of ways: * The client treats timeout as end-of-file, and thinks the resource is comp
542.
by o11c 1y ago
https://bugs.gentoo.org/383179
543.
by o11c 1y ago
The "different laws" thing really should be handled by changing the types of all the nodes around the critical passes. Unfortunately, every language I know sucks at typing if you want to avoid all the copying that the naive appr
544.
by o11c 1y ago
The problem is that nature abhors monocultures. And when the monoculture collapses, there's no guarantee that actually-useful species usefully survive.
545.
by o11c 1y ago
This is quite informative for an introduction to one particular type of IR. It's better than some others because it actually does mention that there are alternatives in some places. And since what people are using an IR for varies a lo
546.
by o11c 1y ago
Hmm, "cloudfail" is already in use, and "cloudfuckyou" while descriptive is profane enough that it will cause unnecessary friction with certain people, and "clownflare" is too vague/silly (and is less appl
547.
by o11c 1y ago
Well, one thing I've noticed about LLVM is that it blatantly and intentionally relies on UB. The particular example I encountered probably isn't what causes the version breakage, but it's certainly a bad indicator. That sai
548.
by o11c 1y ago
The problem is that TLS was already in widespread use for "thread local storage". Transport Layer Security is widely documented as beginning in 1999. I can find references to "Thread Local Storage" going back to at least
549.
by o11c 1y ago
Just CREATE VIEW something (ahead of time, so it's ready) for the rare time you need to visually inspect it.
550.
by o11c 1y ago
> I've never tried doing an 8-bit vs 10-bit-per-color "blind" test, but I think I'd be able to see it? In my tests with assorted 24-bit sRGB monitors, a difference of 1 in a single channel is almost always indistingui
551.
by o11c 1y ago
How so? From what I see it is almost* strictly less useful than BSD make, which (IMO) is strictly less useful than Solaris make, all of which are strictly less useful than GNU make. It only might be more useful than SysV make. * Regex suppo
552.
by o11c 1y ago
I'm pretty sure distro-specific spec files can make it matter. But you really, really should be using `pkg-config` (and no other obsolete `foo-config`) so you don't have to worry about it regardless. (If you really want to do it
553.
by o11c 1y ago
One again, this site misses a lot of details, some of which are quite important: * build-essential - this actually installs what is considered "essential" for Debian packages. This happens to include some common compilers, other
554.
by o11c 1y ago
I prefer `-ff` over just `-f` to avoid the annoyance of every line being interrupted by another process. `strace-log-merge` can merge the files again if you really care.
555.
by o11c 1y ago
Because 50% of humans are stupider than average. And 50% of humans are lazier than average. And ... The only reason people don't frequently talk themselves out of prison is because that would be both immediate work and future paperwork
556.
by o11c 1y ago
If you semi-trust your tool binaries enough not to do something silly like making syscalls directly, what about using the `LD_PRELOAD` equivalent to intercept `open` etc.? (Yes there's a long tail in that "etc.") Or does usin
557.
by o11c 1y ago
For a long time, one of the major problems with alternate allocators is that they would never return free memory back to the OS, just keep the dirty pages in the process. This did eventually change, but it remains a strong indicator of di
558.
by o11c 1y ago
As always, git's answer to the problem is "stop being afraid of `git submodule`." Cross-repo commits are not a problem as long as you understand "it only counts as truly committed if the child repo's commit is refer
559.
by o11c 1y ago
I'm only vaguely aware of how other people do perfect hashing (generators I've used always seem to produce arrays to load from), but dabbled in a purely-arithmetic toy problem recently. As an exercise for the reader: There are
560.
by o11c 1y ago
It's perfectly possible if they start downranking sites full of ads. But an ad company will never do that.
561.
by o11c 1y ago
"/bin/sh does not point to bash" is not the same as "does not use bash for scripting" On my system there are 42 scripts in /bin -> /usr/bin (merged) that start with some variant of `#! /b
562.
by o11c 1y ago
Use: command -v -- -x The POSIX documentation for almost all commands (including `command`) says "The command utility shall conform to [...] Utility Syntax Guidelines" which specifies the behavior of `--`, even if it's
563.
by o11c 1y ago
To be fair that's missing a lot . I'm not sure how much is just showing its age and how much it never had. The actual bash manual is quite informative. In particular, failure to mention `printf -v` is horrible. Not only is it bet
564.
by o11c 1y ago
Use ' %q' and you also fix the problem of program names starting with a dash.
565.
by o11c 1y ago
To be fair, most of those "basic problems" have basic solutions as long as you're not trying to avoid GNU tools. The nastiest case is probably `globasciiranges`.
566.
by o11c 1y ago
This is woefully misguided. Half the time passing it to the shell is explicitly a feature, e.g. `popen("gzip > foo.gz")`. If you have user input you should always sanitize it regardless of API. But `ssh` does deserve all the
567.
by o11c 1y ago
Checking other libcs (note that "edit the header" is not that difficult to automate): bionic - must edit the header dietlibc - must edit the header glibc - undocumented but reliable, see the dance in the original post
568.
by o11c 1y ago
The "always enough interesting characters" problem needs to be solved by something along the lines of "if an important NPC dies, the role is passed to an heir". But ... also the world needs to be less murder-y, and (rela
569.
by o11c 1y ago
You don't have to recompile, just do the following (at least on glibc): #include <sys/types.h> // pull in initial definition of __FD_SETSIZE #undef __FD_SETSIZE #define __FD_SETSIZE 32768 // or wh
570.
by o11c 1y ago
There's no need to actually do all the opening if you control the code. You can do anything with `fcntl(F_DUPFD{,_CLOEXEC})` and `fdopen`.

More ›