8

Trying to learn Angular and reactjs, reading up the tutorial or documentation...

Why the hell are there ten million more shit I need to look at first? (such as rxjs, Babel, webpack... and whatever the fuck they are)

Now am I supposed to master those ten million tools/libraries before I can proceed?

Of course there is no ten million but mentally it's no difference. I'm just fed up with this.

Comments
  • 0
    @theScientist Not at the same time. I just finished following a hello world tutorial on Angular. Before going deeper, I started to take a look at reactjs. As I have no experience for both, I just wanted to have a comparison... Then this strikes me.
  • 0
    @theScientist That's not too bad. I do not have preference over the two in terms of technical aspect as it's too early for me to say. However, Facebook's BSD + patent license does bug me a bit. Again it's not my decision to make whether the license is an issue... But I kinda don't want to waste a lot of time mastering it then my boss one day comes and tells me "we can't use it because of the license". I would like to know enough to comment on pros and cons though.
  • 1
    You have it all nice and easy. I started web deving two years ago. I went with angular 1.x because of the mean stack hype and was afraid of dynamic typing (since I came from c#/java) I used typescript. I ended up with tons of files and added gulp. Then I needed more libraries and I used Bower, then everyone migrated to npm and it was easier to use broeserify. Then webpack became the obvious master (I even fiddled with jspm) and angular 2 came along... Now you can just use angular 2+ cli and not worry about the tools...
Add Comment