Live data from Hacker News

Version 6 of Angular Now Available

blog.angular.io

61–70 of 86 posts

Re: Version 6 of Angular Now Available

#61

This upgrade looks absolutely fantastic. The Elements piece in particular looks amazing, and has the potential to be a real game changer for shops that have a diverse set of applications that they use, and need large scale re-use of components. At the mid-size corporation that I work at, we just standardized all Javascript development on Angular from a mismash of a ton of technologies. Angular seems very well suited…

>At the mid-size corporation that I work at, we just standardized all Javascript development on Angular from a mismash of a ton of technologies. Angular seems very well suited for this role. In my experience centralisation and fixation on specific technology leads to stagnation quickly. IMO you should allow teams to choose their own tools. How else will you improve?

To quote one of Akin's laws which were on HN yesterday, "better is the enemy of good".

It's really good when one technology is used throughout an organization to achieve the same purpose. At some point, the technology you use is actually good enough, and incremental improvements to "keep up with the times" are simply distractions from the real work. And if at some point you find that your tech has truly stagnated, at least you're stagnated together, and can modernize together at the same time.

Re: Version 6 of Angular Now Available

#63
post #37

Sigh. Yet more confirmation that my team has made the correct choice in switching to a mostly vanilla JS development stack (we still use RiotJS for one-way template binding). I was there for the beginning of Angular and it got me hooked on single page applications, but what I am seeing now is the antithesis of productivity. No one building a website for a business should be using this stuff, unless they drank so much…

Amen. Using your own vanilla JS architecture gives you flexibility and future proof. It is easier to hire new devs and train them. A little documentation and a template project go a long way to getting uniform projects.

Re: Version 6 of Angular Now Available

#64
Ignoring Angular since the start, this headline and comments made it like I need check this out again, but, Angluar2+ seems like in decline in trend(comparing to React and even Vue), is this not true all of a sudden now?

Re: Version 6 of Angular Now Available

#65
post #42
post #39

I was joyfully expecting this upgrade and checked the release notes daily during the RC phase. Don't let the quick 'major' version changes shock you, upgrading 4 -> 5 was easy and I expect the same for this upgrade. A big thanks to everyone involved in shaping this release and ensuring the upgradability for the past major versions, including the huge effort in making it possible to continuously migrate from AngularJS…

How about the story on mobile? Is there an Angular analog to React Native?

Not really answering your question cause React Native builds to native platform code.

But Ionic uses Angular internally -> Cordova-> PhoneGap (mobile)

Re: Version 6 of Angular Now Available

#66
In case anyone else has not been following Angular very closely, apparently AngularJS is version one, based on JavaScript, while Angular refers to version 2 and higher, which use Typescript. A major difference seems to be that Angular is more geared towards one-way binding. Two-way binding was from what I gather a common complaint from the React side, saying it's slow and leads to complex and unexpected behavior.

Re: Version 6 of Angular Now Available

#67

The auto import of providers is my favorite feature in this. Now you can just define something as @Injectable() and make it available in the module automatically. Big improvement over older versions

Why do you even need providers?

No one using React uses them. Google can't break free of old Java habits.

Re: Version 6 of Angular Now Available

#68

This upgrade looks absolutely fantastic. The Elements piece in particular looks amazing, and has the potential to be a real game changer for shops that have a diverse set of applications that they use, and need large scale re-use of components. At the mid-size corporation that I work at, we just standardized all Javascript development on Angular from a mismash of a ton of technologies. Angular seems very well suited…

>At the mid-size corporation that I work at, we just standardized all Javascript development on Angular from a mismash of a ton of technologies. Angular seems very well suited for this role. In my experience centralisation and fixation on specific technology leads to stagnation quickly. IMO you should allow teams to choose their own tools. How else will you improve?

This sounds like how you'd end up doing web development in the least efficient way possible. There is a ton of space for reuse, the web is dead simple and the same pattern shows up over and over and over.

Re: Version 6 of Angular Now Available

#69
post #39

I was joyfully expecting this upgrade and checked the release notes daily during the RC phase. Don't let the quick 'major' version changes shock you, upgrading 4 -> 5 was easy and I expect the same for this upgrade. A big thanks to everyone involved in shaping this release and ensuring the upgradability for the past major versions, including the huge effort in making it possible to continuously migrate from AngularJS…

> There are a few workarounds but they did not seem to work properly. If anyone has suggestions on that part.

Actually with angular-hybrid you do not need to use a AngularJS entryComponent. The only thing that needs to be AngularJS is the bootstrap component.

Also AngularJS components can be Upgraded easily and Angular2+ Components can be downgraded easily, too. The only problems are old school Directives which can be wrapped in a component for interop or just rewritten.

You can even remove angular-hybrid when you just "upgrade" all your AngularJS code that is used in routes. (you still need to have a AngularJS rootElement and than inject a downgraded ui-view).

i.e. you can't have `bootstrap: [UIView]` however using `` in your index.html while root element is like that:

`.component('rootElement', {template: ''})`

It sucks to create AngularJS wrapper components in Angular since you need to create two, i.e. from AngularJS component:

    ng1module.component('demo', {template: 'hase'});

You need to create the following ng2+ components:

    @Directive({selector: 'demo-shim'})
    export class DemoShimDirective extends UpgradeComponent {
    @Input() text: string;
    // upgrade constructor with super call
    }
and than have another which can be used in routes:

    @Component({selector: 'demo', template: ''})
    export class DemoComponent {}

and finally you can use it happily in your Ng2StateDeclaration (P.S.: I just did that today)

Re: Version 6 of Angular Now Available

#70

How will WebAssembly play in to Angular in the future?

For the most part, they’re not part of the same discussion. TypeScript/JavaScript is still a sensible language and execution environment for interaction driven browser concerns.

That said, there are some interesting implied ambitions for Angular. The AngularDart project, the Bezel project, the AngularCompiler more generally as a point of special focus...

Post reply on HN