Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

End of Life of Technologies and Devices

endoflife.date

Post reply on HN
Print view View original

71–80 of 81 posts

Re: End of Life of Technologies and Devices

#71

Post by teepo »

captn3m0 wrote: post #25
0x000042 wrote: post #21

Earlier 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…

This is a great idea. Hopefully this gets more attention and resources. You're really well positioned to fill a gap in the ecosystem.

Re: End of Life of Technologies and Devices

#72

Post by seeingnature »

captn3m0 wrote: 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...

I just want to say that I love this and have it bookmarked! I've moved into my 30s and am now thinking about life "maintenance first" and this will be a helpful resource for planning.

I imagine the only help y'all need is for us to update EOL info when we see it?

Re: End of Life of Technologies and Devices

#73

Post by kemotep »

jacquesm wrote: post #13
kemotep wrote: post #11

Earlier quoted context omitted.

In the case of operating systems, do you think 10 or so years of support is not enough? Brian Lunduke once talked about GNU/Hurd and said they should do the following release cycle: 1. Spend a few months working on it and then declare that the 1.0 release. 2. Spend 2-3 years getting Hurd to work on as many architectures and systems as possible. Get all graphics cards types that you can working. Release 2.0. 3. Spend…

> In the case of operating systems, do you think 10 or so years of support is not enough? Yes, I do think that is not enough. An OS should be thought of as scaffolding where parts of it are replaced but never the whole. And preferably while it is running , including all of the core.

In a way, rolling release linux distros meet your requirements.

Re: End of Life of Technologies and Devices

#74

Post by jacquesm »

kemotep wrote: post #73
jacquesm wrote: post #13

Earlier quoted context omitted.

> In the case of operating systems, do you think 10 or so years of support is not enough? Yes, I do think that is not enough. An OS should be thought of as scaffolding where parts of it are replaced but never the whole. And preferably while it is running , including all of the core.

In a way, rolling release linux distros meet your requirements.

Still reboots though, doesn't it?

Re: End of Life of Technologies and Devices

#75

Post by kemotep »

jacquesm wrote: post #74
kemotep wrote: post #73

Earlier quoted context omitted.

In a way, rolling release linux distros meet your requirements.

Still reboots though, doesn't it?

I know there are features to hotpatch the kernel, don’t know if that’s limited to Red Hat or Ubuntu or if something like Arch can do it too.

If individual packages or services have to restart does not qualify for your requirements then I don’t think any system could truly provide that without having it run multiple instances of each service/itself.

Re: End of Life of Technologies and Devices

#77

Post by royce »

captn3m0 wrote: 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...

Naively, would there be any value in providing an RSS feed of new adds, date changes, etc. ?

Re: End of Life of Technologies and Devices

#78

Post by jacquesm »

kemotep wrote: post #75
jacquesm wrote: post #74

Earlier quoted context omitted.

Still reboots though, doesn't it?

I know there are features to hotpatch the kernel, don’t know if that’s limited to Red Hat or Ubuntu or if something like Arch can do it too. If individual packages or services have to restart does not qualify for your requirements then I don’t think any system could truly provide that without having it run multiple instances of each service/itself.

I've used QnX and a home grown clone that could do this. In... 1991. Erlang can do it too.

Re: End of Life of Technologies and Devices

#79

Post by captn3m0 »

royce wrote: post #77
captn3m0 wrote: 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...

Naively, would there be any value in providing an RSS feed of new adds, date changes, etc. ?

New additions probably make sense.

Stock RSS feeds don’t work for future events, so they aren’t perfect for our usecase (warn users in advance of an upcoming date), so we offer ICS feeds instead.

RSS feed of just date changes might work, but ‘s hard to differentiate between a change that creates a feed notification vs one that doesn’t (new release, typo fix, date change by 2 days, and so on…)

Re: End of Life of Technologies and Devices

#80

Post by captn3m0 »

seeingnature wrote: post #72
captn3m0 wrote: 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...

I just want to say that I love this and have it bookmarked! I've moved into my 30s and am now thinking about life "maintenance first" and this will be a helpful resource for planning. I imagine the only help y'all need is for us to update EOL info when we see it?

Yes, great it like a Wiki. Additions of new products are also welcome, as is building tooling on our API or improving our release automation so we track releases better.
Post reply on HN