3 ms·

Why isn't it currently ready for production use? ABI stability is the only real issue I can see now.

• mikeash 9y ago
  I'd say it's ready, but it's a bit iffy because of the tooling. The compiler is way too easy to crash, the debugger is often worse than useless, and larger projects can be extremely slow to build. You can put up with these, and I think it's worth the tradeoff, but you should definitely consider them carefully before putting a lot of effort into build a real-world Swift code base.
  • adamnemecek 9y ago
    > larger projects can be extremely slow to build Ironically this forced me to start using Swift Package Manager more and to split my projects into frameworks.
    • vlozko 9y ago
      Unfortunately, the rise of frameworks has led to another, often ignored problem: app startup time. Carthage and CocoaPods, while great tools, became enablers and I'm hoping static library support will be announced this WWDC.
      • adamnemecek 9y ago
        I dislike both Carthage and CocoaPods with passion. Fortunately SPM doesn't link dynamically.
        • orbitur 9y ago
          Too bad there's no package manager for ObjC libraries.
          • adamnemecek 9y ago
            Embrace the future and never look back.
• deleted 9y ago
  [deleted]