4 ms·
Runtimes are different from languages. The C# language has never been rebooted and is fully backwards compatible, and there's no better example of long-term sup
by manigandham 8y ago
Runtimes are different from languages. The C# language has never been rebooted and is fully backwards compatible, and there's no better example of long-term support than Microsoft. You can still run apps from the MSDOS era, and even upgrade MSDOS through to Windows 10 if you have all the CDs today.
- pjmlp 8y agoRuntimes and languages go hand-in-hand, a runtime that doesn't support everything that one expects from the standard library breaks compatibility. Code starts getting full of #ifdefs Siverlight, .NET Core, WinRT, UWP just to give three reboots. No support for dynamic APIs, appdomains, IL generation on the fly, reflection APIs done in a different way, ... Actually C# is not fully backwards compatible, variables declared on foreach statements changed their semantics in C# 5. https://blogs.msdn.microsoft.com/ericlippert/2009/11/12/closing-over-the-loop-variable-considered-harmful/ https://blogs.msdn.microsoft.com/ericlippert/2009/11/12/clos... MS-DOS is only supported in 32 bit variants, a species in extinsion.
- general8bitso 8y agoSo, like DOS 3.3 to 5 to 6.2, and Windows 3 to 3.1, to 95 to 98 to 98SE, to ME, to XP, to 7, to 8 to 8.1, to 10? I think I was using floppies until Win 98?
- manigandham 8y agoHere's a 10 hour video from DOS to Win10: https://www.youtube.com/watch?v=l60HHWWo9z4 https://www.youtube.com/watch?v=l60HHWWo9z4
- int_19h 8y ago> The C# language has never been rebooted and is fully backwards compatible This is not true - there have been several breaking changes in C#-the-language since 1.0. For example: https://davefancher.com/2012/11/03/c-5-0-breaking-changes/ https://davefancher.com/2012/11/03/c-5-0-breaking-changes/