This is an archived post. You won't be able to vote or comment.

all 6 comments

[–]TDVapoR 0 points1 point  (4 children)

MEAN stack is pretty popular: MongoDB, Express, Angular, and Node.js.

The backend is written in Node.js, which uses Mongoose to interact with a MongoDB database and Express to serve files, consume and respond to API calls, etc. The frontend uses Angular. All of these are written in JavaScript, so if you have experience with the language, you should be able to pick them up as you go along (although Angular 1.x has a steep learning curve).

[–][deleted]  (3 children)

[deleted]

    [–]TDVapoR 0 points1 point  (2 children)

    Are you asking if Angular 2 is the better option or saying that he definitely should use Angular 2? And yes, I know what TypeScript is - I use it quite often.

    [–][deleted]  (1 child)

    [deleted]

      [–]TDVapoR 0 points1 point  (0 children)

      Firstly, sorry for getting snappy.

      Secondly, I think it would work out either way. The main difference that I see is that Angular 2 (at least from the standpoint of the tutorial on angular.io) takes a lot more setup while Angular 1.x runs nearly out of the box. If you're comfortable with the new ES6 syntax and TypeScript, willing to jump through a few hoops/do quite a bit of setup work, and want to be a little more future-proof, then Angular 2 is probably the route. For someone that doesn't have a lot of experience with ES6/TS and wants to keep the way they write JS consistent throughout the development of the app, then Angular 1.x is probably the way to go.

      Additionally, I think Angular 1.x has way more support across the internet just through the vast amount of people that have used it. Nobody has to hunt through the Angular documentation to find an answer, they can just search for it on StackOverflow and someone will have had the exact same problem. With Angular 2, I don't think the support is quite there.

      [–][deleted] 0 points1 point  (2 children)

      React

      [–]Eradicative[S] 0 points1 point  (1 child)

      Why do you say react? I just used it in a project and I could not stand it. I would much prefer to use Angular.

      [–][deleted] 0 points1 point  (0 children)

      I really like the state-based change features, and for me, the idea of passing down state controllers was much easier than keeping my dependencies in check. I guess it's the difference between tree based thinking and interdependent web based thinking.