Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Angular 2 – Best Practises

blog.budacode.com

Post reply on HN
Print view View original

11–20 of 94 posts

Re: Angular 2 – Best Practises

#11

Post by Secretmapper »

laurencei wrote: post #6
cies wrote: 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...

If you run that some trends report - but with "Angular 2" - that shows a much higher uptake: https://www.google.com/trends/explore#q=angular%20tutorial%2...

The takeaway of course is that most of those probably want to pick up Angular 2 because they used Angular.

I made a conscious switch from Angular to React because React (and the flux pattern) really did reinvent how web components are built and it's incredibly intuitive. I simply don't see the same innovation in Angular 2 apart from 'we made Angular more modern'

Re: Angular 2 – Best Practises

#12

Post by spriggan3 »

rahkiin wrote: post #8
spriggan3 wrote: post #3

While I found ng1 useful, I'll never touch this one. I can see now how dependency injection can be both a blessing and also a curse in some contexts. I also can see how Typescript features can shape a codebase and ultimately make it look like Enterprise Java, instead of making it easy to use and to learn. I also just don't like the over use of non standard features like decorators. There is a chance they don't make i…

As is shown with the decorator transpiling in both typescript and babel, it doesn't really matter if it never makes it to the spec: you can still use it using a compiler. I use it in my own production software and it is a real blessing when trying to use a more OO approach in a JS world

> it doesn't really matter if it never makes it to the spec

I does matter as there is difference between introducing type support in a language and introducing features that completely are non standard. Now imagine TC39 introduces a decorator syntax that is not compatible with Typescript's implementation ( it happened in the past with previous Typescript module syntax and the language had to break compatibility )

Angular 2 is completely based on the use of decorators to inject almost anything. Sometimes the decorator definition itself is bigger than the class using it.

Re: Angular 2 – Best Practises

#13

Post by dhaya »

jaimehrubiks wrote: post #2

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.

Angular 2's own tutorial is a nice start: https://angular.io/docs/js/latest/tutorial/ .

Re: Angular 2 – Best Practises

#14

Post by Touche »

rahkiin wrote: post #8
spriggan3 wrote: post #3

While I found ng1 useful, I'll never touch this one. I can see now how dependency injection can be both a blessing and also a curse in some contexts. I also can see how Typescript features can shape a codebase and ultimately make it look like Enterprise Java, instead of making it easy to use and to learn. I also just don't like the over use of non standard features like decorators. There is a chance they don't make i…

As is shown with the decorator transpiling in both typescript and babel, it doesn't really matter if it never makes it to the spec: you can still use it using a compiler. I use it in my own production software and it is a real blessing when trying to use a more OO approach in a JS world

It matters if the person who wrote the babel plugin stops supporting it. This is the problem I have with the babel culture, I don't think people realize that they are really inventing their own language which is a mismash of various language features they like; some of which is part of a real language, some of which is not.

Re: Angular 2 – Best Practises

#15

Post by spdy »

cies wrote: 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...

The only decision you have to make if you like opinionated frameworks or not.

Both ecosystems are vibrant enough to stay for the foreseeable future.

Re: Angular 2 – Best Practises

#16

Post by Avalaxy »

spriggan3 wrote: post #9
Avalaxy wrote: post #5

Earlier quoted context omitted.

> I also can see how Typescript features can shape a codebase and ultimately make it look like Enterprise Java, instead of making it easy to use and to learn. Meh, I don't see how this is a bad thing. We need some more software engineering in the javascript space instead of cowboy hacking.

> We need some more software engineering in the javascript space instead of cowboy hacking Are you saying that the ability to write entreprise java code is what separates "software engineers" from "cowboy hackers" ? That statement is arrogant. My point is the use of Typescript doesn't produce idiomatic Javascript code, since it encourages writing front-end code a certain way. You might like it, fine, I'm personally n…

> Are you saying that the ability to write entreprise java code is what separates "software engineers" from "cowboy hackers" ?

I'm saying that software engineering doesn't need to be simple, it needs to be solid. I think type safety is one of those features that makes a language more solid.

Re: Angular 2 – Best Practises

#17

Post by sjclemmy »

I've been using ng2 for a few Ionic 2 Projects recently and its fantastic. Rxjs is an absolute must - it allows amazingly precise code to manage mutation. The way everything is a component is great. I can write a frontend app in a couple of days using Ionic 2. I'm so productive.

Edit: Why the downvote?

Re: Angular 2 – Best Practises

#18

Post by spriggan3 »

Avalaxy wrote: post #16
spriggan3 wrote: post #9

Earlier quoted context omitted.

> We need some more software engineering in the javascript space instead of cowboy hacking Are you saying that the ability to write entreprise java code is what separates "software engineers" from "cowboy hackers" ? That statement is arrogant. My point is the use of Typescript doesn't produce idiomatic Javascript code, since it encourages writing front-end code a certain way. You might like it, fine, I'm personally n…

> Are you saying that the ability to write entreprise java code is what separates "software engineers" from "cowboy hackers" ? I'm saying that software engineering doesn't need to be simple, it needs to be solid. I think type safety is one of those features that makes a language more solid.

Complexity for the sake of it doesn't make software engineering solid. JEE complexity doesn't come from the need to be solid but from Java's flaws. In my book it's the very definition of bad engineering.

Re: Angular 2 – Best Practises

#19

Post by laurencei »

cies wrote: 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...

One specific reason I am personally choosing Angular 2, is that the Ionic2 Framework also uses Angular 2 [0].

So I can re-use code from my front end website on my native mobile apps for the new startup I'm launching. Much less code = quicker time to MVP, and lower cost of development.

[0] http://blog.ionic.io/angular-2-ionic/

Re: Angular 2 – Best Practises

#20

Post by petetnt »

laurencei wrote: post #19
cies wrote: 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...

One specific reason I am personally choosing Angular 2, is that the Ionic2 Framework also uses Angular 2 [0]. So I can re-use code from my front end website on my native mobile apps for the new startup I'm launching. Much less code = quicker time to MVP, and lower cost of development. [0] http://blog.ionic.io/angular-2-ionic/

Have you tried React with React Native[0]?

[0] https://facebook.github.io/react-native/

Post reply on HN