3 ms·

This is Angular 1.x course because Angular 2 is nowhere near stability. It also won't be for another few years - that's how long it takes to build an ecosystem

by fridek 12y ago

This is Angular 1.x course because Angular 2 is nowhere near stability. It also won't be for another few years - that's how long it takes to build an ecosystem of packages around anything. I'd say apart from people wanting to contribute to Angular 2, or maintaining packages that may need to be ported to Angular 2, nobody should learn it right now. The other two arguments are actually not in favor of the point you are trying to make. For beginner wanting to just have something awesome working, Angular is a perfect way of getting hooked. Sure, for senior JS developers learning Angular is perhaps not the best move - it is very isolated, built on assumptions suited mostly for small websites and, as you said it, "magic". Those are the reasons why Angular 2 is so different.

lobo_tuerto 12y ago
Not to rain on your parade but, would you call Google Cloud Platform's client-side a small site? What are your arguments for claiming that? https://www.youtube.com/watch?v=cVTN8msr5DE&list=PLOETEcp3DkCoNnlhE-7fovYvqwVPrRiY7&index=22 https://www.youtube.com/watch?v=cVTN8msr5DE&list=PLOETEcp3Dk...
- hippich 12y ago
  Is there place to look at actual product, without being paid client? I am looking right now at Console and it is indeed very simple app. I am desperately looking for indeed large projects made with angular 1.x because company I work for is in the middle of pretty large project where we stumble upon many angular shortcomings which I have no idea if even worth trying to search for solution.
  - lobo_tuerto 12y ago
    Have you watched the video I posted? In there they explain the magnitude of the site. And yes, it looks _simple_ that's the point. You don't want a bloated client, you architect a solution to only load what needs to be load. If your app is 25 MB you don't want to send ALL that to your client in one go. Watch the video please.
    - hippich 12y ago
      I watched video, it is just overview. We currently solving same problems and a bit more (we do heavy localization.) And unfortunately level of details provided in this video are not enough to see how specifically they e.g. load module, how they load module dynamically with angular, how they update routes and trigger these again, how they update dependencies in run time for already loaded and registered modules. This proved to be more complicated than it should have been and I am looking to see real app in action to view code and learn from it. Paying (or becoming trial user) is not part of what I want to do to learn from that :)) That's why I was asking where actual app I can touch resides, if it is possible to try it without submitting my credit card details :)
      - lobo_tuerto 12y ago
        Then the problem has nothing to do with AngularJS per se, but how you package and deliver a web app in general. You need to learn about asset management. Take a look at webpack for example: http://webpack.github.io/ http://webpack.github.io/ In the video they explain the strat behind how they managed to make a big app load only the necessary parts. With that, and some researching on your part should be enough to get you on the right track. In any case, your argument doesn't hold. It isn't only for small apps. ;)
        hippich 12y ago
        Believe me, this is problem with AngularJS (mostly because they invented modules/dependencies and decided to stick with it despite obvious deficiencies instead of teaming up with other open source projects and using something like require.js Strategy is easy part, as this stuff done many times already. The devil is in details about how to actually get into guts of angular's dependency and routing systems.
hippich 12y ago
I would say 'magic' argument is controversial. On one hand you want people get easy start, on the other hand, you might not... Don't know :) As for very-angular specifics - it was right there is course outline - directives/services/etc. This knowledge is unique to Angular 1.x (i.e. most of it will be irrelevant even for Angular 2.x)

by fridek 12y ago

lobo_tuerto 12y ago

Not to rain on your parade but, would you call Google Cloud Platform's client-side a small site? What are your arguments for claiming that? https://www.youtube.com/watch?v=cVTN8msr5DE&list=PLOETEcp3DkCoNnlhE-7fovYvqwVPrRiY7&index=22 https://www.youtube.com/watch?v=cVTN8msr5DE&list=PLOETEcp3Dk...

hippich 12y ago
Is there place to look at actual product, without being paid client? I am looking right now at Console and it is indeed very simple app. I am desperately looking for indeed large projects made with angular 1.x because company I work for is in the middle of pretty large project where we stumble upon many angular shortcomings which I have no idea if even worth trying to search for solution.
- lobo_tuerto 12y ago
  Have you watched the video I posted? In there they explain the magnitude of the site. And yes, it looks _simple_ that's the point. You don't want a bloated client, you architect a solution to only load what needs to be load. If your app is 25 MB you don't want to send ALL that to your client in one go. Watch the video please.
  - hippich 12y ago
    I watched video, it is just overview. We currently solving same problems and a bit more (we do heavy localization.) And unfortunately level of details provided in this video are not enough to see how specifically they e.g. load module, how they load module dynamically with angular, how they update routes and trigger these again, how they update dependencies in run time for already loaded and registered modules. This proved to be more complicated than it should have been and I am looking to see real app in action to view code and learn from it. Paying (or becoming trial user) is not part of what I want to do to learn from that :)) That's why I was asking where actual app I can touch resides, if it is possible to try it without submitting my credit card details :)
    - lobo_tuerto 12y ago
      Then the problem has nothing to do with AngularJS per se, but how you package and deliver a web app in general. You need to learn about asset management. Take a look at webpack for example: http://webpack.github.io/ http://webpack.github.io/ In the video they explain the strat behind how they managed to make a big app load only the necessary parts. With that, and some researching on your part should be enough to get you on the right track. In any case, your argument doesn't hold. It isn't only for small apps. ;)
      - hippich 12y ago
        Believe me, this is problem with AngularJS (mostly because they invented modules/dependencies and decided to stick with it despite obvious deficiencies instead of teaming up with other open source projects and using something like require.js Strategy is easy part, as this stuff done many times already. The devil is in details about how to actually get into guts of angular's dependency and routing systems.

hippich 12y ago

I would say 'magic' argument is controversial. On one hand you want people get easy start, on the other hand, you might not... Don't know :) As for very-angular specifics - it was right there is course outline - directives/services/etc. This knowledge is unique to Angular 1.x (i.e. most of it will be irrelevant even for Angular 2.x)