Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think Python was too ingrained to pull a "Python 3"; Go is newer, and this could be more like a "Swift 3".

Break early and then stabilize for a long time; just make sure everybody knows the plan.



It's barely related to the topic, but another team in my company is thinking about rewriting a pretty large codebase in ObjC into something more sustainable. They briefly discussed Swift, but decided against it exactly due to its relatively frequent breaking changes.

Which emphasises even more the fact that large private codebases really dislike breaking changes.


Except that there should not be many breaking changes in Swift. Nothing on the scale Swift 2 -> Swift 3.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: