Live data from Hacker News

End of Life of Technologies and Devices

endoflife.date

31–40 of 81 posts

Re: End of Life of Technologies and Devices

#31
post #30
post #2

Creator here, happy to answer any questions about what it takes to build a collaborative Wiki for tracking support life cycles. You can support our work on GitHub Sponsors or https://opencollective.com/endoflife-date We recently crossed 8M impressions via Google Search this month: https://github.com/endoflife-date/endoflife.date/discussions...

Thank you for making 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.

We have an open issue for a timeline view: https://github.com/endoflife-date/endoflife.date/issues/2148

Second is very subjective. If there's onething that I've learnt over the years working on this - it is that the definition of "support" is very fuzzy. You can't even compare what "LTS" means between different stacks/products, so it is hard to objectively rate anything. It still might be worth doing some analysis and publishing as a blog post though, but i'm not sure if it can be automatically calculated.

Re: End of Life of Technologies and Devices

#32
post #2

Creator here, happy to answer any questions about what it takes to build a collaborative Wiki for tracking support life cycles. You can support our work on GitHub Sponsors or https://opencollective.com/endoflife-date We recently crossed 8M impressions via Google Search this month: https://github.com/endoflife-date/endoflife.date/discussions...

This is an amazing project!

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.

Re: End of Life of Technologies and Devices

#33
post #2

Creator here, happy to answer any questions about what it takes to build a collaborative Wiki for tracking support life cycles. You can support our work on GitHub Sponsors or https://opencollective.com/endoflife-date We recently crossed 8M impressions via Google Search this month: https://github.com/endoflife-date/endoflife.date/discussions...

Could be a very useful resource. There have been a couple of occasions when I've found it harder than it should be to find EOL information.

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).

Re: End of Life of Technologies and Devices

#34
post #2

Creator here, happy to answer any questions about what it takes to build a collaborative Wiki for tracking support life cycles. You can support our work on GitHub Sponsors or https://opencollective.com/endoflife-date We recently crossed 8M impressions via Google Search this month: https://github.com/endoflife-date/endoflife.date/discussions...

Thank you for creating this.

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).

Re: End of Life of Technologies and Devices

#35
post #2

Creator here, happy to answer any questions about what it takes to build a collaborative Wiki for tracking support life cycles. You can support our work on GitHub Sponsors or https://opencollective.com/endoflife-date We recently crossed 8M impressions via Google Search this month: https://github.com/endoflife-date/endoflife.date/discussions...

This is an amazing project! 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 buy…

> where you can see overlapped timelines when support ended

I tried to generate a visual timeline for a given page (https://github.com/endoflife-date/endoflife.date/pull/2859, has some screenshots), but it was limited to a single page (so you'd only see nokia devices at once for eg).

It turned out that it is too hard to generate clear charts with vague data. We often only know whether is device is supported or not (true/false, see comments about samsung below in this thread), and don't have clear release dates.

I'll get to it someday (PRs welcome), but it might not work for the usecase we want (picking phones) because data on mobiles is very vague.

repairability score -> sounds interesting, will file an issue and see. The hard part is that there's no clear identifiers for devices (SWID/CPE are just not good enough) for us to track this kind of data from elsewhere easily.

Re: End of Life of Technologies and Devices

#36
post #2

Creator here, happy to answer any questions about what it takes to build a collaborative Wiki for tracking support life cycles. You can support our work on GitHub Sponsors or https://opencollective.com/endoflife-date We recently crossed 8M impressions via Google Search this month: https://github.com/endoflife-date/endoflife.date/discussions...

Could be a very useful resource. There have been a couple of occasions when I've found it harder than it should be to find EOL information. 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 fi…

Yes, we have an open issue for such timelines (https://github.com/endoflife-date/endoflife.date/issues/2148). Your comment has given me the idea to implement it on our "tag" pages, so you could see the timeline for all java-runtimes in one place for eg.

Generating pages isn't hard for us. We maintain it in our frontmatter/yaml (See https://github.com/endoflife-date/endoflife.date/blob/master... for example). The release-data repo is for tracking new releases of upstream products so we can patch the latest version automatically, and get notified of new major releases that are missing in our tables. release-data is a much smaller subset of our data, and doesn't include the critical EOL data.

Re: End of Life of Technologies and Devices

#37
post #2

Creator here, happy to answer any questions about what it takes to build a collaborative Wiki for tracking support life cycles. You can support our work on GitHub Sponsors or https://opencollective.com/endoflife-date We recently crossed 8M impressions via Google Search this month: https://github.com/endoflife-date/endoflife.date/discussions...

Could be a very useful resource. There have been a couple of occasions when I've found it harder than it should be to find EOL information. 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 fi…

In the case of commercial products it is especially frustrating if you need to log in to some customer portal in order to find such basic product information. And even if you create an account and log in it is not guaranteed to find this information. I can relate to a certain extend as some companies might not even know when they plan to end support for a product, but even this is information that is worth sharing with their customers.

Re: End of Life of Technologies and Devices

#39
post #16

why is the sidebar not on the side, so frustrating to use

Sorry, can you clarify - you'd like the site to take full-width and the sidebar to be left-aligned? Something like this? https://imgur.com/E0Wkxrt

I’m not GP but my problem with the sidebar is, at least on iPadOS, it does not scroll to match the page on the screen. Most times it scrolls the sidebar way too far and I can’t quickly flip through two or three similarly named pages. For example, I was trying to look at both Microsoft .NET pages.

Re: End of Life of Technologies and Devices

#40
post #2

Creator here, happy to answer any questions about what it takes to build a collaborative Wiki for tracking support life cycles. You can support our work on GitHub Sponsors or https://opencollective.com/endoflife-date We recently crossed 8M impressions via Google Search this month: https://github.com/endoflife-date/endoflife.date/discussions...

Thanks for the site. It answered a question I had in the back of my mind, but hadn't found the time to look up.

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.

Post reply on HN