I just do not comprehend how that can be the hill people choose to die on.
Like.. I get it. It's wrong. It feels wrong to give the AI nonsense just an inch and all.
But in the grand scheme of things, it's just highly ineffective dogmatism that makes people unheard, miserable and just further increases struggle.
Which people are free to do, in the same way that I am free to purposefully drop a massive hammer on my foot just to make some kind of statement.
Hurts me a lot, rest of the world stays entirely indifferent.
a) Using some other horizontal line is not in the class of "wrong" that would warrant this sort of reaction. You're debating the pixel count. Not the object. The aspect ratio of it.
b) If you're acting out of fear that's dumb, yes. If you however simply pick your battles for efficiency, that's not "the terrorists win". That's "you win" instead of "you loose due to attrition".
__
I've also consulted with the LLM regarding the "class of wrong" thing, because I thought it might be not quite clear.
So what I meant by that is that it's not giving up actual words or dumbing down your sentences.
Just swapping out a character that is practically indistiguishable for the untrained eye.
Hell, whole classes of social engineering attacks rely on that very property.
I know I know. "Wehret den Anfängen". Slippery slope.
But those are insane as a default reaction to everything.
___
I get it. SV sucks. HN sucks. The world sucks. Can't let it also take this little thing.
If it can take all the big things, then at least it won't take this tiny tidbit.
Emotionally, I get it.
But that's not how you make rational decisions. Nor is it how we would win.
Only times i've ever used the emdash was to signal sophistication. It's not like it makes the text any more understandable. Of course some people may have more practical reasons to use it, and there's nothing wrong with more or less conscious status signaling, it's probably unavoidable. But every status signal that's cheap to fake is going to get faked, and that's exactly what happened. Now you don't even have to know about its existence to use it, and in the effect it has shifted to signal low cultural capital. In a few years it will probably get RLHFed out of the default LLM tone. Next step is also already happening: people countersignaling by consciously still using it, showing that they can afford it, because they're unmistakably not pushing AI slop.
Thing is, you WILL encounter refusals with Sol doing anything remotely adjacent to security work. Which for Codex Security is kinda... problematic.
Just a few days back, I was reviewing some small bit of legacy DSA signature verification code, to get a sense of how safe it is to reuse - purely defensive, precautionary work and the context of it was there. But I simply wasn't able to use Codex Security: it threw refusal tantrums on every step of the way. Even the reasoning went like "nah, this is false positive, this is defensive code hardening, I'll nuke the subagent and tell it so" , followed by a refusal.
In the end, I was only able to do partial review with vanilla Codex w/o Codex Security.
yeah,
Sol failed to review my pr to my code of my app this way.
day after, my openai 200usd subscription down to 20usd one.
i started to use my 200usb subscription of google gemini a lot more.
got openrouter account and put 200usd here.
started to use glm.
> The member states want to reactivate the transitional regulation for voluntary monitoring of messages by technology groups, which expired on April 3, in an expedited procedure. The Council adopted a corresponding position for a “new” regulation on Thursday via written procedure to close a looming legal loophole and increase pressure on MEPs.
This is the EU Council pushing it. The elected heads of state of the member nations. The Commission just do their bidding.
The author is an unreliable narrator. The very first thing, the location of the script, can’t possibly be true (the app itself won’t be in per-user support data directory). They conflate things, they definitely don’t know enough about macOS to know to use sudo. I mean, they even rant about bog standard localization files…
Sadly, there are apps out there whose installers drop helper apps in ~/Library/Application Support. Or worse: Eve Online actually puts the whole game there. The Eve.app in /Applications (or wherever you choose to put it) is just the launcher/downloader.
You improve this skill by not using LLMs more and getting more experienced as a programmer yourself. Spotting problems during review comes from experience, from having learned the lessons, knowing the codebase and libraries used etc.
The LLM would, under that argument, be a transformative derivative work, which has important fair use implications (that don’t exist in the chardet case)…
> IMHO pluralization is a prime example, with an API that only cleanly handles the English case
That’s not true at all? Gettext is functionally limited to source code being English (or alike). It handles all translation languages just fine, and competently so.
What is doesn’t have is MessageFormat’s gender selectors (useful) or formatting (arguably not really, strays from translations to locales and is better solvable with placeholders and locale-aware formatting code).
> fully in the translator's hands.
That is a problem that gettext doesn’t suffer from. You can’t reasonably expect translators to write correct DSL expressions.
> Gettext is functionally limited to source code being English (or alike). It handles all translation languages just fine, and competently so.
The *ngettext() family of functions take two strings (typically singular/plural) and rely on a language-wide expression to choose the variant (possibly more than 2 variants). There's no good reason for taking two strings, this should be handled in the language file, even without a DSL. Ngettext handling a single countable makes some corner-cases awkward, like gendering a group with possibly mixed-gender elements. The Plural-Forms expression not being per-message means that for example even in English "none/one/many foo" has to be handled in code, and that a language with only a rare 3rd plural has to pay the complexity for all cases.
Arguably, those are all nitpicks, Gettext is adequate for most projects. But quality translations get cumbersome very quickly.
> You can’t reasonably expect translators to write correct DSL expressions.
This feels demeaning. Translators regularly have to check the source code, and often write templates, they're well able for a DSL like MessageFormat's, especially when it's always the same expressions for their language. It saves a trip to the bugtracker to get developers to massage their code into something translatable. You can't reasonably expect a English-speaking developer armed with ngettext to know (and prepare their code for) the subtleties of Gaelic numerals.
Because they are literate? Unlike the "em-dash means AI" illiterate crowd?
I'm not going to change my writing because some idiots who never read a novel or heard about typography think only AI does that.