Live data from Hacker News

Angular 5.0.0

blog.angular.io

101–110 of 189 posts

Re: Angular 5.0.0

#101

Earlier quoted context omitted.

Vue.js can be a good option for shops coming from Angular 1.x.

When Angular 1 was left for dead I went to Knockout. I think it is very similar and also very simple to use.

KO is long dead, but I kinda liked it. After ko and angular 1 I felt right at home with Vue.

Re: Angular 5.0.0

#102
post #97

Earlier quoted context omitted.

I don't agree. react-router has changed enough in the last 2 years to throw me off quite a bit when I started a new project

React and react-router are not the same thing at all. They're developed by different teams at different organisations. It's not fair to compare the two.

But we're comparing against Angular, which has a router and the rest of the kitchen sink. If your React app is anything more than a toy, it will almost certainly require most of that sink and you'll suffer the version churn of a thousand ambiguously maintained components.

--React developer

Re: Angular 5.0.0

#104

Has anyone had success using the AOT tools to build a package of reusable angular components? I was able to use AOT pretty easily for a stand-alone app, but keep running into issues when trying to create a shareable component, and there is not a lot of documentation around this.

I have, but by using ngc in my gulp build task (had to use gulp for the reason below), unfortunately couldn't make it incremental at that time, so it takes several seconds to re-build when the source is changed.

There is actually another problem when you want to develop reusable UI component library project is that you have to inline style files and template file into ts component.

Re: Angular 5.0.0

#105

I somehow do not get all that bashing. Angular did extremely great things with Angular 1 (back then). As time passed, the community learned that there are better/other concepts. React came out - nice. NG2/4 therefore had to include major changes to pave the way for the future and more modern concepts. And it is important that they do that because some people have built huge teams and applications based on Angular. So…

> ng5 fixes major issues from ng2 Good grief, this is insanity. I'm still dealing with major issues in ng1.

Consider upgrading. Ng2/4 fixes a lot of major issues in ng1. It takes you a week or so but you'll have a solid foundation for the future. And it's as i said more economic than doing a full rewrite to react/vuejs (of course VueJS is sexy as hell)

Re: Angular 5.0.0

#107
post #69

Earlier quoted context omitted.

I hear you. What's causing them to iterate so fast? I still remember the days of Java and .Net where they did yearly releases and phased transitions with good documentation of what's deprecated and what's new.

> and phased transitions with good documentation of what's deprecated and what's new. If you're after that >> https://emberjs.com

Agreed. Ember does a great job with documentation.

Re: Angular 5.0.0

#108

Earlier quoted context omitted.

Vue.js can be a good option for shops coming from Angular 1.x.

This. Vue feels a lot like Angular 1, but gets more stuff right. Angular 2 feels like an over engineered React clone using more complex tech to solve the same problems. I also really dislike JSX so I am biased.

I am in the same boat as you. I was in love with Angular 1 and when Angular 2 was announced I was very much disappointed. There was not one redeeming things about A2 IMO, just a huge clusterfuck which is still growing with every version.

Also never liked React. The whole JSX and everything is just isn't for my taste. I'm speaking as a solopreneur who likes launching a new site every month. Anyway, so a friend suggested Vue and this framework brought me actual joy. It is everything I was hoping to see in Angular 2 and better.

Seriously, if you like A1 but not a fan of A2 or React then Vue is definitely up your alley.

Re: Angular 5.0.0

#109
post #48
post #18

Earlier quoted context omitted.

They are following semver: http://semver.org/ So the major version changes whenever they make a backwards-incompatible change. However, I clicked in their upgrade calculator (linked from the post) and at a glance it appears the incompatible changes are fairly minor.

But did semver really set out to eradicate all distinction between minor incompatibilities and complete architectural reboots? So much semver adoption seems to be based entirely on wishful thinking. Step 1: hey, perfect drop-in compatibility would be so cool Step 2: we can do it, with semver! Step 3: we use semver! Yay us! Step 4: oh, turns out adopting semver did not make perfect drop in compatibility any easier Ste…

Adopting and enforcing usage of semver across teams helps tame some code cowboys that think they can change their library and everyone else should just adjust to their new API. I found it very useful for documenting API changes on an intra-company dependency where the library developers said, "Oh we don't change the API", but actually changed the API in backwards-incompatible ways all the time and made everyone downstream change their code on every release.

Re: Angular 5.0.0

#110

Has anyone had success using the AOT tools to build a package of reusable angular components? I was able to use AOT pretty easily for a stand-alone app, but keep running into issues when trying to create a shareable component, and there is not a lot of documentation around this.

I have, but by using ngc in my gulp build task (had to use gulp for the reason below), unfortunately couldn't make it incremental at that time, so it takes several seconds to re-build when the source is changed. There is actually another problem when you want to develop reusable UI component library project is that you have to inline style files and template file into ts component.

> There is actually another problem when you want to develop reusable UI component library project is that you have to inline style files and template file into ts component.

We have a webpack-based process, and using the angular2-template-loader will take care of this for you. Unfortunately, webpack and aot don't mix well.

Post reply on HN