Hacker News Reader

Actually, that doesn't seem very sane to me. Why are we doing additional work for functionality that we already created, and losing support for people on older versions? Sure if you are a making a new app it makes sense to use great new features. It doesn't make sense to delete code that is working and redo it just because the new way is easier. 0 effort >>>> small effort times 10.

View on HN

When you introduce new people to the development team, less code means less issues.

Old code had nasty things like traversing the UIView hierarchy and removing unwanted UIViews.

Old code had deprecation warnings.

Old code is not optimized. Apple are doing a much better job at creating great working UIKit controls for us.

Any day that I delete code is a good day.

"It doesn't make sense to delete code that is working and redo it just because the new way is easier."

Less code to maintain >>> custom written code that might be prone to break on newer versions of the OS. It's definitely what I would do.

While I agree that less code is better, is it the highest ROI on your time compared to actually improving the app, or maybe making a new one? It might break in the future, it might not. What you change it to might break in the future too. Why not wait until it breaks to rip out and rewrite working code?

Reply on news.ycombinator.com