Angular 2 – Best Practises
blog.budacode.com
Angular 2 – Best Practises
1–10 of 94 posts
Re: Angular 2 – Best Practises
#2Can 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.
Re: Angular 2 – Best Practises
#3While 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 it to the spec, what then ?
Re: Angular 2 – Best Practises
#4Could 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...
Re: Angular 2 – Best Practises
#5While 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…
> 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.
Re: Angular 2 – Best Practises
#6Could 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...
Re: Angular 2 – Best Practises
#7Could 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...
It's more mature now that the Angular 1 experiment is over
It's written in TypeScript, so you can write your frontend in TypeScript. Many bugs averted.
You can use a real reactive model (http://victorsavkin.com/post/137821436516/managing-state-in-...)
Re: Angular 2 – Best Practises
#8While 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
Re: Angular 2 – Best Practises
#9While 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…
> 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 not willing to deal with that kind of over engineering blessed in the Java world, I know what it leads to. If this approach was really successful everybody would be using JWT by now. Obviously they don't.
Re: Angular 2 – Best Practises
#10Could 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 TypeScript is very similar to Java and C#.
(The list is a slight caricature but I hope the general point is clear.)