ezekiel68

For sure. The original quote by Max Planck in his "Scientific Autobiography":

"A new scientific truth does not triumph by convincing its opponents and making them see the light, but rather because its opponents eventually die, and a new generation grows up that is familiar with it."

Admirers of this idea shortened it to, "Science progresses one funeral at a time."

The world got more benefit because it was kids like us who learned on these Commodore machines who rose in ranks in the tech world in the 1990s and laid the groundwork for products like the Palm Pilot, the iPod, and the iPhone.

You might be right but -- why would they have watied until these recent weeks?

I think the writing and the voice are both brilliant, in this case.

First movers rarely take the prize, though, do they? Les Paul and Mary Ford pioneered overdubbing voices back in the 1940s and 50s. The Beatles stole it from Buddy Holly. And Elton John from the Beatles.

If automatic scaling were free, this would be true...

So many things that could be said about this. For one -- I truly enjoyed the accidental repetition in the article that marked the effort as likely not aided too much by AI.

But I couldn't help, most of the way through it, to crystalize the respone, "How did we get the idea Tim Cook was chosen because he was likely to be much like Steve Jobs?" Honestly, having watched the Steve Jobs commencement address several times, I kept going back to his declaration that "Death is very likely the single best invention of Life. It is Life's change agent. It clears out the old to make way for the new."

No one must ever lose.

Or ever learn how to lose.

Argh -- perfectly read. I was thinking of Huawei.

"Let's isolate China's semiconductor industry," they said.

"This will all turn out well," they said.

Sure. Except that nobody ever does just stick to those elements.

> (Theme music)

I like this guy already.

Bona Fides: I learned c on with the K&R book on an Amiga (and transitioned to enterprise software engineering from there).

This seems like one more "When all you have is a hammer, everything looks like a nail" take. I agree with the other commenters who advocate for best-of-breed (e.g. Kafka, etc. for a message queue). PS I freakin love PostgreSQL as a relational (or even a time-series or OLAP) DB.

And I'm over here on SiliconFlow using Stepfun AI Step-3.5-Flash at $0.10/M input and $0.30/M output tokens (262K context window) for complex market analysis work in rust utilizing vectorized instruction sets. It provides me with amazing results.

I honestly wonder how long this calliope can keep playing before it crashes to the ground.

(I have no business relationship to anything mentioned here except as a regular retail customer who went bargain-hunting)

I tried it through siliconflow (I have no relationship to them other than as a normal customer) with the command line Pi agent and it's pretty good at adding features to a rust lang code repo. Compared to Deepseek V4 Pro there, M3 is about 3X the cost for non-cached input tokens and 5X the cost for output tokens. (both offering a 1M token context window). It certainly wasn't worh 5X the output of the Deepseek model for my uses, though.

I couldn't find any info on how they (siliconflow) quantized the model. I think some of the other ineference service aggregators might offer it as well, already.

I imagine the commenter was referring to the article title wrt satire.

Thanks for this!

Silence! Something something NPU at the edge hand-wave.

/s

For sure -- but these are the 'exceptions that prove the rule'. Someone else mentioned HTTP3 and QUIC. For all of these, there are thousands of projects (including multiplayer games and even enterprises) that didn't quite get it right and suffered for it.

Or, at least, so says the lore.

Well, not all killer drones run any kind of transformer model so...

Coming from the enterprise SQL world, I never took SQLite seriously for the very reason that field types were not enforced by default. (Yes, I was agog when it became the backbone for app metadata on smartphones.) Anyway, reading this reminds me of the old chestnut from networking about choosing UDP over TCP for its low-latency and simplicity and then eventually adding nearly all the reliability facilities of TCP to the app (automatic retry, etc) by hand.

> The cancel lands on a process that has never heard of the query, and nothing happens.

> Peering fixes this. The processes are aware of one another, so a cancel that lands on the wrong process is forwarded to the one that actually owns the session.

I understand "peering" as a concept here but have never tried this with PostgreSQL before. May I ask:

A) Does PostgreSQL have a mode/setting for peering that makes this easy? I'm imagining a mechanism that either goes round robin (re-sending the cancel to peers until it doesn't return an error of some kind) or some metadata in the cancel request that enables the wrong-destination process to somehow identify the proper process.

B) And by what mechanism? If all the PostgreSQL processes are listening to clients via so_reuseport, I guess there must be some other IPC method used for the peering chatter.

I'm sure all of this is "correct", but the fact is that many of us (myself included) enjoyed years of trouble-free service from our Commodore 1541 disk drives. And we could easily compare them with the Apple ][ computers and drives we learned on at high school

Thank you for helping remove my ignorance!

I had no trouble with it once I realized it wanted me to drag the border area.

You kind of covered this in your last point but it's worth emphasizing: we generally don't know for sure whether "correcting" a low serum vitamin D reading helps out in some way or merely silences a warning beacon that should have been traced to a more serious underlying condition.

Still, 170,000 - 1.2M years is a fairly short amount of time if we go back only to the common ancestor who begat progeny that would become Pan and Autralopithecus (around 12 million years ago). It could be that early hide wearers started a trend that, to this day, continues to interfere with natural vitamin D metabolism (while also providing many benefits).

If I'm not guilty until proven innocent, then neither is Motorola.

or

"How I Learned To Relax And Just Start New Sessions Often"

Lots of people throwing shade at Gemini CLI in the comments. I'm not saying it's perfect, but I enjoy using it. I haven't tried antigravity at all yet. I hope it will be an experience that is somewhat close to agentic coding on the CLI. I hit other model providers from Pi agent, but I'd like to be able to take advantage of my Google AI subscription on the CLI.