4 ms·
that doesn't mean its because of the chosen framework. i would love to see actual breakdowns of productivity on a similar project performed by a single team, on
by robotkilla 12y ago
that doesn't mean its because of the chosen framework. i would love to see actual breakdowns of productivity on a similar project performed by a single team, once with angular once with Product B, by a dev team who is equally capable in Angular as they are Product B.
- aikah 12y agoThe difference between project A with angular and project A without angular is that project A team without angular would need to develop its own framework, its own coding style,conventions,... been there done that.
- robotkilla 12y agoI would just say "framework" instead of Angular. That said, it seems the real issues that frame works solve are those of teams who are unable or unwilling to establish their own set of coding standards and thus fall back on using some other team of dev's coding standards. I'm not saying that's a bad thing - I'm all for frameworks on the backend, and like I said above, I'm for (loose) frameworks on the frontend (backbone + underscore). I don't mind standards, but I'm against Angular becoming the standard because its not very good.