3 ms·
Working on a big existing codebase is a different scenario too, since adding in Swift either means rewriting the whole thing, or convincing two very different l
by mikeash 10y ago
Working on a big existing codebase is a different scenario too, since adding in Swift either means rewriting the whole thing, or convincing two very different languages to work together. And I imagine that's magnified for Apple's store code, which appears to have the unfortunate combination of receiving a metric buttload of traffic and being held together with baling twine and chewing gum.
I'd speculate that "not production ready" is at least partly rationalization or cover for "we really can't afford to screw around with this codebase, even though this is the company's Big New Thing."