Hacker News new | past | comments | ask | show | jobs | submit login

I think the old way works well for a smaller scale app that doesn't need to change often. Otherwise, I find the components-based code reuse to be a pretty valuable pattern, especially when working as a team.



There's no reason at all why you can't also organise code into components under this model. Orthogonal concepts


Most (if not all) backend frameworks provide components these days.

See Laravel, Dotnet, Rails, etc.




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

Search: