Smaug123

26 ms·

421.
by Smaug123 3y ago
JetBrains Rider is really excellent until you start getting up to like the 30-project mark. Stdlib is very extensive although has a bunch of annoying quirks due to being like twenty years old and due to having Linux retrofitted onto it; I h
422.
by Smaug123 3y ago
AOT compilation is actually usable in net7, and I'm told it's got much better in net8 - massively reduces startup time (and in net8 apparently binary size too)!
423.
by Smaug123 3y ago
In fairness it is rather terrifying :P personally I pull all necessary information into some form of version-controlled storage, and then have a test to assert that the remote information is consistent with the stored version. Life's
424.
by Smaug123 3y ago
May I plug https://github.com/G-Research/ApiSurface/ ? It ensures this as part of your testing pipeline, and requires an appropriate minor or major SemVer bump if you alter the API in a non-breaking or breaking wa
425.
by Smaug123 3y ago
It's sort of postponing the actual work, though: there is indeed value in asserting that your code adheres to some domain model, but it's not entirely clear to me whether the value is outweighed by the friction when that arbitra
426.
by Smaug123 3y ago
(The "strangler pattern" can encompass this if you make an exception to the policy for the facade that hides the legacy code.)
427.
by Smaug123 3y ago
(facepalm, thanks - I have the right structures in my head but not the right words)
428.
by Smaug123 3y ago
Computers aren't magic, much as they seem to be. In general, if you can reproduce a bug reliably, it is always possible to keep digging until you find the cause. It may take more and more esoteric tools to do so, and you may need to
429.
by Smaug123 3y ago
That is what "low" means as a vulnerability severity! "Low" means "you totally don't need to do anything about this". The reported property does make the attacker's job slightly harder, after all, s
430.
by Smaug123 3y ago
The consequences were in fact catastrophic for SBF, so this surely can't be a demonstration that consequentialism is bad. If a magic oracle (that's always been right before) had told SBF that this was going to happen, he presumabl
431.
by Smaug123 3y ago
(And Nix derivations compose, whereas Dockerfiles entirely do not.)
432.
by Smaug123 3y ago
Ish. This is covered in section 6.4.1 of Eelco's thesis ( https://edolstra.github.io/pubs/phd-thesis.pdf ). It all becomes much simpler if evaluating a build many times can only ever result in one output, but the Ni
433.
by Smaug123 3y ago
Such standards do exist: https://slsa.dev/spec/v1.0/provenance
434.
by Smaug123 3y ago
Yeah, "who built this" information belongs in a signing certificate that accompanies the build artefact, not in the artefact itself. The Git hash can certainly appear in the binary (it's a reproducible part of the build input
435.
by Smaug123 3y ago
GCC respects SOURCE_DATE_EPOCH, and Nixpkgs has specific support for setting that environment variable: https://github.com/NixOS/nixpkgs/blob/92fdbd284c262f3e478033... (although I haven't proved that thi
436.
by Smaug123 3y ago
The bootstrap chain is https://github.com/oriansj/stage0-posix-x86/blob/e86bf7d304b...
437.
by Smaug123 3y ago
Loads of things. Obvious ones where the decision is explicitly taken to be non-reproducible include timestamps and authorship information. There are also other places where reproducibility is implicitly broken by default: e.g. many runtimes
438.
by Smaug123 3y ago
(As well as making sure you don't have actual matter blocking the view, you also want to avoid staining the bowels with something that could be mistaken for blood; so also don't drink red stuff.)
439.
by Smaug123 3y ago
For much much more on this, I'm most of the way through Google's book _Building Secure and Reliable Systems_, which is a proper textbook (not light reading). It's a pretty interesting book! A lot of what it says is just com
440.
by Smaug123 3y ago
(This is discussed in footnote 2 of the article.)
441.
by Smaug123 3y ago
Those ones are much easier to answer: they require very good coordination between each other. "Split-brain" is literally a canonical failure mode in the study of distributed systems, for example. (We kind of do have two brains, ri
442.
by Smaug123 3y ago
Oh nice - https://github.com/Millak/guix/blob/00747316ee0e1a7962ffe226...
443.
by Smaug123 3y ago
Relevant is https://github.com/NixOS/nixpkgs/pull/85542 , a (very stale) PR that uses mrustc to get straight to Rust 1.29 and then walks the chain.
444.
by Smaug123 3y ago
Same with the Go developers I know, which means it falls to me to raise the bugs against their stuff ;)
445.
by Smaug123 3y ago
Petition to replace the title with the more informative original, "Enhancing Self-Therapy with Internal Family Systems and AI". The article is very specifically about IFS!
446.
by Smaug123 3y ago
Specifically in languages with types and zero-cost abstractions . If it's not zero cost, then… there's a cost, which must be weighed.
447.
by Smaug123 3y ago
My point is that it's extremely common for people to go "this doesn't need to be documented", and then I come along as a user of the library and have to actually run the thing to determine its semantics.
448.
by Smaug123 3y ago
In a language without units of measure, `get_height` should be documented!
449.
by Smaug123 3y ago
SBF did have a very unusual discounting policy, namely "no discounting", in fairness. I'm not aware of anyone other than SBF who bites the "keep double-or-nothing a 51% probability gamble forever, for infinite expected
450.
by Smaug123 3y ago
Here's a very urgent but entirely unimportant task: buy a ticket for tonight's lottery.

More ›