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

All projects written without frameworks are destined to re-implement framework-like features, but not as well, if they succeed.

(My statement isn't really ALWAYS true, but neither is yours.)



>All projects written without frameworks are destined to re-implement framework-like features, but not as well, if they succeed.

Of course they will implement framework-like features, that's inevitable. You'll still need routing, authentication, etc.

The win is that they'll implement them for their SPECIFIC use case, and only as much of them as they need, instead of having to accept the whole garbage that comes with a framework.

And you can cherry pick the best libraries for the cause, enging with even better ones that what any framework offers built-in.


I can't guarantee it is always true but I've yet to see a counter example on the code bases I've been exposed to.

It's almost like common problems have common solutions ;).




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

Search: