There's zero chance you have some secret sauce a motivated employer / your replacement couldn't figure out (using AI) if they wanted to fire you.

The GUI is pretty sharp, but I don’t like it uses emoji instead of SF symbols.

Is it Claude or Codex built?

I didn’t build it. The emoji were my idea. I (and Homebrew) have used them heavily before LLMs did. Maybe LLMs loving them is my fault. Sorry if so.

Have we pinned down the emdashes source yet? ;-P

I think it's because LLMs tend to obsessively write in a this-therefore-that kind of way, where an emdash is often the most semantically fitting punctuation.

Apple devices produce a ton of emdashes; "Smart Punctuation" is enabled by default on iOS and iPadOS, maybe Mac as well - and it's at least a decade old.

I've had to disable it on all my iDevices bc it breaks some Markdown parsers. How big a % of training data was produced on an Apple device? Ehhhhh probably small.

I don’t get these questions asking if it’s codex or Claude – I see them often. Does it matter? There are other options out there also, it feels strange to ask this. Like asking “is your car a Toyota or a BMW?“

If you say "AI tools", some vibe-coders try to equivocate between tools that generate the whole program for you and, like, an editor that uses an scoring algorithm to decide which method to show at the top of an autocomplete list. But if you say "vibe coding", some vibe-coders try to claim that what they're doing technically isn't vibe coding because they applied some non-zero amount of testing or review during the process.

If you ask "did you build this using Codex or Claude", it removes most of the wiggle room. And it's worded pretty neutrally, so it will often get vibe-coders who aren't technically using either of those tools to say something like, "Actually, I've built a custom harness for DeepSeek..." instead of an outright denial.

Long term it matters very much if your car is Toyota or BMW or Kia or John Deere though.

I think some users are also conscious about the longevity of their tooling related to LLM usage, too. Whether it has an effect or not, we've yet to find out.

My point was “why do you assume it’s one of the two”.

> 3. The aspect ratios were weird. I ended up using native app sizes, making the extra space kind of a waste

Ternus opened the Duo segment of the presentation talking about aspect ratio. Having the "right" aspect ratio drove the design for this more than anything else. It's something Apple really cares about (c.f. iPads and MacBooks)

Just you.

Good thing I don't live there.

> I'm excited that the Duo will get developers to actually design apps for foldables.

For Apple foldables yes. Not Android.

>Microsoft literally does not have a product like this.

Well yes their product like this is so old its already been discontinued. The Surface Duo targeted the same unfolded layout / passport sized folded device the iPhone Duo is, but opted for different folding methods and screen solutions.

Microsoft had one with a different folding method and screen, but it was equivalent to a product in which the key differentiators are the folding method and screen?

I wouldn't want to design the phone around an event that happens every 3 years at minimum.