[fadzlan]

I think that depends on how good is the framework is architecturally sound in the beginning AND where you work.

I had a case where we had our own internal framework. Its okay. But the team turnover is quite bad to an already tight deadline that I had to re-explain everything every time a new dev comes in. That framework has no routing(its basically for multipage app) and guess what, if someone decide that they need routing, that guy is going to create his own, and there might be two of these guys, so then we have two ways of doing routing then.

And given the fact that this team has high turn over and tight deadline, I don't think you can say that it'd make a cohesive team, and the communication channel that everyone has is already overloaded (loads of meetings).

Sure, that may be a bad project to begin with, but that would be a different story.

In this case, at least for me, using a standard framework would be no brainer.