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.
Angular 5.0.0
101–110 of 189 posts
Re: Angular 5.0.0
#102Earlier 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.
--React developer
Re: Angular 5.0.0
#103Re: Angular 5.0.0
#104Has 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.
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
#105I 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.
Re: Angular 5.0.0
#106Re: Angular 5.0.0
#107Earlier 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
Re: Angular 5.0.0
#108Earlier 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.
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
#109Earlier 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…
Re: Angular 5.0.0
#110Has 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.
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.