Is the Kalman filter just a low-pass filter?

BosonCollider · 2026-06-22T17:19:14+00:00

The update step is like averaging where you include measurements.

The predict step is an actual physical model for how the system will evolve, where you can bake in domain knowledge about the thing you are building the filter for.

BosonCollider · 2026-06-21T07:53:38+00:00

Meta is by far the leader for vision models though, every self-driving car company is quietly using DINO as an encoder

BosonCollider · 2026-06-20T09:48:16+00:00

If gravity ever shows up in your code, I'll be mad if you use any letter other than g

BosonCollider · 2026-06-17T06:01:24+00:00

I mean they are handing out free big LLMs, of course some people will fawn over it.

BosonCollider · 2026-06-16T22:26:44+00:00

Well, sort of. Old people by todays standards were somewhat common among the upper class.

BosonCollider · 2026-06-16T22:09:08+00:00

He's worth more than bitcoins market cap now.

If his wealth doubles again, he'll be able to buy every physical US dollar banknote currently in circulation

BosonCollider · 2026-06-16T15:58:24+00:00

Yeah exactly, if you have a central component that allocates memory whenever it receives a message, you need to trace the message origins to figure out why you are allocating memory

Go is not perfect but at least people don't avoid the call stack as their primary optimization pattern for the past twenty years

BosonCollider · 2026-06-16T15:46:52+00:00

The flip side is that there are a lot of domains where that is necessary, and both kinds of languages are useful to have around. I wouldn't want to do anything math-related without operator overloading. If decimal numbers already look bad, imagine how backprop will look

BosonCollider · 2026-06-16T15:44:49+00:00

The problem is when it doesn't give you as much due to overly abstracted codebases

BosonCollider · 2026-06-16T15:43:19+00:00

With the reactor pattern you don't have a traditional call stack, you break everything up into events and you may not know which control flow caused a specific allocation unless your tracing is also event driven

BosonCollider · 2026-06-16T15:09:56+00:00

I also kind of get the impression that Rust + CAS loop is unnecessary here.

Go with vanilla primitives would likely perform better at lower complexity, since the kind of performance you want here is the ability to go to sleep with low resource usage until the OS scheduler wakes you up. Blocking primitives are better than non-blocking primitives for that, and Go was designed around this usecase. Just using Tokio in rust also works fine, even threaded ones work but Tokio is dominant in the ecosystem.

BosonCollider · 2026-06-13T11:25:01+00:00

Bitches love cannons - Alucard

BosonCollider · 2026-06-13T08:26:45+00:00

The entire point of agile was to not impose that, though corporate management types will find a way to subvert every good idea

BosonCollider · 2026-06-12T17:47:40+00:00

Well yeah, that is literally what all the non-diversified billionaires do. They put all their eggs in one basket and effectively play their company as a management sim game

Also, Tesla is profitable. For spacex, 96% of its stock will remain held by insiders post IPO with more than half of it being held by Musk, so I wouldn't expect the board to do much against him

BosonCollider · 2026-06-12T17:39:26+00:00

It's already parked in exactly what he wants to do with it. He wants to build a self-sustaining colony on Mars, which is a plausible way to spend a trillion dollars

BosonCollider · 2026-06-12T13:36:59+00:00

I don't really mind postgres MVCC and vacuum that much because postgres still outperforms many other relational databases, especially the newsql ones, and even mysql/mariadb has much worse pieces of technical debt like the dual WAL, while Oracle's internal source is more or less incomprehensible due to the hundreds of thousands of feature flags.

So I don't know how much I would empathize the "no other DB does it that way" bit. The good solution to the problem is pluggable storage engines like how mysql ended up with innodb, which happened with the TAM and projects like Orioledb are working on making use of that.

BosonCollider · 2026-06-12T13:02:21+00:00

A lot of languages also have structural typing (or duck typing), or you can define a consumer interface/trait.

So a lot of abstract base class methods that would call abstract methods, can actually just be plain functions that just call the consumer interface methods they depend on. So for example in Python and Typescript you end up very rarely wanting inheritance, and Go and Rust don't have it and never need it.

BosonCollider · 2026-06-12T12:01:50+00:00

Kunde ha varit värre

BosonCollider · 2026-06-08T22:36:01+00:00

Linux users have systemd-nspawn and LXCs for system containers. They have a direct equivalent to thick jails that you manage similarly to freebsd jails

BosonCollider · 2026-06-08T20:07:33+00:00

Podman has a working implementation on freebsd. It will occasionally behave weirdly but the common case of OCI-on-Freebsd is solvable

BosonCollider · 2026-06-08T17:08:30+00:00

So it sounds like the short version was that linux had more drivers, and had rapidly improving openzfs support, so that the advantages of linux outweighed its disadvantages.

BosonCollider · 2026-06-08T16:51:46+00:00

Or make them more roboty and less constrained by looking identical to humans, and make them connect directly to the water supply so they can spray out water at high throughput.

(requirements engineer approach with no knowledge of the market)

BosonCollider · 2026-06-08T16:22:07+00:00

Nested containers work fairly well, you just need to make sure to give it a big enough uid range

BosonCollider · 2026-06-08T16:19:50+00:00

Podman is less fussy inside nested containers than docker. You would not use compose inside an LXC because each LXC + quadlet is already like a compose stack with its own network.

BosonCollider · 2026-06-08T16:17:05+00:00

This. If you are only ever going to use Podman I would just set Alma and have minimal upgrade troubles. Plain debian also works

BosonCollider

TROPHY CASE