Every morning I had to wakeup fast enough before the vibrating alarm would have it jump off my bedside table.

Of course the back cracked quickly with the constant falling. It eventually met its demise during a bike accident. I landed on a tiny rock that pushed through my pocket, exploded the glass, and ultimately broke the charging circuitry. You could see the hole through the front glass! And it was still playing music. At least until the battery died.

I have resorted to "0.0.0.0".

I want to be clear that losing (meta)data in flight during a power loss is expected. But a broken filesystem after that is definitely not acceptable.

Some postgresql db endedup soft corrupted. Postgresql could not replay its log because btrfs threw IO errors on fsync. That's just plain not acceptable.

Honestly the code of btrfs is a bit scary to read too. I have lost all trust in this filesystem.

Too bad because btrfs has pretty compelling features.

The difference is that they didn't have rebar. And so they built gravity stable structures. Heavy and costly as fuck.

A modern steel and concrete structure is much lighter and much cheaper to produce.

It does mean a nodern structure doesn't last as long but also the roman stuff we see is what survived the test of time, not what crumbled.

Their hypothesis was that maybe there was aj intention to have claude code fill the terminal history. And using potentially harzardous cursor manipulation.

In other words, readline vs ncurse.

I don't see python and ipython readline struggling as bad tho...

Peel the wrapping from one end; and just like that; you got a big butter stick-stick!

Is it time to model and 3D print a butter-stick stick-pusher? With a little battery and heating coil at the sticking out end. Getting a slightly soft and sticky enough butter out of the butter-stick-stick without it sticking to the stick? What a buttery sticky thought.

I recon the US electrical code for swimming pool allpows mains voltage as long as the conduit/cabling is certified for use in water (ie: watertight), properly grounded, and behind a GFCI.

And you can skip grounding/GFCI for anything below 24V.

For me its capslock as ctrl, super (windows key) for window management, altgr for layers, right side ctrl as compose key.

Ultimately you should read the code of rkyv_dyn to understand what it does instead of making random claims.

It will be faster for you to read the code than for me to attempt explaining how it works. Especially since you will most likely choose the least charitable interpretation of everything I say. There is very little code, it won't take long.

The length is first. The pointer second. The inline string is terminated with 0xFF. The length is 62 bits out of 64 bits such that a specific pattern is placed in the first byte that utf8 doesn't collide with.

I was a bit confused when you compared it to Python pickle and assumed you were talking about general input validation somehow.

I agree that pickle and similar are profoundly surprising and error prone. I struggle to find any reasonable reason one would want that.

As for the man in middle attack, I meant that if somebody intercepts the serialized form, they can mutate it. And without a cryptographic signature, you wouldn't know.

Trusting possibly malicious inputs is an universal problem.

Here is a simple example:

    echo "rm -rf /" > cmd
    sh cmd

The solution is to add a cryptographic signature to detect tempering.

This seems false after reading the book, the doc, and a cursory reading of the source code.

It is definitely independent of rust version. The code make use of repr(C) on struct (field order follows the source code) and every field gets its own alignment (making it independent from the C ABI alignment). The format is indeed portable. It is also versioned.

The schema of the user structs is in Rust code. You can make this work across languages, but that's a lot of work and code to support. And this project appears to be in Rust for Rust.

On a side note, I find the code really easy to understand and follow. In my not so humble opinion, it is carefully crafted for performance while being elegant.

You are supposed to guess the speed limit from the size and shape of the road too. When I ask, almost nobody knows what is the speed of a road, they just wing it.

By law the speed limit has to be posted before an automatic speed trap (they are everywhere in France). Essentially training everybody that speeds limits are only for avoiding the speed trap "tax", but don't matter otherwise.

On Thinkpad you can add the module later. It's a simple upgrade, open up the laptop and plug in the wwan module. The Thinkpad already comes with a sim tray. Though today presumably you would use an esim.

But hey you can pick a color for your macbook, so that's something.

Extra rant: the hardware quality of modern MacBook is fantastic. The keyboard sucks. The reflective screen sucks. The number of ports is ridiculously small. Soldered ssd and ram etc etc. Fantastic battery life. My thinkpad is a turd in comparison. But at least it doesn't bend when dropped. MacOS is horrible, Linux is the only thing I want. Sleep on modern PC is broken by design. A MacBook sleeping loses 1% of battery per day. A thinkpad loses 100%. Why can't we have nice things god dammit.