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

OK, but that doesn't require any further changes to Mono. It should essentially be a read-only project going forward.


It won't get new features, but will likely require maintenance to keep it running as new versions of operating systems are released.


This is the thing about software: even if you aren't looking to improve it, the world around it will subtly shift so it'll need to be updated or it'll stop working.

For example, Windows XP can't access the modern internet because it doesn't support TLS 1.2 or 1.3 and most of the web is now secure. The software still exists, but the world around it has shifted so it doesn't really work. If 95% of people end up owning electric cars, gas stations are going to become scarce. Maybe there will be workarounds, but the world will have shifted around the product. Let's say that all gas pumps were changed to wider-nozzle pumps. Sure, you could make an adapter, but that's the point: changes in the world around you end up necessitating changes, workarounds, etc.

It might be mostly read-only, but there's always little possible things that come up requiring work to be done on it.


Is there anything to suggest that there will be further changes? I mean, other than bug fixes.


I’m surprised that such an old product would even get bug fixes. It’s not like Microsoft is fixing bugs in .NET Framework anymore.


.NET Framework isn't EOL and is probably going to be supported forever pretty much. There are still regular updates to .NET Framework distributed through Windows Update.


"Supported"... Kind of. Showstopper stuff is fixed. Other stuff is not. My last company had two open bugs with .Net Framework on more recent versions of Windows Server that were year and half old.

.Net Framework will be supported as long as Windows Servers OSes it runs on support it. If Windows Server team ever casts it out, it will die.




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

Search: