Top all-time · #12541
Crunchy Development
Personal blog · alisoftware.github.ioprogramming
Crunchy Development is a personal blog at alisoftware.github.io about programming. Since 2016, 6 different Hacker News readers have linked it 10 times. The last post was in 2021, but the archive is still widely read.
Too few sampled comments (3) to say how often HN recommends it.?
Why HN links it
Commenters link this blog's Swift pattern-matching posts when discussing Swift's destructuring syntax, such as 'if case let' and the variety of expression and control-flow forms. The comments cite the posts without judging the writing.
Summarised by Claude from a sample of 3 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Making your Swift code more fun 🎉, magical ✨ and crunchier 👌
What Hacker News says?
This is my personal gripe with Swift. Theres just so many different ways to form expressions and do control flow. It just feels like code golf to me. for case let (title?, kind) in mediaList.map({ ($0.title, $0.kind) }) where title.hasPrefix("Harry Potter") { print(" - [\(kind)] \(title)") } http://alisoftware.github.io/swift/pattern-matching/2016/05/...
Comment linking /swift/pattern-matching/2016/05/16/pattern-matching-4/
on “Why many developers still prefer Objective-C to Swift”Submitted Mixins over Inheritance (2015) as a story · 2 points
HN discussionSwift handles this exact problem quite elegantly with the "if case let" construct, allowing you to destructure sum types directly within an if statement. https://alisoftware.github.io/swift/pattern-matching/2016/05...
Comment linking /swift/pattern-matching/2016/05/16/pattern-matching-4/
on “Simpler UI Logic With Finite State Machines”Submitted Swift Pattern Matching: tuples, ranges and types as a story · 2 points
HN discussionI've read a ton of such blog posts recently in exploring this subject - seems like the tradition is as soon as you believe you understand the monad you must immediately write a blog post explaining it and pointing out why everyone else's metaphor is too complicated. This one is kind of nice in its succinctness, but that ends up meaning it doesn't explain why I should care or what I would do with my monad once I have…
Comment linking /swift/async/error/2016/02/06/async-errors/
on “Functors, Applicatives, and Monads in Plain English”Submitted Closures Capture Semantics, Part 1: Catch Them All as a story · 1 points
HN discussionSubmitted Overlooked announcements at WWDC'16 as a story · 1 points
HN discussionSubmitted Swift Pattern Matching: Custom pattern matching and syntactic sugar as a story · 1 points
HN discussionSubmitted Pattern Matching in Swift: switch, enums and where clauses as a story · 1 points
HN discussion