throwaway219450
Joined 1 year ago
Joined 1 year ago
> and it was drawn to communicate messages powerfully both in the physical world and
.. in the ethereal?
You could at least compare to Notre Dame. It’s a bit tone deaf to draw comparison to Versailles, which was a vanity project to glorify the French monarchy.
You also don’t have to go straight into LLMs. You can learn most of the training mechanics via classic deep learning. It isn’t much different with LLMs except the training data and losses are specific and the models are much larger.
> Every mountain stands at its real height
> The Matterhorn is exactly as tall and as steep as the real one.
The models are RLd so hard to declare their own legitimacy. Everything has to be correct, genuine or real, no x, y or z.
But with a high res sensor, even flex in the PCB will invalidate the calibration. Only takes a few microns for a pixel to be in the wrong place.
Because stereo disparity (parallax) scales inversely with distance, conveniently you don’t need to search huge ranges. A point at infinity should have zero disparity in a calibrated stereo system. So normally you pick a depth range and search the corresponding pixels. Also if the cameras are calibrated, you only need to search horizontally so it works out to say 64 operations per pixel, which can be vectorized if the CPU supports it. Other approaches use more stable comparisons like census (is each pixel in the match window brighter than the central one) and hamming distance which is also very efficient.
And yes, stereo is sensitive to repeating texture but absence of texture like a blank wall is usually worse.
I don’t think it’s better. Any frontier LLM is capable of competent translation without significantly re-wording the text.
I use Whisper to transcribe foreign language videos and then run them through a couple of models to translate into English. It works really well, and much better than mechanical translation because they can figure out likely mistakes based on how whisper might have misheard (or surrounding context from the script).
I use black/ruff on a lot of projects and it will only touch standard-y things like docstring spacing, or spacing between methods and classes, import sorting etc. It doesn’t touch intentional/aesthetic user spacing. With agents it is helpful to make them run ruff and mypy to keep them honest, but as long as the code adheres to the spec, it doesn’t get changed. Astra also creates things like “report” functions with 10 arguments, so it’s useful to turn on complexity checkers as well.
I don’t see how Prettier is any better here unless you really want everything to be deterministic; how could it possibly know (always) when to insert a line? Aside from some more obvious cases like adding a gap before a loop declaration. Sometimes I group lines because they’re part of a mathematical formula or other operation and it makes sense to me, but Prettier doesn’t know that.
https://lucumr.pocoo.org/2026/9/7/astra-why/
EDIT: You can search for "tenobrus astra" on X, but link removed.
The generated code certainly does what's asked of it, but it's as sloppy as anything else I've seen. I don't think this benchmark can control for that. Maybe if it had a metric for minimum diff to satisfy the new requirement with the existing constraints on dead code etc?