Earlier quoted context omitted.
> It wasn't obvious at the time, but I think in retrospect the case can be made that Apple's ability to innovate effectively (both in terms of time and quality) died with Jobs. Oh stop. Apple's effectiveness was entirely a product of its time. You had designers building the Zune and calling it competitive but really there was no competition for the products Apple was building for a market that was screaming for a bet…
Apple only kept Java around because coming from Pascal and C++ background they were unsure how the Apple developer community would welcome Objective-C. When they saw the community had no issue embracing Objective-C that is when they dropped the Java bridge, QT for Java and eventually their own JVM. Chris Lattner never speaks about MacRuby on his interviews, rather how, like clang before it, Swift started as a side pr…
Re: Mail Data Loss in macOS 10.15
#131Yeah, but Objective-C 3.0 would have been a much better path than Swift. It would have allowed easier upgrading to existing code instead of mass rewrites, which always bring their own bugs (and that's ignoring the bugs in Swift itself).