Though, there's probably a reason they didn't go with this. Any ideas?
Also, not every navigation bar needed to have a red line.
// edit: "overriding drawRect:" should have read "overriding drawRect: in a category".
Re: not every navigation bar needing to have it, you could have a different UINavigationBar category in those VCs to not draw the red line, no?
And what happens if there is a second category somewhere in UIKit or elsewhere to override drawRect: on UINavigationBar?
And if you don't call the original implementation, who knows what will happen to your navbar's drawing in the future? Relying on undefined behavior and implementation details is bad.
To me, subclassing UINavigationBar (like I did in the blog post) and overriding layoutSubviews is a cleaner fix and doesn't rely on implementation details and runtime behavior.