This is great! Thanks for building this!
Show HN: Endoflife.date – Site with EOL dates of everything
71–80 of 83 posts
Re: Show HN: Endoflife.date – Site with EOL dates of everything
#72Missing: EOL for 32-bit time_t is Jan. 19, 2038. https://en.m.wikipedia.org/wiki/Year_2038_problem
This also assumes you are using the current epoch. You could always be using a different epoch for that 32bit time.
Re: Show HN: Endoflife.date – Site with EOL dates of everything
#73I 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…
I want to suggest a side-wide search feature. The site is now pretty small, but when it become bigger, this feature will be very useful.
Thanks to the new theme I switched to, this is now implemented
Re: Show HN: Endoflife.date – Site with EOL dates of everything
#74Missing: EOL for 32-bit time_t is Jan. 19, 2038. https://en.m.wikipedia.org/wiki/Year_2038_problem
I think this would be quite redundant, until maybe 5-10 years from now. The 2038 is right there in the date, so not like anybody needs reminding.
Re: Show HN: Endoflife.date – Site with EOL dates of everything
#75Earlier quoted context omitted.
This made it even worse (everything was one line). I tried changing "Fedora Linux" to Fedora, and even that doesn't work. CSS!
That might be because everything isn't one line for myself. It's a bit of a hack, because HTML usually thinks it's fine to break a text cell on a space, and this prevents it. There's probably better solutions, like maybe converting spaces in title links to nbsp. It was just a quick hack that seemed to work for me. I obviously didn't test it on bigger screens. Whoops.
Switched to a different theme, and this is now fixed.
Re: Show HN: Endoflife.date – Site with EOL dates of everything
#76Earlier quoted context omitted.
I like it! It would be nice to have (you knew this was coming, yes?) an API, whereby one could programmatically request, say, https://endoflife.date/api/os/ubuntu/16.04 (Haven't thought through the semantics.) Digression alert. I've been thinking of a multi-OS package analysis database that I wish existed. The idea being, a database of information on packages to answer questions like: - Which packages of what OSes in…
THat'd be great, though there are many issues to handle: - packages don't have the same name across distributions: python or python2? python or python3? - most binaries don't have the same checksum (except scripts that aren't compiled: not many files) - paths tend to change across distriutions: usual Linux has /bin/bash, FreeBSD has /usr/local/bin/bash, NixOS has... something else. The closest I can think of are the…
There are a lot of fuzzy edges. One big one is managing different aspects of "sameness" for a file in different contexts that makes sense. You mentioned the problems with binary hashes; there are others, like comments in scripts and config files. If distro-X just spams boilerplate at the top of the config file, is that the "same" file? What if they add or rewrite informational comments in a config file?
I think the answer is that sometimes they are; it depends on the question.
I also noticed that it is really easy to end up wanting to pull data from source repos and bug trackers, but down that path lies madness.
Anyway, I don't have any plans to start building this. But it is an interesting project to think through.
Re: Show HN: Endoflife.date – Site with EOL dates of everything
#77Earlier quoted context omitted.
I wonder why they didn’t use the ` ` element for this. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/ti...
As far as I know, no browser actually does anything special with ` ` elements. Might be nice for screenreaders though, so I'll see if I can switch.
I don’t know if this has been done but I suppose a good use of the `` element would be for browser addons to target it and use the `datetime` attribute for something like “add to calendar (ical)” or “translate the text content to my locale” or something similar.
Re: Show HN: Endoflife.date – Site with EOL dates of everything
#78Earlier quoted context omitted.
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.
Yeah, if this was published in a API format upstream, might have been possible. 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?
Absolutely, yea. That would help quite a bit - or even a "Last verified" date.
Re: Show HN: Endoflife.date – Site with EOL dates of everything
#79Earlier quoted context omitted.
That might be because everything isn't one line for myself. It's a bit of a hack, because HTML usually thinks it's fine to break a text cell on a space, and this prevents it. There's probably better solutions, like maybe converting spaces in title links to nbsp. It was just a quick hack that seemed to work for me. I obviously didn't test it on bigger screens. Whoops.
Switched to a different theme, and this is now fixed.
Painless solution, I like it.
Re: Show HN: Endoflife.date – Site with EOL dates of everything
#80I repeatedly google this stuff en mass and thought a community-managed website would be a really great so thank you for saving me loads of effort! I'll be PR-ing a bunch of stuff to help out ;) It may be worth adding a per-version EOL cell, and potential caveats. Windows operating systems, for example, can receive paid support if you happen to have a billion dollars laying around. Edit: By per-version EOL cell, I mea…
My pet peeve is Python specifically. They have a PEP per release which basically tells you what all will become EOL on this release, which is very confusing. And they also list unsupported releases on the main download page. Can you clarify on the “release cell” part? Not sure what you mean by that. I get you on the Windows part. It took me quite some time to figure out what all is even possible. The Windows page def…
Sorry I'm not actually sure what they're called but for each release, list the date it was released in a .