oasisaimlessly

أول أمسdiscuss

For things that need much more precusion than my lunch, ±1 second probably still isn't good enough, so they need another layer of correction anyway. Given that exists, might as well push leap seconds into that layer too.

oasisaimlessly

قبل 21 يومًاdiscuss

s/shit/shot/g

oasisaimlessly

الشهر الماضيdiscuss

Why use zvols? Aren't they essentially just single-file ZFS datasets (allowing e.g. independent snapshotting)?

oasisaimlessly

قبل شهرينdiscuss

OpenSCAD has almost zero crossover with B-rep modelling ('true' CAD, what this apparently is), though.

oasisaimlessly

قبل شهرينdiscuss

No, that is actually very rare, not typical. Do you have any examples of password managers that do that?

oasisaimlessly

قبل شهرينdiscuss

You dropped this: </sarcasm>

oasisaimlessly

قبل شهرينdiscuss

> Wrapping around is what happens when you decrement the minimum value of any integer type, including signed types.

No, signed wraparound is undefined behavior in C, whereas unsigneds are defined to wraparound. If you use -ftrapv, signed wraparound is an immediate abort().

oasisaimlessly

قبل شهرينdiscuss

> That's true for signed numbers too though? `int_min - 2 > int_min`

No, that's undefined behavior in C, and if you care about correctness, you run at least your testsuite in CI with -ftrapv so it turns into an abort().

oasisaimlessly

قبل شهرينdiscuss

MEMS oscillators do use a vacuum, and that's why they're susceptible to helium. A helium atom is tiny compared to an oxygen or nitrogen atom, and can leak through many otherwise-perfect seals.

So, a (badly-designed) MEMS oscillator is basically a region of vacuum enclosed by a membrane that only helium can permeate. Of course exposing it to helium is going to permanently change its behavior! Once the helium gets in, there's no reason for it to leave, due to the vastly higher atmospheric pressure outside.

oasisaimlessly

قبل شهرينdiscuss

You don't have to 'build' anything. Just spin up a GitLab docker container. Bonus: If you put it behind a VPN, you never have to worry about updating it.

oasisaimlessly

قبل 3 أشهرdiscuss

This is a very SWE-centric perspective. The very names of software/hardwsre would imply the exact opposite.

oasisaimlessly

قبل 3 أشهرdiscuss

What?

> Exactly, the application logic is the target. Actually doing seccomp bpf base but for managed bindings (Java, Node, Go, ...) add a lot of complexity....

Maybe proofread the slop before posting it next time?

oasisaimlessly

قبل 3 أشهرdiscuss

I'm an actual boss, and wasting a week is cause for a 30-minute post-mortem, not immediate termination.

oasisaimlessly

قبل 3 أشهرdiscuss

I don't think this is true. Modulo the sign bit, the "next float" operator is equivalent to the next bitstring or the integer++.

oasisaimlessly

قبل 3 أشهرdiscuss

I've never heard anybody (mis)attribute that to Apple.

oasisaimlessly

قبل 3 أشهرdiscuss

On the contrary, I would take this as evidence that these projects are alive and well - they have people who care enough to try to affect their future trajectory.

oasisaimlessly

قبل 3 أشهرdiscuss

> There's zero reason to replace your gloves when switching from dicing green peppers for a salad to picking up raw chicken.

Typo?

oasisaimlessly

قبل 4 أشهرdiscuss

It does, in combination with a pinned nixpkgs commit, which you can find like this:

    ~/repos/nixpkgs$ git log --grep='nodejs.* 24.14.0' -1 origin/master
    commit 9c0e2056b3c16190aafe67e4d29e530fc1f8c7c7
    Merge: d3a4e93b79c9 0873aea2d0da
    Date:   Tue Feb 24 16:53:40 2026 +0000
    
        nodejs_24: 24.13.1 -> 24.14.0 (#493691)
    ~/repos/nixpkgs$ nix eval nixpkgs/9c0e2056b3c16190aafe67e4d29e530fc1f8c7c7#nodejs_24.version
    "24.14.0"
    ~/repos/nixpkgs$

oasisaimlessly

قبل 5 أشهرdiscuss

I don't think it's abstract at all. Rub something sharp (anything from a stick to a phonograph needle) on an object and you'll directly transcribe its spatial frequency spectrum into an audio frequency spectrum.

oasisaimlessly

قبل 5 أشهرdiscuss

It's possible to fix this in application code with a Primitive<T> or NoDefault<T> wrapper that acts like a T, except doesn't have a default constructor. Use Primitive<int> wherever you'd use int that it matters (e.g. struct fields), and leaving it uninitialized will be a compiler error.

comments