angular 9
Posted Jan 21, 2020, 11:39 AM UTC
20235
* sad waifu noises *
12
I don't understand why is the community rushing? let the team take their time, Angular 8 is great, why are you pushing them?
9
Ivy. Everyone wants stable fixed ivy already.
10
The Ivy side project has taken up so much time and effort that other parts of the ecosystem are languishing behind. Once they get Ivy out then they can finally upgrade to RxJS 8, TS 3.7, etc and maybe focus on a few other bugs.
8
Actually TS 3.7 seems to have been merged into angular 9 cause it got delayed so much.
1
I recently updated a branch off of our master to v9 and it all seemed to go pretty smoothly! Much better than the last time I tried. Only one issue with a package not being supported that we weren't using anyway.
That being said ivy did close to nothing for us but oh well our app is large š¤·āāļø
8
I dont know if I should be happy or worried about the Release
6
Happy. It means they're really working hard to iron out as many bugs as possible before going live. What you don't want is a major new release where they're like, "Hey, we're proud to announce the upcoming Angular 9, and here's the beta, but don't use it because here's RC1, and now it's done!" That shit's gonna be buggy as hell.
10
dot.net core intensifies
6
Still remember that tweet that some prson from angular team said on Twitter that she will not release angular 9 before xmas.. what a joke. It is still not released even now :D
2
So Iām not the only one that feels this way. :( Where are yea Angular 9! )
1
hahaha, not only me )
1
[deleted]
1
Worth the wait
1
I've started Angular recently snd looking for working solutions on tutorials and stack is nightmare. Things that worked 5 years ago don't work now. Whyyy.
-10
5 years ago was angularjs. Angular is a completely different framework. They just (unfortunately) share the name.
14
Nah, even Angular 5 has this feature.
-4
There were some breaking changes in RXJS going from 5 to 6. But that's about it.
6
That's going to be the case with most frameworks, chief. Laravel, React, Vue, Spring(maybe not as much) but the list could go on.
Frameworks evolve just like languages do. Javascript today is fairly different from 5 years ago I'd say.
8
Haha, no its not the case with React at all. React doesn't break BC often, if ever. the closest thing we have to breaking bc in React are some life cycle methods that are currently scheduled to be deprecated.
-7
React does well in not breaking as new stuff is added, but everytime I go back to React there is a whole new paradigm I am (supposed) to be using that is different from before. Think HOC, Stateless Components, etc.
5
You .. you go back from Angular?
edit: joke aside. Vue and Angular it is for me. Fuck that state management in react. Fun fact: When i used React, i sprinkled observables all over. Nobody tells me how to manage state.
3
I actually agree with you there. The recent trend of switching to functional components with hooks is so annoying. its all the rage and its a poor fit for many situations. i still use es6 classes and stateless components more often than hooks
2
I recently inherited a React project that was using hooks, but not context. Also redux. Oh and sagas too. Took the previous Dev 3 months to write it and it wasn't even finished. After 2 weeks of staring at the codebase I re-wrote most of the core app in one night in Angular and RxJS, the gradually have put in Akita for better state management and a few weeks later the app is almost done and ready to ship. I LOLed in Angular.
2
React is awful for large systems. It's nice for little one off apps. And FB is actually a reason against using React heh.
1
heh, i have built multiple large apps with react. 100+ routes on one app with ssr. not many performance issues honestly. last app i built i used preact instead and its a little buggy with react router sometimes doing a navigation instead of using history but its hard to care when the build is so small. i started using react around the time angular 4 came out and havent looked back. i like mobx because it reminds me alot of $scope from ng.
2
Keep an eye on v9 blockers.
Thanks. I"m refreshing regularly! Two have been closed since you posted this.
Hmm looks like they are almost there.