6 ms·

A lot of things aren't correct in the article Rxjs isn't a drop in replacement for promise. Rxjs is about stream, promise is just a way to avoid callback hell.

A lot of things aren't correct in the article Rxjs isn't a drop in replacement for promise. Rxjs is about stream, promise is just a way to avoid callback hell. Promise can be replaced by rxjs but not the other way around You don't break the promise of being cross platform by using local storage if you do it the angular way. I'm to lazy to keep going ...

jaimex2 10y ago
I stopped reading after "I used it for two weeks"
- flukus 10y ago
  Two weeks should be plenty of time to put something through it's paces and do a thorough evaluation.
  - heisenbit 10y ago
    > The home of a peculiarly minded 21! year old web developer This developer was dropped into a larger project. He caught up with Angular 2 and TypeScript. He wrote an elaborate post. But maybe he had not been exposed to a larger set of diverse use cases and software patterns in practice yet. There are some learning hurdles to Angular 2 but imho. they are lower than what was there with Angular 1. Documentation could be better of course. Moving from 1 to 2 requires a bit of unlearning, it is essentially a new framework.
    - Udik 10y ago
      > There are some learning hurdles to Angular 2 but imho. they are lower than what was there with Angular 1 I really don't understand how people can claim this. I got my first basic application running in angular 1 in about two hours- no, I'm not talking about a tutorial but a small, real application. All you had to do to start was to include the minified angular framework in the page and write some plain javascript functions. That's it. Now, I've been working with angular 2 for the past month or so (on a brand new application). I still have very little understanding of what the framework does or how it works. I found it pretty easy to understand the basic concepts and inner working of angular 1, but I still haven't managed to grasp what angular 2 actually does. Some things seem to work, some others just don't. The documentation is obscure and lacking. The requests for basic features or bug fixes have discussion trails that go from many months ago up to yesterday. I just googled for the first example that comes to my mind- a pretty fundamental question: what's the execution order of directives in angular 2 and how to influence it? On the first page of results, only the first two are relevant (thanks Google!). Both are StackOverflow questions, and the answers are: >As far as I know the order of execution is undefined. You shouldn't depend on a specific order. >> That's just awful.. ---- > I think priority concept is yet not there in Angular2. (If it is already i'm not aware of it yet) but One should not depend on a specific order as already said. ---- > Suppose you have ngIf and ngFor directives on one element >> that's not supported. For more details see ngIf and ngFor on same element causing error. At least for this case there is no requirement to specify an execution order. Thank god. It breaks so it doesn't even need the feature.
  - jordic 10y ago
    Depending on your knowledge level.. for me was enought to build a comeplex prototype that probes I was with a correct choice.
