How do I “think in AngularJS” if I have a jQuery background?

Suppose I’m familiar with developing client-side applications in jQuery, but now I’d like to start using AngularJS. Can you describe the paradigm shift that is necessary? Here are a few questions that might help you frame an answer:

How do I architect and design client-side web applications differently? What is the biggest difference?
What should I stop doing/using; what should I start doing/using instead?
Are there any server-side considerations/restrictions?
I’m not looking for a detailed comparison between jQuery and AngularJS.

1 Like

I’ve started paging loosely through an angular book (ORLY, Brad Green, Shyam Seshadri), where they show that you don’t manually put in event listeners, as we do with front-end JS. And the whole data-binding thing and the black-boxiness of “stuff just works for you without you needing to write it” sounds like I’d get pretty scared whenever something broke, since fixing black boxes is hard.

I think actually the book would be good, you can get it as an e-book or PDF, and it’s clearly written to devs who’ve used Javascript before but not in this new, client-side-processing way.

1 Like