Top all-time · #20033
Mark Sands
Personal blog · marksands.github.ioprogramming
Mark Sands's personal blog at marksands.github.io covers programming. Since 2014, 3 different Hacker News readers have linked it 5 times, most often “How Apple Cheats”. The last post was in 2019, but the archive is still widely read.
Too few sampled comments (4) to say how often HN recommends it.?
Why HN links it
HN readers link Mark Sands's posts on Swift and Apple platform behaviour, especially subtle reference cycles. One commenter says his reference-cycle article opened their eyes to how subtle they can be.
Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Programming Tidbits
Most-linked posts?
- How Apple Cheats2 people · 2 mentions · first linked 2014-05-28
What Hacker News says?
one example is Popover controls on iPhone. http://marksands.github.io/2014/05/27/how-apple-cheats.html
Comment linking /2014/05/27/how-apple-cheats.html
on “Blizzard Exempt from iOS and MacOS Security Sandbox”Submitted How Apple Cheats as a story · 348 points
HN discussionI find it extremely dangerous if issues arise rarely but not rarely enough stop thinking about them and not as rarely as you would think. Look at this terrifying example from [1]. How long do you have to look at this code to tell if there is a reference cycle or not? class ServiceLayer { // ... private var task: URLSessionDataTask? func foo(url: URL) { task = URLSession.shared.dataTask(with: url) { data, response, e…
Comment linking /2018/05/15/an-exhaustive-look-at-memory-management-in-swift.html
on “Swift 5 Exclusivity Enforcement”I agree. Here's an article that has really opened my eyes on how subtle reference cycles can be: http://marksands.github.io/2018/05/15/an-exhaustive-look-at-... I have pasted the most egregious example here: https://news.ycombinator.com/item?id=21919728
Comment linking /2018/05/15/an-exhaustive-look-at-memory-management-in-swift.html
on “The Decade of Swift”>I don't understand your comment about reference counting being intrusive. It's intrusive because you can never really stop thinking about it if you want to write correct code. Here's an example from a very interesting article by Mark Sands [1]: How quickly can you tell whether or not this piece of code has a reference cycle? class ServiceLayer { // ... private var task: URLSessionDataTask? func foo(url: URL) { task…
Comment linking /2018/05/15/an-exhaustive-look-at-memory-management-in-swift.html
on “The Decade of Swift”