Tried Knockout.js, Mithril.js, Marko.js, Rocket (Rust), none to be found.
Also, the site seems to have abysmal performance.
"Is This Tech Dead?" A snarky autopsy engine for your dead frameworks
21–30 of 59 posts
Re: "Is This Tech Dead?" A snarky autopsy engine for your dead frameworks
#22You're calling frameworks with two day old commits critical and terminal? As Mark Twain would say, reports of my death have been greatly exaggerated.
As my tool is.
Re: "Is This Tech Dead?" A snarky autopsy engine for your dead frameworks
#23Pretty bad. Stack-overflow and hackernews metrics don't work, python is considered 100% dead and 70% dead respectively. By trying to search in the page with control-f.. I voted for death? Reddit and youtube are not remotely reasonable proxies for project health. Naturally no one likes wordpress, but it runs like 40% of sites on the internet, and it's also 40% "dead", which seems wrong. Why is there a newsletter? My advice is to throw away all the social media garbage, including hackernews sentiments, focus on github metrics for commits, issues, and forks.. see if you can add anything new there
Re: "Is This Tech Dead?" A snarky autopsy engine for your dead frameworks
#24Earlier quoted context omitted.
I'd say you'd have to be brain dead to say either are "almost dead". Sorry, you offered a poorly made peanut gallery to a poorly made peanut gallery, I couldn't resist.
It’s a Frankenstein made with duct tape and dead techs. The algo will evolve. It just needs more data
[deleted]
Re: "Is This Tech Dead?" A snarky autopsy engine for your dead frameworks
#25Looks like a cool project. That said, it doesn't pass the sniff test on the methodology- Something like 30% of the score is just related to bitching and instability. Imagine a crazy world where maintainers/owners do a good job on serving their community and building good tech... clearly a death sentence
That’s right. But isn’t it how techs are declared dead ?
I'd probably go with adoption & activity spent building, but given the conversation seems like there might be a "tongue in cheek" aspect to this project ;)
Re: "Is This Tech Dead?" A snarky autopsy engine for your dead frameworks
#26ASP.NET is endangered?
Re: "Is This Tech Dead?" A snarky autopsy engine for your dead frameworks
#27where OSGI?
Re: "Is This Tech Dead?" A snarky autopsy engine for your dead frameworks
#28The execution is a little iffy. Deno is nowhere close to being dead, and Elm is intentionally frozen for stability. The website also appears to be quite laggy, especially the dropdown menu for sorting. That being said, it's a really cool idea and I'm glad how open it is. This has the potential to become an authoritative and useful source for considering software stability and support.
I'd say Deno never got to be quite alive.
Node is the big player and Bun is the promising upstart from where I sit.
Re: "Is This Tech Dead?" A snarky autopsy engine for your dead frameworks
#29Pretty bad. Stack-overflow and hackernews metrics don't work, python is considered 100% dead and 70% dead respectively. By trying to search in the page with control-f.. I voted for death? Reddit and youtube are not remotely reasonable proxies for project health. Naturally no one likes wordpress, but it runs like 40% of sites on the internet, and it's also 40% "dead", which seems wrong. Why is there a newsletter? My a…
I'm sorry you had to learn about python this way.
Re: "Is This Tech Dead?" A snarky autopsy engine for your dead frameworks
#30Pretty bad. Stack-overflow and hackernews metrics don't work, python is considered 100% dead and 70% dead respectively. By trying to search in the page with control-f.. I voted for death? Reddit and youtube are not remotely reasonable proxies for project health. Naturally no one likes wordpress, but it runs like 40% of sites on the internet, and it's also 40% "dead", which seems wrong. Why is there a newsletter? My a…
It will definitely evolve. Feedbacks like this are important to improve the algorithm. You can see it now as a prototype. The project is 2 days old