Angular 2 is a great option especially for people who like TypeScript. Hope release will be ready soon.
Angular 2 Release Candidate
21–30 of 139 posts
Re: Angular 2 Release Candidate
#22I realize a lot of companies flocked to Angular and it's used in a lot of places, but from the outside it seems to be fighting on two fronts. 1. Companies currently implementing it not wanting it to change or for there to be a quick and painless migration from 1.x to 2.x. So, less change, more hand-holding. The web changed a lot though, so its change is understandable. 2. Trendsetters and upcoming companies looking f…
It is the million dollar question. If you are building a large product with an expected life of 10+ years, can you trust Angular to still be maintained?
Re: Angular 2 Release Candidate
#23I realize a lot of companies flocked to Angular and it's used in a lot of places, but from the outside it seems to be fighting on two fronts. 1. Companies currently implementing it not wanting it to change or for there to be a quick and painless migration from 1.x to 2.x. So, less change, more hand-holding. The web changed a lot though, so its change is understandable. 2. Trendsetters and upcoming companies looking f…
As someone that works for a #1 company, I am living that anxiety. We all know it will be inevitable, and we all know it will be hell rewriting it. If it's more than copy-pasta then I doubt it will be received well. And #2 is spot on -- React is eating Angular's lunch. I'd love to use it at work but I can't, and I don't think I'm the only one.
Just out of curiosity what exactly can you do with React that you can't with Angular 2?
Re: Angular 2 Release Candidate
#24"Having to rewrite for our Angular 1 app for Angular 2".
Honestly, there is so little continuity that you have the option of just switching to React.
Or perhaps, just maintaining your Angular 1 app - and then assuming the 1.x fork will be carried on for a long time.
Re: Angular 2 Release Candidate
#25Earlier quoted context omitted.
As someone that works for a #1 company, I am living that anxiety. We all know it will be inevitable, and we all know it will be hell rewriting it. If it's more than copy-pasta then I doubt it will be received well. And #2 is spot on -- React is eating Angular's lunch. I'd love to use it at work but I can't, and I don't think I'm the only one.
Just out of curiosity what exactly can you do with React that you can't with Angular 2?
React lets you summarize your framework in a single sentence: make your UI a pure function of your model, but keep performance. OTOH, I still don't understand what the deal with Angular is.
Re: Angular 2 Release Candidate
#26I'm coming at this from the perspective of someone who has never used Angular 1.x or 2.x. I guess the first thing on my mind is: can I make Angular 2 work just like React does? Is there any way to use it without making/(being allowed to make) separate HTML templates and CSS files? If not, this is a serious disadvantage. Having the view layer scattered across 3X the files (vs React) would make it very hard to follow t…
"Is there any way to use it without making/(being allowed to make) separate HTML templates and CSS files? If not, this is a serious disadvantage"
Translation:
"Can I sh*t where I eat? If not, this is a serious disadvantage"
Re: Angular 2 Release Candidate
#27Angular core team member here, happy to answer questions
Since Angular 2 is so different from Angular 1 and there is not a universal solution to upgrade from 1 to 2, do you think there would have been a better PR/current user reaction if it was named something else?
i like Max Lynch's (of Ionic framework) take on this http://blog.ionic.io/angular-is-a-design-pattern/
Re: Angular 2 Release Candidate
#28I realize a lot of companies flocked to Angular and it's used in a lot of places, but from the outside it seems to be fighting on two fronts. 1. Companies currently implementing it not wanting it to change or for there to be a quick and painless migration from 1.x to 2.x. So, less change, more hand-holding. The web changed a lot though, so its change is understandable. 2. Trendsetters and upcoming companies looking f…
> looking for something new fresh and solid
Don't we all? I wonder if it's really worth it most of the time... That's assuming that new can be solid to begin with.
Re: Angular 2 Release Candidate
#29Earlier quoted context omitted.
I read something a while ago that I think really sums the key difference, is that angular and other frameworks inject javascript into html and its awkward. React injects HTML into javascript, and it seems, that way around is a lot more powerful as you have all of javascript to manipulate html rather than having HTML/Templating/Extensions to manipulate Javascript. The two advantages are speed (it's supposed to be fast…
So Java Servlets was the right approach all this time?
Pretty sure PHP predated Servlets (if not by much).
Re: Angular 2 Release Candidate
#30Lots more work to do here, but we're pretty happy with how the core looks! For those worried about size (which has absolutely been a fair concern over the alpha/beta process) - here's a "hello world" built with Rollup and our offline template precompilation. Clocks in at 200kb min/47k gzipped, with a bit more room from optimization over the next couple of weeks... https://ng2-compiler-test2.firebaseapp.com/
That seems a lot for:
Hello world
hello child