Live data from Hacker News

PaintCode 2.1 adds support for Swift

paintcodeapp.com

1–6 of 6 posts

Re: PaintCode 2.1 adds support for Swift

#4
"Our experience with Swift has been very positive so far - congratulations to Chris Lattner and his entire development team for this great work! "

Oh really? I mean, kudos to Chris...but the Swift compiler needs a ton of work. Filed about 10 radars to Apple last weekend while playing with a toy project.

Re: PaintCode 2.1 adds support for Swift

#5
post #4

"Our experience with Swift has been very positive so far - congratulations to Chris Lattner and his entire development team for this great work! " Oh really? I mean, kudos to Chris...but the Swift compiler needs a ton of work. Filed about 10 radars to Apple last weekend while playing with a toy project.

Was it heavily functional? I've found the compiler works great for regular OO stuff plus heavy use of closures.

Most of the reports of compiler problems seem to arise when people use more functional idioms.

Re: PaintCode 2.1 adds support for Swift

#6
post #5
post #4

"Our experience with Swift has been very positive so far - congratulations to Chris Lattner and his entire development team for this great work! " Oh really? I mean, kudos to Chris...but the Swift compiler needs a ton of work. Filed about 10 radars to Apple last weekend while playing with a toy project.

Was it heavily functional? I've found the compiler works great for regular OO stuff plus heavy use of closures. Most of the reports of compiler problems seem to arise when people use more functional idioms.

Yes, actually it is. I'm using filter.map.reduce quite a bit. I think there's issues with the performance of StringNSString (the bridge) too.