That EoX logo though.<p>Every organization or committee that designs a logo should be legally required to have at least one teenager on the board to prevent accidental goatse or other inadvertent blunders.
Htm. So, how does this compare, and/or is different from <a href="https://endoflife.date" rel="nofollow">https://endoflife.date</a>?
I think it will take a while for people to realize this effort looked great, but wasn't the right approach. Or no silver bullet, at least.<p>The presentation with a simple diagram that combines this data with an sbom to yield "information" gives me navel gazing vibes of UML being <i>the future of coding</i>.<p>Just as <i>architecture</i> didn't equate to well designed and maintainable software, I fear this initiative won't fix horribly outdated and vulnerable deployments. Software life cycle, deprecation, abandonment, supply chains are mostly a process problem, standards and technology won't fix that.
How does this relate to the OWASP/Ecma Common Lifecycle Enumeration Specification (<a href="https://tc54.org/cle/" rel="nofollow">https://tc54.org/cle/</a>)?
JEDEC has long maintained an EOL/EOS standard for semiconductors. This was a big part of a previous PM gig. Sounds boring, and it was. But having a process kept us out of serious hot water.