Live data from Hacker News

Angular 2 – Best Practises

blog.budacode.com

31–40 of 94 posts

Re: Angular 2 – Best Practises

#31
post #4

Could someone tell me one-or-more reasons to choose Angular for a new project, now that the React ecosystem is mature enough to compete with it? As I feel that from a conceptual/architectural point of view Angular is simply on a loosing path. https://www.google.com/trends/explore#q=angular%20tutorial%2...

I'm not sure I'm on the bandwagon that believes that commingling JS, CSS and HTML into a single "component" is a great thing. I just don't understand...

Re: Angular 2 – Best Practises

#32
post #23
post #10

Earlier quoted context omitted.

My impression is that a lot of "mature" (aka boring old) companies like Angular 1 and the sound of Angular 2 over React. For a number of reasons: - In general Java and C# programmers like it. - It is made by Google (perceived as more "mature", business like) rather than Facebook (young kids). - It takes a lot of inspiration from server side development with its dependency injection and general terminology. - And Type…

> My impression is that a lot of "mature" (aka boring old) companies like Angular 1 and the sound of Angular 2 over React. React has been around for a while, but it is still only a library. Angular 1 and 2 are frameworks. Also Angular 2 is a complete rewrite and not even in final release. I'm not sure how that is boring or old. As with Angular 1, Angular 2 aims to be opinionated, so it should be clearer how to do thi…

The places I am referring to are not actually using Angular 2. They are using Angular 1 but like "the sound" of Angular 2.

Where the sound is the promise of a better tomorrow without actually looking at alternatives.

Re: Angular 2 – Best Practises

#33
post #4

Could someone tell me one-or-more reasons to choose Angular for a new project, now that the React ecosystem is mature enough to compete with it? As I feel that from a conceptual/architectural point of view Angular is simply on a loosing path. https://www.google.com/trends/explore#q=angular%20tutorial%2...

Your link proves controversial point :)

Please stop wars "a vs r" - it's counterproductive. Knowledge sharing is much better. If you don't trust me - read Twitter of Dan Abramov.

Re: Angular 2 – Best Practises

#34
Not directly related but I would appreciate any thoughts on which angular version one should go with, for a new development (fairly large enterprise project) at this point of time. How hard would it be to upgrade to version 2.0 if we start our early development on v1.5, assuming 2.0 is not ready for prime time (or is it?)

Re: Angular 2 – Best Practises

#35

Well there are 2 advantages to angular (1 or 2) over react: 1. It has effortless two way binding, which makes apps that allow mutating the same state from a lot of places easy and simple to make (though one could argue harder to maintain) 2. It uses a template rather then a precompiler (such as jsx) which has two advatages- since its html it makes cooperating with designers and the design process itself easier and it…

3. You can just learn / hire for Angular 2. You don't have to learn / hire for React + insert 5 other pieces of the stack required to make a complete app.

Re: Angular 2 – Best Practises

#36
post #4

Could someone tell me one-or-more reasons to choose Angular for a new project, now that the React ecosystem is mature enough to compete with it? As I feel that from a conceptual/architectural point of view Angular is simply on a loosing path. https://www.google.com/trends/explore#q=angular%20tutorial%2...

I'm honestly not sure why React being more mature now would be a reason not to use Angular for a new project.

Re: Angular 2 – Best Practises

#37
post #31
post #4

Could someone tell me one-or-more reasons to choose Angular for a new project, now that the React ecosystem is mature enough to compete with it? As I feel that from a conceptual/architectural point of view Angular is simply on a loosing path. https://www.google.com/trends/explore#q=angular%20tutorial%2...

I'm not sure I'm on the bandwagon that believes that commingling JS, CSS and HTML into a single "component" is a great thing. I just don't understand...

There's a lot to be said for separating concerns and it's still good practice within your component. No-one is really disputing it afaik, but the way we are/were creating web pages are based on a document-centric paradigm.

Single Page Apps (SPAs) are more app-like than webpage-like and if you're really going for reusability then your components need to have a say in how they are rendered. That means they need to provide /some/ HTML.

You can still create components without including CSS but you'll likely need to provide structure (HTML) in order to bind behavior/callbacks/events to it. It's still good practice to separate rendering (HTML/JSX/NG) and behavior.

Re: Angular 2 – Best Practises

#38

Can someone recommend me good resources to learn (start with) angular 2? I am totally new, I am learning node after JS and after that, I would like to introduce myself to angular. I have some experience on JSF but I suppose it is completely different.

If you're willing to pay: https://www.ng-book.com/2/ is good.

Re: Angular 2 – Best Practises

#39
post #4

Could someone tell me one-or-more reasons to choose Angular for a new project, now that the React ecosystem is mature enough to compete with it? As I feel that from a conceptual/architectural point of view Angular is simply on a loosing path. https://www.google.com/trends/explore#q=angular%20tutorial%2...

For Angular 1 vs. React, I would just say depending on the resources you have - for example if a team is very productive with Angular 1 & there isn't enough time to get a team to pivot skills, then it may make more sense to go with that from a business perspective.

IMO there is one main reason to choose Angular 2 over React currently - perf. Angular 2 has significant perf improvements over the other libraries/frameworks out there, and supports incremental rendering as opposed to React's render all at once model. Angular 2 also will have the best built-in animation support of the various libraries/frameworks out there, in part due to the Angular team's collaboration with the Chrome team (this is true with Angular 1 as well).

Otherwise, React is more mature than Angular 2 & has a simpler API. Conceptually, Angular 2 and React share much in common, and architectures should look similar between well written apps in both.

Re: Angular 2 – Best Practises

#40
post #10
post #4

Could someone tell me one-or-more reasons to choose Angular for a new project, now that the React ecosystem is mature enough to compete with it? As I feel that from a conceptual/architectural point of view Angular is simply on a loosing path. https://www.google.com/trends/explore#q=angular%20tutorial%2...

My impression is that a lot of "mature" (aka boring old) companies like Angular 1 and the sound of Angular 2 over React. For a number of reasons: - In general Java and C# programmers like it. - It is made by Google (perceived as more "mature", business like) rather than Facebook (young kids). - It takes a lot of inspiration from server side development with its dependency injection and general terminology. - And Type…

> In general Java and C# programmers like it.

Why? What are you basing this on?

> It is made by Google (perceived as more "mature", business like) rather than Facebook (young kids).

By who? React is more mature than angular 2 and angular 1 is crap.

> It takes a lot of inspiration from server side development with its dependency injection and general terminology.

I'm not sure how this is a good thing even if true.

> And TypeScript is very similar to Java and C#.

TypeScript can be used with React.

Post reply on HN