What if I like magenta? Or brown?
2,435 karma · joined June 10, 2014
(Worked somewhat better for me than the classicreload version)
struct parser {
const char* s;
int pos;
struct grid* g;
};
struct parser {
const char *s, *p;
struct grid* g;
};
The old BBC Connections series has a segment with James Burke using the old census tabulators.
At least they managed to kill `auto_ptr`.
``` Before you start the delivery of accelerometer updates, specify an update frequency by assigning a value to the accelerometerUpdateInterval property. The maximum frequency at which you can request updates is hardware-dependent but is usually at least 100 Hz.
```
100Hz is way too slow. Presumably some devices go higher but according to the article the peak signal is in the 3kHz to 15kHz range.
And you just know that whatever they end up paying will be so tiny that it will just be seen as the cost of doing business. From a corporation's perspective it's always better to break the law and maybe pay a tiny fine (if you get caught and can't argue your way out of it) than it is to follow the law and miss out on profit/revenue/strategic advantage etc.
It's about how filesystems as they are (and have been for decades) are proving to be powerful tools for LLMs/agents.
TNC is "terminal node controller". They're kinda sorta like modems for radios. KISS TNC is a particular protocol for communication between a radio and a TNC.
My guess is that deer wouldn't be frightened by a drone but the sound is pretty annoying. Maybe it would be a good Pavlovian conditioning trigger to pair with some other deterrent.
Could you put sprinklers out there?
import zlib
input_text = b"I ordered three tacos with extra guacamole"
tacos = b"taco burrito tortilla salsa guacamole cilantro lime " * 50
taco_comp = zlib.compressobj(zdict=tacos)
print(len(taco_comp.compress(input_text) + taco_comp.flush()))
# prints 41
padel = b"racket court serve volley smash lob match game set " * 50
padel_comp = zlib.compressobj(zdict=padel)
print(len(padel_comp.compress(input_text) + padel_comp.flush()))
# prints 54As the author points out, the cheap quartz mechanism has no way of reporting the position of the hands (other than the hands themselves) and that you have to set the PULSETIME constant by the right number of milliseconds. If you're off by even a millisecond, that's going to accumulate quick enough that it would make a difference over even a single day, wouldn't it?
EDIT: as some have pointed out, the Lavet stepper theoretically accounts for this in that it steps exactly one tick after so many oscillations. That number of oscillations does not change so that's all you need to get right.
However, that basically just kicks the can down the road a bit in that if each step is not exactly 1/60th of a circle or bits wear down or get sticky or you have analog noise in there you will presumably still have a source of biased drift that you won't be able to detect. But maybe those affects are small enough that they don't matter for a wall clock.
""" “I’ve got just one question, Cliff,” he says, carving his way through the Eberhard-Faber. “Why is the sky blue?”
My mind is absolutely, profoundly blank. I have no idea. I look out the window at the sky with the primitive, uncomprehending wonder of a Neanderthal contemplating fire. I force myself to say something—anything. “Scattered light,” I reply. “Uh, yeah, scattered sunlight.”
“Could you be more specific?”
Well, words came from somewhere, out of some deep instinct of self-preservation. I babbled about the spectrum of sunlight, the upper atmosphere, and how light interacts with molecules of air.
“Could you be more specific?”
I’m describing how air molecules have dipole moments, the wave-particle duality of light, scribbling equations on the blackboard, and . . .
“Could you be more specific?”
An hour later, I’m sweating hard. His simple question—a five-year-old’s question—has drawn together oscillator theory, electricity and magnetism, thermodynamics, even quantum mechanics. Even in my miserable writhing, I admired the guy… """
Couple of observations:
- the page size drop down doesn't display any units (e.g. "6 x 9"). I assume there're all in inches but it would be a little more helpful if it said so and/or included a common name (e.g. US Letter) if one exists for that size.
- you might want to look into page imposition[1] something that's basically essential for any kind of stitched binding (as opposed to "perfect binding"). Full-blown imposition software is often ridiculously expensive and can have quite a few options so it's definitely both an engineering and UI challenge. In the meantime, Bookbinder JS[2] is a great site that I think runs entirely client side and can transform any PDF.
1: https://en.wikipedia.org/wiki/Imposition
2: https://momijizukamori.github.io/bookbinder-js/?paperSize=LE...
Hopefully, we'll have alternate means of power generation that nullify the dam's economic viability long before then but water supply and flood mitigation are other functions that need consideration. Silt will eventually destroy those functions as well however.
The stars themselves will move - relative to us - and eventually some of them will disappear but nothing much is expected on that front for much longer than 10ky timeframes.
""" I walked across the marble star map that traces a sidereal revolution of the equinox and fixes forever, the Reclamation man had told me, for all time and for all people who can read the stars, the date the dam was dedicated. The star map was, he had said, for when we were all gone and the dam was left. I had not though much of it when he said it, but I thought of it then, with the wind whining and the sun dropping behind a mesa with the finality of a sunset in space. Of course that was the image I had seen always, seen it without quite realizing what I saw, a dynamo finally free of man, splendid at last in its absolute isolation, transmitting power and releasing water to a world where no one is.
"""
Another interesting factoid about the catenary: Robert Hooke proved that it takes on the shape (though inverted) of the ideal arch, in terms of supporting loads above it. La Sagrada Familia in Barcelona is filled with them.
"For trivial relocatability, we found a showstopper bug that the group decided could not be fixed in time for C++26, so the strong consensus was to remove this feature from C++26."
[https://herbsutter.com/2025/11/10/trip-report-november-2025-...]
Seems that most of it's novelties were eventually added into LISP proper.
That tradeoff is fine for some things but not others. There's a reason why git et al require human intervention for merge conflicts.
The article is doing a classic bait-and-switch: start with a motivating example then dodge the original question without pointing out that CRDTs may be a very bad choice for collaborative editing. E.g. maybe it's bad for code and legalese but fine for company-issued blog posts.
Now you just need and Oculus and you can turn yourself into Johnny Mnemonic.