- _blrj 10y ago
  You stopped reading after "I used it for two weeks?" Really? How much time do developers need to waste before realizing some software is bad? A month? A quarter? A year or two? I should be able to look at a library or framework's API examples and say "I don't want to use this," and not have to waste a second more.
  - onion2k 10y ago
    You can assess whether a framework is a good fit for your use case in two weeks. You can't assess whether or not the entire framework is good or bad in two weeks.
    - mwfunk 10y ago
      Exactly. There's a huge difference between saying something is objectively terrible, vs. saying that it's not the right choice for you (or that it's bad based on your subjective preferences).
    - Udik 10y ago
      Are you sure you don't want to say the exact opposite? Something might look good, simple and logic, but you might discover in the end, after a long time, that it wasn't well fit to your use case. On the other hand, something can be horrible, inconsistent, poorly documented and extremely hard to master, but might turn out to fit just exactly one specific use case. In any case, we're talking about web applications. Which would be the use case that angular2 doesn't fit? And which the one it fits? Because I don't remember angular2 being advertised as something that has a very specific use case.
      - alex504 10y ago
        The use case for Angular 2 is super hardcore enterprise. Lots of developers, very large multimillion dollar projects, and safety being a top concern. Everything must be done in a very standard way, and it assumes you need a bunch of stuff that only a fairly big application will need. Testing is very highly emphasized, with components being forced to be written in a way that is testable. This guy clearly doesn't know what Angular is doing under the hood, meaning there is a bunch of stuff going on in his app that he doesn't understand, which is causing him lots of bugs and heartache. Many a time developers have built Angular apps without understanding what they are doing and ending up with a flaming pile of garbage that needs to be completely rewritten. However if you know what you are doing or hire someone that knows what they are doing to set up an application for you, I think the framework does have its advantages. Having said all of this I really disliked my time working in Angular, with things like the terrible docs and lots of hidden esoteric knowledge needed being big flaws that they should address. For my company it made sense though.

jaimex2 10y ago

I stopped reading after "I used it for two weeks"

flukus 10y ago
Two weeks should be plenty of time to put something through it's paces and do a thorough evaluation.
- heisenbit 10y ago
  > The home of a peculiarly minded 21! year old web developer This developer was dropped into a larger project. He caught up with Angular 2 and TypeScript. He wrote an elaborate post. But maybe he had not been exposed to a larger set of diverse use cases and software patterns in practice yet. There are some learning hurdles to Angular 2 but imho. they are lower than what was there with Angular 1. Documentation could be better of course. Moving from 1 to 2 requires a bit of unlearning, it is essentially a new framework.
  - Udik 10y ago
    > There are some learning hurdles to Angular 2 but imho. they are lower than what was there with Angular 1 I really don't understand how people can claim this. I got my first basic application running in angular 1 in about two hours- no, I'm not talking about a tutorial but a small, real application. All you had to do to start was to include the minified angular framework in the page and write some plain javascript functions. That's it. Now, I've been working with angular 2 for the past month or so (on a brand new application). I still have very little understanding of what the framework does or how it works. I found it pretty easy to understand the basic concepts and inner working of angular 1, but I still haven't managed to grasp what angular 2 actually does. Some things seem to work, some others just don't. The documentation is obscure and lacking. The requests for basic features or bug fixes have discussion trails that go from many months ago up to yesterday. I just googled for the first example that comes to my mind- a pretty fundamental question: what's the execution order of directives in angular 2 and how to influence it? On the first page of results, only the first two are relevant (thanks Google!). Both are StackOverflow questions, and the answers are: >As far as I know the order of execution is undefined. You shouldn't depend on a specific order. >> That's just awful.. ---- > I think priority concept is yet not there in Angular2. (If it is already i'm not aware of it yet) but One should not depend on a specific order as already said. ---- > Suppose you have ngIf and ngFor directives on one element >> that's not supported. For more details see ngIf and ngFor on same element causing error. At least for this case there is no requirement to specify an execution order. Thank god. It breaks so it doesn't even need the feature.
- jordic 10y ago
  Depending on your knowledge level.. for me was enought to build a comeplex prototype that probes I was with a correct choice.
_blrj 10y ago
You stopped reading after "I used it for two weeks?" Really? How much time do developers need to waste before realizing some software is bad? A month? A quarter? A year or two? I should be able to look at a library or framework's API examples and say "I don't want to use this," and not have to waste a second more.
- onion2k 10y ago
  You can assess whether a framework is a good fit for your use case in two weeks. You can't assess whether or not the entire framework is good or bad in two weeks.
  - mwfunk 10y ago
    Exactly. There's a huge difference between saying something is objectively terrible, vs. saying that it's not the right choice for you (or that it's bad based on your subjective preferences).
  - Udik 10y ago
    Are you sure you don't want to say the exact opposite? Something might look good, simple and logic, but you might discover in the end, after a long time, that it wasn't well fit to your use case. On the other hand, something can be horrible, inconsistent, poorly documented and extremely hard to master, but might turn out to fit just exactly one specific use case. In any case, we're talking about web applications. Which would be the use case that angular2 doesn't fit? And which the one it fits? Because I don't remember angular2 being advertised as something that has a very specific use case.
    - alex504 10y ago
      The use case for Angular 2 is super hardcore enterprise. Lots of developers, very large multimillion dollar projects, and safety being a top concern. Everything must be done in a very standard way, and it assumes you need a bunch of stuff that only a fairly big application will need. Testing is very highly emphasized, with components being forced to be written in a way that is testable. This guy clearly doesn't know what Angular is doing under the hood, meaning there is a bunch of stuff going on in his app that he doesn't understand, which is causing him lots of bugs and heartache. Many a time developers have built Angular apps without understanding what they are doing and ending up with a flaming pile of garbage that needs to be completely rewritten. However if you know what you are doing or hire someone that knows what they are doing to set up an application for you, I think the framework does have its advantages. Having said all of this I really disliked my time working in Angular, with things like the terrible docs and lots of hidden esoteric knowledge needed being big flaws that they should address. For my company it made sense though.