jonathrg

Why were people so incredibly wordy back then?

It's not an optimization if it pessimizes almost all usage by adding a check for the dunder

The only other reasonable explanation would be that he has consumed so much LLM content that the machine has erased his voice and replaced it with its own.

Yes, that's the point where I was like "wait a second" and started counting em dashes. A third alternative, perhaps the LLMs were trained hard on his prior work? :-)

I wish they would just explain it in normal terms instead of this nasty LLM "engaging blog post" style

This is the key insight.

Worth flagging, real gap, transparent win, center of gravity... I'm tired boss

This feels like saying there are probably hundreds of stars in the universe

That's rude. Give them back

I thought the author might just be heavily influenced by the LLM style, but when there are also complete non sequiteurs like

> Low frequencies take very few bits to encode, and you feel them as much as hear them

yeah then it starts to smell pretty bad.

The diff of the linked commit in git is completely trivial, clearly it just got tagged because of the signoff in the commit message: https://github.com/git/git/commit/d7971544fe17378f44f4998301...

I would be surprised if there is no LLM-assisted code in there prior to this commit, this is just the first where the author chose to disclose it.

Several and a few are the same number, they only differ rhetorically.

Presumably there is an antialiasing low pass filter somewhere before JS gets to the data. I have a similar sample rate and it certainly didn't work at all for me.

What do you mean by cycles? A ripple-carry adder needs to wait for the carry bits to ripple through yes, but there's no clock cycle involved.

Good to know!

The JSON types are string, number, boolean, null, object and array. So how could the suggested code possibly work? Do you want JSON.parse to do arbitrary code execution like Python's pickle?

Bitbucket is okay to use, the main problem like with every Atlassian product is that it is dog slow.

How do you know what you were downvoted for?

Having a type safe generic ring buffer and such is nice

You definitely need discipline to use C++ in embedded. There are exactly 2 features that come to mind, which makes it worth it for me: 1) replacing complex macros or duplicated code with simple templates, and 2) RAII for critical sections or other kinds of locks.

I have no reason to trust that the fork itself is competently maintained when the author did not even bother to write the announcement.

But it is fine. If I disagree with a project's values I'm not going to contribute to it, and they wouldn't want me there either.

They explain why in their AI policy. It's an ethical stance. Of course they wouldn't notice if there aren't clear signs of LLM-ness, but that's not the main reason why they forbid it.

https://docs.postmarketos.org/policies-and-processes/develop...

It's fine for a project to have moral/ideological leanings, it's only weird if you insist that project teams should be entirely amoral.

Very happy to see PostmarketOS take an uncompromising stance and also providing justification for it.

Context: https://en.wikipedia.org/wiki/Loongson

And I better not see any capacitors on there remembering any charge!

Stuff like that is a good argument for using structured logging, but even if you are just parsing text logs, surely you can make the parser be a bit more specific when retrieving the log level.

Oh that makes sense.