Live data from Hacker News

The Swift Programming Language

developer.apple.com

171–180 of 970 posts

Re: The Swift Programming Language

#172
post #93

It seems like the only way to view the programming language documentation is on iBooks on an iOS device? For a programming book, this is ridiculous. Edit: The latest version of OS X does support iBooks. Lets hope you have that.

Well, you can always just open it with a zip program (e.g. WinZip on Window) if you're desperate enough.

Re: The Swift Programming Language

#174
post #78

Earlier quoted context omitted.

Swift doesn't seem to have anything to do with the parallel language at swift-lang.org. In any case, reference counting is disastrous for the parallelism story. GC thread coming along and causing an additional cache miss is way better than having to do atomic operations on reference counts all the time.

Swift doesn't seem to have anything to do with the parallel language at swift-lang.org. Whoops. Should've corrected that when I copied the comment over. In any case, reference counting is disastrous for the parallelism story. GC thread coming along and causing an additional cache miss is way better than having to do atomic operations on reference counts all the time. Why are atomic reference counts necessary? You wou…

I'm not sure you can be Objective-C compatible without a shared heap. If you have a shared heap, you need atomic reference counting.

Re: The Swift Programming Language

#177
post #167

I'm impressed that it looks like they're turning Bret Victor's demo into a reality with playground. Check out his demo if you haven't: https://www.youtube.com/watch?v=PUv66718DII Really, really interested and excited about learning Swift.

[deleted]

Yes, it's funny that people didn't pick up on Apple potentially doing more with it when his demo made the rounds a few years back.

Re: The Swift Programming Language

#178
post #84

Still on an Objective-C runtime, so it's hard to see how the performance gains they claim are achievable, but otherwise having an interpreted version should be good for productivity.

maybe it is accompanied by improvements in LLVM? Or optimizations in LLVM that are more feasible with Swift (it has immutable values).
Post reply on HN