News for hackers. Stuff that matters.
Re:Swift architecture at Uber by melling on Wednesday April 26, 2017 @08:53PM (#14208333)
Problems aside, Swift is the future of the Apple platform. It's a much less verbose language than Objective C. (no headers, type inference, no @, no ;)

https://h4labs.wordpress.com/2016/02/09/should-i-use-objecti...

Re:Swift architecture at Uber by anonred on Wednesday April 26, 2017 @09:02PM (#14208377)
It may be the future, and I love the syntax, but I've run into many of the same problems mentioned in the article (long compile times, SourceKit issues, increase in binary size, etc.) with my own smaller apps. It's honestly frustrating, sometimes more so than the eyesore that is ObjC.
Re:Swift architecture at Uber by melling on Wednesday April 26, 2017 @09:44PM (#14208571)
Uber and Facebook have large apps. Uber is 500,000 lines of Swift. This means someone is already working on these problems before you get there. The video had a lot of good advice. Hopefully, they'll contribute back to the Swift compiler too.
Re:Swift architecture at Uber by beaconstudios on Wednesday April 26, 2017 @08:55PM (#14208343)
my point is that a full switch-over is usually a terrible idea. I don't know if an incremental change-over from ObjC to Swift is possible in the Apple ecosystem, but if it is that's almost always the better option in my experience.
Re:Swift architecture at Uber by valuearb on Thursday April 27, 2017 @11:24AM (#14212168)
Swift is so far superior to Objective C that I switched permanently with version 1.2 three years ago. No more dangling pointers is huge, and worth the toolchain issues.