Apple's project codenamed "Marzipan" aims for apps that run on either platform. Thus the dividing line between MacOS and iOS becomes even grayer.

(Can a MacBook or Mac mini with an Arm processor or the iPad Pro becoming a MacBook model be far behind?)

If it's already been condemned, it will most likely run on neither platform.

@#$*^#$^ Spelling checker

I just don't get this "code named" thing.

"Omaha Beach" was code named for a pretty darn good reason, and, in fact, some poor guy who was unlucky enough to have used the word "Omaha" in a crossword puzzle at the wrong time came under heavy scrutiny.

But a code name for a something that's in no way a secret? Oxymoronic!

I imagine it's supposed to have some sort of effect, but I can't, for the life of me, imagine what it might be.

In a highly competitive industry such as computer and software development code names are on a par with military code names in war. While actual human lives are not at risk careers, big money, and perhaps even company survival are. Clues that might provide competition with an idea of a companies next innovation or product trajectory can be worth tens of millions even billions of dollars. Industrial espionage and counter-espionage are very real and the fact it goes on virtually unnoticed by the general public is a testament to the skill of the practitioners.

Therefore project "code names".

Of course, but I was really questioning Apple's sometimes gratuitous use of "code named".

In this instance


it's appropriate, but if my memory serves me, Apple has referred to versions of OS X/macOS as "code named (e.g.) Snow Leopard".

It sounds somehow pompous.

Most OS X versions have had Apple-internal code names different from the marketing name, so triple-named. https://www.imore.com/macos-version-code-names

Thanks for the link. (I prefer the wine names to the locations, although not the big cats.)

And all that for projects that weren't even secret...unless it was to enable employees to keep secret which projects they were working on.