4 ms·
OS X, iOS, and all new APIs consumed by Swift on those platforms are written in Obj-C or C++, never in Swift. So what's "stagnant"? It's true that few others h
by mdhughes 9y ago
OS X, iOS, and all new APIs consumed by Swift on those platforms are written in Obj-C or C++, never in Swift. So what's "stagnant"?
It's true that few others have adopted Objective-C, GNU & MS occasional efforts aside. Which is why I keep a number of languages in practice.
But fragile, power-hungry, slow-compiling Swift isn't going to beat out stable Java, or easy JS or PHP on servers, and outside iOS/OS X, building desktop software needs UI toolkit support and stability.
Which is my point: Building in Swift is total technical debt.
- bsaul 9y agoi guess it all comes down to whether you believe swift is going to get better with time and solve its current issues ( the ones you mention),or if it's inherently a bad design. I'm betting on compilation speed and fragility improving a lot in the next two years. What matters to me is that the language type system is among the best ( enums and optionals) , and the general feeling when coding with the language is a real joy. For objc, however I've never been able to say anything better than "i got used to it".
- apple4ever 9y ago> Which is my point: Building in Swift is total technical debt. That's the truth. Swift makes it easy to build clever, unmaintainable code. The beauty of Objective-C is it is readable! And then easily maintainable.