The .NET framework to .Net Core migration broke a bunch. Similarly java 6 to 8, ... | Hacker News

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

		Macha 16 days ago \| parent \| context \| favorite \| on: Deprecate like you mean it The .NET framework to .Net Core migration broke a bunch. Similarly java 6 to 8, and when they introduced the new module system in Java 11 broke a bunch in another case. You’d still need to fixed that they swapped the string types, renamed a bunch of core APIs etc. in a statically typed python

anonymars 15 days ago [–]

Those are good examples. But python is dynamically typed -- indeed, python 3 is what I was alluding to

That being said, I think backwards compatibility comes down to project philosophy and foresight (e.g. https://learn.microsoft.com/en-us/dotnet/standard/design-gui...), not static versus dynamic typing

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