3 ms·

Because framework that big takes months to understand and discover, a 2 week project is the same as a 'hello world' when it comes to gauging a framework. You'r

by pothibo 13y ago

Because framework that big takes months to understand and discover, a 2 week project is the same as a 'hello world' when it comes to gauging a framework. You're in the enlightenment phase. You start to understand some critical part of the framework and you feel giddy about it. However good angular.js is, your feeling right now is due to you wrapping your head around angular, not angular being awesome. I strongly think it's a dumb idea to jump around framework that does the same thing (1 project rails, another nodejs, another sinatra, etc.) Choose angular, or backbone, or ember and stick with it, you'll learn a lot more.

craigching 13y ago
> Choose angular, or backbone, or ember and stick with it, you'll learn a lot more. I agree that there is a problem of depth of learning of a framework (or any third party library that you use), but to suggest that you only learn one is not the best way to go about it either. As always in life, balance is a good thing. Sometimes learning another library/framework/whatever is a good way to learn about your current "one" library/framework/whatever.
- pothibo 13y ago
  It was meant as a general statement. I'm not advocating to stay with the same framework for your whole career. I'm advocating for having a deep understanding of a framework of your chosing before changing so you actually understand why you are changing. I believe we think the same thing.
nobleach 13y ago
I agree, I've written 4 apps with it and I really only feel like I'm scratching the surface.
AdrianRossouw 13y ago
I _know_ backbone. almost biblically, actually. I've been building backbone apps since early 2011 and have released more than half a dozen apps into production, including a few node knockout entries I would be able to build in a weekend. I also released my own open source framework built around backbone and marionette in a bid to standardise my team's stack and force us to use proper methodologies. i think ember is basically just backbone with a bunch of assumptions (i really hate working around other people's assumptions about my code). They are closer to each other than they are different. angular otoh is something completely different. I needed to build something achievable in it to understand how and why it differs from backbone. on a deeper level.

by pothibo 13y ago

craigching 13y ago

> Choose angular, or backbone, or ember and stick with it, you'll learn a lot more. I agree that there is a problem of depth of learning of a framework (or any third party library that you use), but to suggest that you only learn one is not the best way to go about it either. As always in life, balance is a good thing. Sometimes learning another library/framework/whatever is a good way to learn about your current "one" library/framework/whatever.

pothibo 13y ago
It was meant as a general statement. I'm not advocating to stay with the same framework for your whole career. I'm advocating for having a deep understanding of a framework of your chosing before changing so you actually understand why you are changing. I believe we think the same thing.

nobleach 13y ago

I agree, I've written 4 apps with it and I really only feel like I'm scratching the surface.

AdrianRossouw 13y ago

I _know_ backbone. almost biblically, actually. I've been building backbone apps since early 2011 and have released more than half a dozen apps into production, including a few node knockout entries I would be able to build in a weekend. I also released my own open source framework built around backbone and marionette in a bid to standardise my team's stack and force us to use proper methodologies. i think ember is basically just backbone with a bunch of assumptions (i really hate working around other people's assumptions about my code). They are closer to each other than they are different. angular otoh is something completely different. I needed to build something achievable in it to understand how and why it differs from backbone. on a deeper level.