6 ms·

All frameworks that start out as small tools are destined to become the thing that they hate if they ever get popular.

• nathan_long 13y ago
  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.)
  • noir_lord 13y ago
    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 ;).
  • coldtea 13y ago
    >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.
• dashoffset 13y ago
  Would you mind to give us an example?
  • coldtea 13y ago
    Rails. Now it's as bloated as the frameworks it used to mock for not being nible enough.
    • dashoffset 13y ago
      I disagree. I work daily with Java and Rails and Rails is nowhere near as bloated as the Java frameworks I have to work with.