Viewing profile — Diggsey

How does this packing/unpacking scheme compare to just using a lookup table?

You're getting confused between lifetimes (the static analysis that prevents use after free and similar errors) and lifecycles (more commonly discussed under the heading of ownersh…

Yes - I think the proof of the pudding will be whether they put in the effort to eliminate these unsafe blocks. The conversion to Rust is the starting point that makes this possibl…

1. Seems hard but doable (assuming there is some way to inject "inputs" into the build process, that can be recorded). However, I'm not sure exactly what you mean by a build here? …

> Yes, and the amount of study and knowledge required had a tendency to filter out people with the inclination to do such things. The Venn diagrams weren't completely empty, but th…

You would have had to run `jj edit` in order for this to happen, so I think it's a stretch to say you didn't ask for the edit? This is the main difference though: in git files can …

> git was originally implemented as a handful of low level binaries stitched together with shell scripts. A bunch of low level binaries stitched together with shell scripts is a lo…

Which works for about 5 minutes until someone leaks a manufacturer's private key or extracts it from a device...

Yes this stood out to me as well...

Stored procedures don't eliminate serialization anomalies unless they are run inside a transaction that is itself SERIALIZABLE. There's essentially no difference between putting th…

This is completely untrue. While the index only stores the hashes, the table itself stores the full value and postgres requires both the hash and the full value to match before rej…

It's also `position: fixed` which breaks all scroll optimizations and makes scrolling feel terrible.

There were two things I think went extremely poorly here: 1) Lack of validation of the configuration file. Rolling out a config file across the global network every 5 minutes is ex…

IMO, safety and "idiomatic-ness" of Rust code are two separate concerns, with the former being easier to automate. In most C code I've read, the lifetimes of pointers are not that …

I've found Gemini to be much better at completing tasks and following instructions. For example, let's say I want to extract all the questions from a word document and output them …

That would be because package version flexibility is an entirely orthogonal concept to lock files, and to conflate them shows a lack of understanding. pyproject.toml describes the …

Agree, but I think there is a point to be made here: Go as a language has more subtle runtime invariants that must be upheld compared to other languages, and this has led to a rela…

Essentially zero as a fraction of global concrete usage...

They are different: "0": ">=0.0.0, =0.9.0, =0.9.3, Notice how the the minimum bound changes while the upper bound is the same for all of them. The reason for this is that unless ot…

Within a crate graph, for any given major version of a crate (eg. D v1) only a single minor version can exist. So if B depends on D v1.x, and C depends on D v2.x, then two versions…

It doesn't link two versions of `rand-core`. That's not even possible with rust (you can only link two semver-incompatible versions of the same crate). And dependency specification…

No, sRGB refers to both a colour space and an encoding of that colour space. The encoding is non-linear to make best use of the 256 levels available per channel, but you were never…

Also, isn't the way browsers interpolate colors in sRGB just a bug that I assume is retained for backwards compatibility? sRGB is a logarithmic encoding, you were never supposed to…

> There will always be 2 sets of "primary" colors for a given eye: Additive and Subtractive. If your eye only has two types of cone cells then your additive and subtractive primari…

Documents don't contain calls to action like "Download X" or "Tell me more about Y", so your argument falls down in relation to the examples presented by W3C.