Indie-Resource.com

Hey guys

I've been browsing jobs as a web developer, since I'm almost finishing my degree in Computer Science.
Most of them require knowledge in HTML,CSS,JS,PHP (or ASP), jquery, some kind of framework and then there's AngularJS.

I've searched, and AngularJS looks really sweet and a good replacement for jquery. But, while learning, I like to have some kind of goal, and not just learning for learning, because without the practice you won't learn much right?
So, I ask, what can I aim to build (nothing too big) to learn angularJS, something angularJS is made for, like.. if it were Jquery I probably would say to create a fancy website with fancy fades and stuff xD

What do you think I should aim for?

Thanks

A little casino. Slots and blackjack.

Angular is a lot of fun.

Nice idea, it will be fun to code those type of games.

Do you know a good place to learn? Atm I'm following w3schools' tutorials, but if you have a better one I'll ditch it

anything is better than W3.

I think I used these and liked them

https://www.youtube.com/watch?v=LH0Z0U- ... J2heoDv9Hu

Wow
Thanks, I prefer videos so much, but I wasn't able to find any playlists though.

Thanks so much

Angular is designed to build Single Page Applications (SPAs). Basically, you will see things you typically thought of as server-side move to the client-side. You can have models, views, a routing engine, etc. The idea is extremely different from jQuery. jQuery is designed to simplify working with the DOM and other typical client-side tasks. Angular aims to move state from the server to the client-side, so your users will download one large app as one webpage, and then do pretty much everything without changing pages. Your server then becomes either a collection of REST web services, or perhaps even a websocket server, but the main business logic is not happening there anymore. Instead of requesting a page from the server and having the server render the HTML to display the page, your SPA will only require the data from web services to update the page with the newly acquired data. It is a fundamental shift in web development, and it is a shift that isn't right for all web applications. Apps that do the best as SPAs are typically some kind of CRUD (Create Read Update Delete) app that is displaying information from a back-end database for the user. Account management, some e-commerce, etc., all work well as SPAs. Also many apps that rely around newer HTML5 JS APIs for functionality (such as a multi-user canvas drawing app) work well as SPAs. However, some apps that rely on search engine ranking, or are already extremely complex even as a multi-page application don't work as well as SPAs (SPAs are more complex to build than traditional web apps).

Wow, very nice explanation as always

I've watched 13 of the videos halls shared, and I'm enjoying it, although I still wonder "what to do with this knowledge". I'm hoping that by the end of the playlist, and attempting to create what halls suggested ( a simple casino game ) I will figure it out.

Maybe the problem was in thinking from the start that it was a jQuery alternative, and not something different for other goals.

Like you said, Angular uses the MVC approach of doing things, and that's also why I'm struggling more, since I never used that approach like it should be used. (Maybe I never needed it?)