endoflife.date
exhibitor
endoflife.date | exhibitor | |
---|---|---|
43 | 6 | |
2,192 | 8 | |
2.8% | - | |
9.9 | 6.8 | |
3 days ago | 12 months ago | |
Ruby | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
endoflife.date
-
End of Life of Technologies and Devices
> 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.
-
understanding Rails version maintenance policy?
Here's the PR where it was added by a user, "Based on a Rails core team member's comment"...
-
Pragmatic Versioning – An Alternative to Semver
A lot of the communications regarding End of Life for Support is done very effectively here: https://endoflife.date/
-
Maybe helpful: https://endoflife.date
https://endoflife.date (not mine)
-
Central Hardware Firmware versions?
a little similar to endoflife.date if anyone has ever come across it for Software versions?
-
You can serve static data over HTTP
We do this at https://endoflife.date API, and it works quite well.
-
python-eol: A package to check whether the python version you're using is beyond/close to end of life
I've created the `db.json` with the [end of life](https://endoflife.date/) api.
-
Ask HN: Most interesting tech you built for just yourself?
Something I've recently worked on is building an SQLite database of all the dependencies my organisation uses, which makes it possible to write our own queries and reports. The tool is all Open Source (https://dmd.tanna.dev) and has a CLI as well as the SQLite data.
Ive used it to look for software that's out of date (via https://endoflife.date), to find vulnerablilities (via https://osv.dev) and get license information (via https://deps.dev)
It's been hugely useful for us understanding use of internal and external dependencies, and I wish I'd built it earlier in my career so I could've had it for other companies I've worked at!
-
Keeping up with EOS and EOL hardware and software
This is neat: https://endoflife.date/
-
Looking for a 3rd party library of EOL/EOS software support dates
I'm looking for a 3rd party vendor that can do the mindlessly tedious work of maintaining a library of software support dates. Think hundreds of thousands/millions of versions of software in an enterprise with ridiculous tech debt. Something like endoflife.date but much more far encompassing.
exhibitor
-
Ask HN: Most interesting tech you built for just yourself?
TL;DR: A React front-end component workshop, a simple version of Storybook.
So around 5 months ago, I needed a tool to preview front-end (React) components whilst I create them for a personal project of mine. There were two options: Storybook or Ladle.
Storybook is the tool everybody knows. I've used it before quite a lot. It's very big, full-fat, supports loads of use-cases, etc.
Ladle comes out of Uber. It's very small, lean, and doesn't support that much. After trying it out for a while, it just gives me a feeling like it's a 20% project to learn some new tech.
So I realised that I wanted something kind of in the middle. Something that's a bit more customizable than Ladle, but something much simpler and less intrusive than Storybook.
This led me to create Exhibitor (https://github.com/samhuk/exhibitor) (https://demo.exhibitor.dev).
I worked on it on-and-off for a couple months, and it ended up being something that I'm quite proud of. It's not perfect, and supports only a fraction of what Storybook does, however for a tool made by 1 engineer vs the 20+ for Storybook, I'm quite happy about it!
-
Show HN: Exhibitor – Snappy and delightful React component workshop
Exhibitor, a snappy & delightful React component workshop, is GA. My aim is for Exhibitor to be an extremely fast, easy to use, and delightful tool for creating front-end component libraries.
It's been around 2 months since my last mention and quite a tonne has changed.
Wiki: https://github.com/samhuk/exhibitor/wiki
-
Show HN: DriftDB is an open source WebSocket back end for real-time apps
Looks interesting. Coincidentally, I've just completed the bulk of work on a distributed Websocket network system to synchronize certain bits of state between multiple clients for my own kind of Storybook tool [0]. How interesting!
This kind of tool is exactly what I would have needed, instead of the approach I've taken which is a bit kludgy, grass-roots, novice-like, etc.
Good work :)
[0] https://github.com/samhuk/exhibitor/pull/22
-
Ask HN: What have you created that deserves a second chance on HN?
I was a bit deflated when my submission about https://github.com/samhuk/exhibitor fell through the HN floor-boards.
Think Storybook but simpler, faster, better Typescript support, and uses esbuild by default.
...Is the aim. I'm the sole lead dev working on it at the moment up against the ~10-20 strong team who built most of Storybook, so it's a long road ahead, but it's growing into something I'm quite proud of and happy about.
- Show HN: Exhibitor – Snappy, no-fuss, delightful React component workshop
What are some alternatives?
WordOps - Install and manage a high performance WordPress stack with a few keystrokes
epub2tts - Turn an epub or text file into an audiobook
django-DefectDojo - DevSecOps, ASPM, Vulnerability Management. All on one platform.
MLVPN - Multi-link VPN (ADSL/SDSL/xDSL/Network aggregation / bonding)
xeol - A scanner for end-of-life (EOL) software and dependencies in container images, filesystems, and SBOMs
scheme-for-max - Max/MSP external for scripting and live coding Max with s7 Scheme Lisp
radiofeed-app - Simple podcast aggregator
mqtt-to-kafka-bridge - Move your messages from MQTT to Apache Kafka in real-time :rocket:
public-iperf3-servers - A list of public iPerf3 servers...
brethap
digraph - Organize the world
ratarmount - Access large archives as a filesystem efficiently, e.g., TAR, RAR, ZIP, GZ, BZ2, XZ, ZSTD archives