vsl

> they're a major indicator of AI writing.

For the illiterate, sure. Where do you think LLMs picked them up from?

Exactly. This is far better than your usual AI slop...

> I'm not sure where they buried that clause.

It’s cleverly hidden on the checkout page, right under the no-commitment plan…

https://www.adobe.com/creativecloud/plans.html#miniplans-buy...

How? Step 1 is kinda problematic for that, no?

> I just do not understand why people - even when actively denying LLM usage - use the fucking em dash.

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.

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.

Yes, in EU the Commission proposes legislation: https://commission.europa.eu/law/law-making-process/planning...

> In the article, it talks explicitly about this being driven by the heads of state.

Did you miss that the article talks explicitly about it being in the second reading already?

It wouldn’t occur to a Czech speaker to use caron standalone - it’s not an alphabet character on its own. It’s a combining Unicode code point.

Sound like it’s not about removal from keyboard but rather ability to enter standalone?

It’s a combining accent character. It’s used to alter other characters (e.g. “c” to “č”). It doesn’t make sense to use it standalone.

Apple probably fixed a bug and https://xkcd.com/1172/ followed.

Dropped Backblaze over this when I learned about it in December (https://mjtsai.com/blog/2025/12/19/backblaze-no-longer-backs...) and went to Arq. Not as polished, especially on Windows, but works and is actually cheaper.

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…

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.

Because GHA was stagnant and expensive and multiple services like https://www.warpbuild.com/ popped up, with better performance and much lower price. Looks like they ate enough of GH’s lunch…

Yeah, the joys of mass ignorance.

- Barely literate native English speakers not comprehending even minimally sophisticated grammatical constructs.

- Windows-centric people not understanding that you can trivially type em-dash (well, en-dash, but people don’t understand the difference either) on Mac by typing - twice.

> Why did they think this was a cyberattack and only after two hours realize it was the config file?

They explain that at some length in TFA.

The opposite actually: the market is growing, only Tesla sales are shrinking:

https://electrek.co/2025/09/25/tesla-tsla-down-22-europe-whi...

> Apple tells you why they rejected the app, and you correct the problem and resubmit.

Such as, elsewhere in this thread, app for viewing HealthKit data “unnecessarily using HealthKit”?

App Store rejections are arbitrary bullshit most of the time. We stopped shipping through MAS because of that and went direct-only, the 30% wasn’t even part of the decision; the bullshit and broken sandbox were.

Polish and decent UI...

Beta 3 walked it back and added frosting.

Beta 4 went back again.

As for being "sure" Apple will find the right balance, they never fixed usability regressions in macOS introduced in the last redesign. And they have ~10 weeks to fix all this.

That’s security though, not mere bugs.

...or in 2020 (the year of the article).

Give DeepL Writer a try.

Same. Large companies keep freeloading and ask for support. They buy a single personal license and share it among employees. And it’s not some small shops from poor countries, where you can understand it, it’s (often German) enterprises…

...and Wise support became utterly terrible a few years back. I mean "failing basic reading comprehension" terrible, the level of incompetence shown in this article is par for the course.

> Might be an EU thing, though.

So is Wise:

> All investment services are provided by Wise Assets Europe AS, incorporated in Estonia under registration number 16267372. Wise Assets Europe AS is authorised and regulated as an investment firm by the Estonian Financial Supervision and Resolution Authority under licence number 4.1-1/174. The registered address is Veerenni 24, 10135 Tallinn, Estonia.

But people treat them as if they could. You can already see them using LLM output as "proof" in discussions...

Major ones are enough. Linux and Darwin (that is, macOS and GNU userspace, really) differ sufficiently that you need to pay attention or limit yourself to POSIX. E.g. sed and wc burned me a few times with scripts that need to run on both.

> Hard to follow this argument, not sure which companies in Europe "won't have to play by the same rules"...

Nobody except Apple is required to make its new features available to competitors, from day one, no?

> I hope this works out, it's ultimately to the benefit of the consumer.

See iPhone mirroring on Mac: not available in EU. This was entirely rational choice by Apple given how small market EU is, and it's hard to see them handling any new deeply integrated features any differently.

See also how GDPR worked out: clicking through bazillions of obnoxious banners and an occasional 451 error on obscure US websites that can't be assed with this nonsense.

Thanks to overreaching EU bureaucrats, I will now also "benefit" by missing out on features that I would probably personally consider beneficial (just as do iPhone mirroring). Thanks I guess?