dapperdrake

6 ms·

61.
by dapperdrake 5mo ago
It gets better: (NOT a lawyer) Previously, liability and indemnification could be bureaucratically laundered to "engineers", because it was a huge diffuse set of people. Now the bag is left with top of the chain for authorizing
62.
by dapperdrake 5mo ago
Luckily, no oversupply of people who understand null-sets, Hausdorff-separable spaces, and databases.
63.
by dapperdrake 5mo ago
Missed opportunity to add a context window key ;)
64.
by dapperdrake 5mo ago
That is the point.
65.
by dapperdrake 5mo ago
The basic argument was "NFS is stupid". The basis for this claim is its data model being ill-suited to network latency. This is different from "useless".
66.
by dapperdrake 5mo ago
Here is what email patches are all about: https://blog.ffwll.ch/2017/08/github-why-cant-host-the-kerne... I tried email patches with another person myself. The only reason GH won here, is because the git people m
67.
by dapperdrake 5mo ago
Which all boil down to "replace NFS with something that has a better data model."
68.
by dapperdrake 5mo ago
And also, this is what makes NFS useless. Latency is at least two orders of magnitude higher. That is the (relevant) difference here. And treating it like a loc system with all the incidental non-optimizations made the NAS use-case take 4
69.
by dapperdrake 5mo ago
Does -Ofast still ignore -fno-fast-math ?
70.
by dapperdrake 5mo ago
Have had to do this live in a production MtG card management application. It worked well. The owner kept their MtG card money. Lisp saved the day.
71.
by dapperdrake 5mo ago
This also really bugs me. To be fair, the gcc people are unkind to both servers and laptops.
72.
by dapperdrake 5mo ago
Firstly, atomicity and/or thread-safety not composing is where the Consistency and Isolation come in. The "application layer" always has to enforce its own consistency guarantees. If the lower layers are total garbage, then
73.
by dapperdrake 5mo ago
Not quite. For persistence latency, yes. For read-only access there could be way better caching, especially for common use cases like listing the contents of a filesystem directory. But stuff like this was excluded on purpose. NFS is real
74.
by dapperdrake 5mo ago
Unix and POSIX are fractally a booby trap.
75.
by dapperdrake 5mo ago
Alpine Linux has a better shot at acceptable compile times. Some FOSS software seems to maximize kernel IO last time I had a Gentoo.
76.
by dapperdrake 5mo ago
> well behaved readers. Around and around we go.
77.
by dapperdrake 5mo ago
GNU coreutils is known for adding command libe options. One of the big philosophical differences to the BSD's. For a human being, it sucks both ways.
78.
by dapperdrake 5mo ago
Welcome to building something new.
79.
by dapperdrake 5mo ago
Isn't this how Kernighan and late Ritchie (K&R) ended up with unix and C? Honestly, brilliant guys. When C got its own standards committee they even rejected Ritchie's proposal to add fat pointers to C before it was too late t
80.
by dapperdrake 5mo ago
Additional point: The point of data storage is to be a singleton. (Backups are desireable, anyhow.)
81.
by dapperdrake 5mo ago
Filesystem access is mostly treated by users as serialized ACID transactions on "files in directories." "Managing this resource centrally" is where unix syscalls came from. An OS kernel can be used like a specialized li
82.
by dapperdrake 5mo ago
Unix embodies this, as well. When K&R created unix and C there was still the better option of moving changes that were better to have in the "kernel" into the kernel. Now we have "standards" that even cause headaches
83.
by dapperdrake 5mo ago
Isn’t "cd" a unix syscall , because it changes the process's working directory? There was something written somewhere that it cannot be a unix utility for this very reason, but has to be a shell built-in. The syscall is a &
84.
by dapperdrake 5mo ago
Higher throughput increases the risk of high latency. Low latency increases the risk of "wasted cycles”, i.e. lowers (machine) throughput. Helps with human discovery throughput, though. The sled.rs people had a well readable take on t
85.
by dapperdrake 5mo ago
In short, NFS has a terrible data model and only pretends to be a file system.
86.
by dapperdrake 5mo ago
Accurate a.k.a. "correct" implementation of ACID needs a single (central) source of truth and temporal serializability (or something close to that). In practice this always "impacts" performance. If I understand it corre
87.
by dapperdrake 5mo ago
Facetious reply: > However, GNU software tends to work very hard to avoid arbitrary limits [1].
88.
by dapperdrake 5mo ago
First of all, thank you for presenting a succinct take on this viewpoint from the other side of the fence from where I am at. So how can I learn from this? (Asking very aggressively, especially for Internet writing, to make the contrast unm
89.
by dapperdrake 6mo ago
I thought it cheesy at the time. Then I tried clojure. "The value of values". Indeed. Q.e.d. No notes.
90.
by dapperdrake 6mo ago
Thank you for opening my mind to a viewpoint I didn’t even know existed. Yes, for many scenarios this is "not even an academic exercise". For a very select few applications this is Gold. Finally serious linear algebra crunch for

More ›