Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If you’re working on a reasonably sized project “without a framework”, and haven’t effectively built your own, I’m very skeptical of the engineering practices at play.


Not using a framework doesn't automatically imply everything is built from scratch. Maybe I prefer calling libraries, instead of plugging my code into a framework. I could also implement patterns using the batteries included features of the platform. For example Web Components on the frontend, or a REST API on the backend built using the standard Go "net/http" package


Maybe Vue and Svelte are different. But something like react is "just a library", right? So they must be greenspunning their own framework as well, by their own admission.

So then ask yourself the question - which underlying tech of your in house framework is going to be more stable, supported, have better tooling, and be easier to reason about. I'd pick the DOM every time.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: