TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Ask HN: How do you know if a framework is worth sticking with?

2 pointsby zenNekoabout 2 months ago
What tools&#x2F;frameworks do you think will stay relevant in the future?<p>To avoid this question becoming a contested topic, I would like to clarify I got this question while looking at livescript&#x27;s syntax, wondering why it never took off and became a dead language. Then wasted time at reading online discussions on why elm is no longer active anymore, and the split of ReScript from ReasonML, I learned about how people who get used to functional programming based languages always feel like all other languages are cavemen&#x2F;primitive compared to its beauty. BASIC was a beginners learning tool to begin with, but why did pascal stopped being actively used?<p>I remember looking for a 3d renderer in 2018 or 2019 for a one off project, picked threejs but there was an overwhelming amount of choice of things to use, apart from unity engine and unreal most of those frameworks or engines are no longer even used anywhere (atleast in public repos), documentations take you to sold out domains (a github repo of docs could keep the tools usable atleast for tinkerers).<p>The kind of heights things like coffeescript and jquery were at one point compared to others is not even close to what we have now, which is good thing that we can design our things in a way that feels suitable to us, but If I have to port something that I wished to be something big, perhaps a decade long project, then it feels like a bad tooling choice from the start.<p>For my learning project, Alpine.js was great, but any typing mistake anywhere would break the whole thing without clear feedback, console.log was my only friend. Svelte&#x27;s component based system felt brilliant but vite kept showing blank page every 3-4 minutes with no errors anywhere, I had to keep guessing the mistakes, and rerun pnpm run dev too many times. I see that as a vite problem, although would need to test more with other things. So my question isn&#x27;t about vite (I am yet to understand that error), it&#x27;s about gathering some general opinions on how does one pick a stack (language&#x2F; framework&#x2F; tooling) for longetivity?<p>For those who have worked in the field for some time, what signs do you look for to see if a framework has staying power?

no comments

no comments