We keep track of EOL dates in our internal wiki with links to various websites. Would be nice to reduce the scatter and just link to this site!

Would you accept Pull Requests that add server hardware EOS and EOL dates? They are especially hard to find and it would be great to have them in there as well!

Edit: I should have taken a look at open issues first, it seems there is tracking issue for network equipment so I guess adding server hardware is certainly not off the table (https://github.com/endoflife-date/endoflife.date/issues/1387).

.NET Framework support is tied to Windows itself.

https://learn.microsoft.com/en-GB/lifecycle/faq/dotnet-frame...

One suggestion I hope you can look into: the Java world is a lot bigger than just Oracle Java, with multiple implementations where End-of-Life greatly differs. If possible, people avoid Oracle Java. Look up OpenJDK, Eclipse Temurin, Azul, IBM Semeru. There are some more, but I have never used them.

Do you have plans to monetize it? I hope not. Because this is a thing that should exist in the world. I would much rather support this via donations than ads or anything else.

Of course sometimes there isn't any because many small projects have no official support cycle, but sometimes projects of significance, and even some commercial products, don't either. But sometimes there is and it isn't well documented (or sufficiently linked so it is hard to find).

Would you consider adding a timeline-like view, for instance pages listing everything due to go EOL or move between support categories (current, still under standard support, extended (full LTS), extended (limited, i.e. security only or common packages only)) this/next month/quarter/year? Those pages could be static and refreshed daily rather than needing resource to generate on each visit (filtering could be done client-side to allow more flexibility without extra server resource for dynamic generation). This could be done by a 3rd-party, but that might involve scraping the API/site in a way that imparts an unfriendly amount of load (unless I'm missing something, the data in the release-data repo doesn't contain everything that would be needed for this).

It would be nice if these projects competed to get on the leaderboard.

I imagine the only help y'all need is for us to update EOL info when we see it?

Could there also be something like a comparison view of devices and models where you can see overlapped timelines when support ended (e.g. in the past vs now?)

Also, something like repairability scores from e.g. ifixit would be amazing to integrate.

Whenever I am looking for devices, I am also on the lookout for whether or not a third party OS has upstream support for it at the time of buying (e.g. LineageOS or postmarketOS wiki) because the device isn't "just a dead thing" when there's an OS available that you can flash on it.

- Would like a time line view: as of the next few months, what are expiring.

- Would like to see a stability score for a Product / Stack, you define the metrics for what is considered stable vs obsolete. How it compares with other similar categories.

The metric to track is probably “lifetime emissions”, which a few vendors report. The majority of these are actually from manufacturing and not lifetime, resulting in every upgrade becoming an emission spike(?)

Something like this? https://imgur.com/E0Wkxrt

I bought a perfect, will never deteriorate houseboat twenty years ago (it is now 2043) and moved it across the world. But now in the harbor of Hong Kong I won’t get a permit to stay there because there is (1) no onboard emergency manual in either Cantonese or Mandarin, and (2) it is not up to code for sustained quarantine due to the novel airborne virus that became a pandemic some years ago, and (3) there is no mounted non-lethal (because animal welfare) protection against a hull-eating[1] marina pest that migrated from the Equator ten years ago because of climate change.

Software obsolescence is all about the world changing around the software.

[1] The boat might be perfect but apparently creatures can still eat it if determined enough.

IMO it made a lot of sense when the hardware was changing rapidly - when the speed of new hardware doubled every year or two, maintaining existing hardware for more than a decade or two was often just a bad idea. And new hardware usually means porting or rewriting the software.

Nowadays though, hardware has largely peaked - CPUs are getting faster, but not that much faster. We won't see five doublings of CPU speed (64x increase) in our lifetimes, let alone in a decade. Security issues and repairability aside, today's hardware and operating systems will be perfectly serviceable in, say, 30 years.

Yes, I do think that is not enough. An OS should be thought of as scaffolding where parts of it are replaced but never the whole. And preferably while it is running, including all of the core.