It would be awesome to have a simple API as well that can be curl'ed from a script. I think we could possibly make it work with the current Jekyll base by just rendering JSON in addition to HTML. I'm willing to give it a shot if that's something people would like (unless someone else wants to).
Show HN: Endoflife.date – Site with EOL dates of everything
21–30 of 83 posts
Re: Show HN: Endoflife.date – Site with EOL dates of everything
#22Really great idea, thank you! I can't believe I hadn't thought of this before. It would be awesome to have a simple API as well that can be curl'ed from a script. I think we could possibly make it work with the current Jekyll base by just rendering JSON in addition to HTML. I'm willing to give it a shot if that's something people would like (unless someone else wants to).
Will add it soon.
Re: Show HN: Endoflife.date – Site with EOL dates of everything
#23I recently did a rant on twitter[0] on how release/download pages of various languages/tools get it wrong, especially with respect to giving EoL Dates/policy and a list of supported releases. This is my attempt at solving the problem. If you have to every check the EoL date of anything, or if you have to verify that the version you have is supported, just visit endoflife.date/toolname. The website runs on Netlify, an…
If I add Fedora, Ruby, and a few other things will you accept the PR (assuming it's good of course. I just don't want to waste my time if you are already happy with the current list and don't want any more)?
There is a CONTRIBUTING file that details all the fields you can use.
Re: Show HN: Endoflife.date – Site with EOL dates of everything
#24but the link points back to the same page https://endoflife.date/python
There is a page on python.org for this, but I can never find it.
Re: Show HN: Endoflife.date – Site with EOL dates of everything
#25Earlier quoted context omitted.
The metadata isn’t hard to maintain (only the Latest Release field changes often). And I made this because the authoritative source are very often confusing with no clear dates. PHP supported release page is great for eg, but Python is a mess.
As a dev working primarily in PHP I hear all you're saying, but am mostly just enjoying the PHP > Python moment ;P That's good to hear, as I sort of said, my primary concern for EOLs is that they have been known to change over time and when they do I'd like to be sure the source I'm relying on is tracking those changes.
I don’t want to iframe it for sure (won’t even work for all sites).
I understand the pain point though. Maybe having a “Last Updated” date can provide a confidence estimate of sorts?
Re: Show HN: Endoflife.date – Site with EOL dates of everything
#26The RHEL page is mostly useless... it only has RHEL 8 which won't EOL for a while. What we really need are RHEL 6 and 7; 7 won't EOL for some time.
Now that I now, will give it a shot. Can I reach out to you for a review once the PR is up?
Re: Show HN: Endoflife.date – Site with EOL dates of everything
#27Is it just random but cached?
I think best might be release version order - it's correlated to EOL, but also shows how far behind you are if you have to look down.
Re: Show HN: Endoflife.date – Site with EOL dates of everything
#28> More Information is available on the Python website. but the link points back to the same page https://endoflife.date/python There is a page on python.org for this, but I can never find it.
Re: Show HN: Endoflife.date – Site with EOL dates of everything
#29The RHEL page is mostly useless... it only has RHEL 8 which won't EOL for a while. What we really need are RHEL 6 and 7; 7 won't EOL for some time.
I don’t use RHEL so I wasn’t sure what to include and what to exclude. (And the Release Policy is like 5 pages long). So I just left the image without the versions being covered. Now that I now, will give it a shot. Can I reach out to you for a review once the PR is up?
Re: Show HN: Endoflife.date – Site with EOL dates of everything
#30What's the sort order? It doesn't change on refresh, but e.g. Python has 4y, 2y, 7m, 1y, in that order, being 3.x, 3.x, 2.x, 3.x respectively. Is it just random but cached? I think best might be release version order - it's correlated to EOL, but also shows how far behind you are if you have to look down.
I like the release date suggestion, will implement.