A Thinkpad doesn't have an End of Life. It just passes down from generation to generation.
End of Life of Technologies and Devices
61–70 of 81 posts
Re: End of Life of Technologies and Devices
#62Creator 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.
We already track almost all of them. https://endoflife.date/tags/java-distribution
We have to redirect the /java page here, but stalled by some housekeeping of separating the 2 Oracle JRE pages.
Re: End of Life of Technologies and Devices
#63Earlier quoted context omitted.
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.
Seconding this. As it stands, the Java page is only of very limited use.
Does this help: https://endoflife.date/tags/java-distribution
Re: End of Life of Technologies and Devices
#64Earlier quoted context omitted.
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 wi…
Fortigate is one such vendor we already cover, such information deserves to be free not behind login or paywalls.
Re: End of Life of Technologies and Devices
#65Very nice, I never heard of that site before. A possible addition, for hardware devices, could be a field reporting their environmental footprint, that is, how much waste is produced by simply marking a product as obsolete forcing users to ditch it instead of opening it so that it can be repurposed by the community by installing lighter OSes and apps, or reused in completely different contexts (example: old phone ->…
PRs welcome, although I think this is more suited to something like Wikidata. As I noted elsewhere, the lack of standard identifiers for devices makes this especially hard. Companies will often release the same hardware with different model numbers at different timelines and support cycles across different geographies.
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(?)
Re: End of Life of Technologies and Devices
#66I've recently updated the Lambda functions to Amazon Linux 2023, only to find that its standard support apparently expires earlier than that of the older Amazon Linux 2.
The lambda runtimes are separately documented: https://endoflife.date/aws-lambda
Re: End of Life of Technologies and Devices
#67Pretty nice to have this level of openness on a data set. In my dreamworld all the data would be in Wikidata.
Re: End of Life of Technologies and Devices
#68Earlier quoted context omitted.
Seconding this. As it stands, the Java page is only of very limited use.
Does this help: https://endoflife.date/tags/java-distribution
Yes, though it would be more helpful to have a comparison chart of the various (Open)JDK distributions, because for most purposes they are exchangeable, apart from the support terms.
Re: End of Life of Technologies and Devices
#69Earlier quoted context omitted.
> OpenCollective says that the total donations are $1,107.75 USD with 6 contributors. I threw another 20 bucks at them after reading that, but it seems like at least ads or something would make sense purely from a financial perspective, since even with 8M impressions, not that many are interested in donating sadly. What are the operational costs of running such a site?
Currently none, but that's mostly because we've worked hard to keep it that way. I publish finance updates on a GitHub Discussion ( https://github.com/endoflife-date/endoflife.date/discussions... ). We used to pay $9/mo for Netlify Analytics but didn't find it helpful. We're looking to join OpenEoX.org to standardize EoL information publication, but that requires a lot more funds ( https://github.com/endoflife-date/e…
> We want to make an API that does SBOM->EOL alerts for eg
You could consider making more expensive features paid options? Definitely tradeoffs there but it is an option, especially for business-useful features
Re: End of Life of Technologies and Devices
#70This nicely shows how insane the world is that we live in. There are many core pieces of technology on that site and almost all of them go EOL within 2 or 3 years. Anything that builds upon these pieces of technology will take some time to support the new version, so the time frame is actually even shorter.
Yea, some of these (e.g. PHP) have dozens of minor/bug fix releases which then just suddenly stop which just shows that you're vulnerable all the time... either because the release isn't "mature yet" or because it's "already eol" :)
Nothing ever gets "mature" in today's web development environment. As soon as something becomes stable, people don't find it exciting anymore so the devs need to introduce new features, create new bugs, and make backward-incompatible changes.
If you want to keep your sanity and focus on building an actual business on a solid foundation, ignore all the upstream EOLs and just use a major stable Linux distro that promises to backport security fixes for 5+ years. The peace of mind is totally worth the larger container size.