3 ms·
Same. I know that "naming is hard" but it seems like these days software people take a perverse delight in giving things completely unrelated names. At least ba
by taneq 8y ago
Same. I know that "naming is hard" but it seems like these days software people take a perverse delight in giving things completely unrelated names. At least back in the day we used impenetrable acronyms which kind of made sense when explained.
- saagarjha 8y agoThis is an internal code name for something that has not been publicly released.
- kkarakk 8y agoremember windows metro? marzipan is going the same route, whatever apple calls it later, marzipan is going to stick
- toasterlovin 8y agoMarzipan is not something that is public facing. It is an API for software developers. It will get a name at WWDC in a few weeks and then it will have about as much public awareness at UIKit.
- airstrike 8y agoAgreed. I understand unexpected brands for consumer facing products – Apple and Blackberry come to mind. But for a tool / library meant for developers, it seems a bit over the top.
- toasterlovin 8y agoIt is an internal code name.
- zapzupnz 8y agoApple has a precedent. The Carbon API was so named because "all lifeforms will be based on it". The Cocoa API was so named as an alternative to the Java API, at one point a major pillar for Mac OS X before Apple discovered people preferred to learn Carbon/Cocoa than bother with Java. Marzipan, if the name does stick, could be "the icing on the cake" that brings iOS developers to the Mac. It seems as though Apple has been spending the past twenty or so years preparing a small bakery. We patiently await for an updated version of discoveryd to be reintroduced into macOS, codename Tea-and-Biscuits.
- deleted 8y ago[deleted]