Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Angular v14 is now available

blog.angular.io

Post reply on HN
Print view View original

81–90 of 114 posts

Re: Angular v14 is now available

#81

Post by azemetre »

Zetaphor wrote: post #80
azemetre wrote: post #77

Earlier quoted context omitted.

Big corporations tend to copy what trendy tech companies do, and react dominates that market place. I haven’t look into too much but I’ve yet to see something like a boot camp even teach angular. It’s always react and friends.

I work for a Fortune 500 who has clients who range from Fortune 500 to Fortune 1000, I see TONS of Angular throughout the organization. There's also React, but a lot more Angular being paired with Java. Without data we're all just sharing anecdotes colored by our individual experience.

While that’s fair react still absolutely dominates the FE world, until proven otherwise I have a hard time believing angular is more popular or even close. I’d bet money on it if possible.

Boot camps, job listings, conferences, paid learning materials, etc all favor react in numbers.

Re: Angular v14 is now available

#82

Post by WorldMaker »

veidr wrote: post #76
WorldMaker wrote: post #61

It's good to see even experimental support for lessening the reliance on NgModules (which get in the way of appropriate tree-shaking), but I wish it weren't by doubling down on Angular's usage of non-standard Decorators. Requiring an experimental build flag in Typescript to even use Angular at all still feels like a red flag if not just outright poor taste in the framework architecture.

Yeah, that has always weirded me out, too, but I have assumed that because Angular is one of TypeScript's largest and most significant customers, that the flag is highly unlikely to actually be removed. (?) I'm just guessing though.

My understanding is that Babel already removed support for similar decorators to the ones Angular uses because that first attempt at TC39 decorators proposal was entirely revised and replaced with a very different decorators proposal. The "Decorators 2: Electric Boogaloo" proposal has actually made it to Stage 3 in TC39's proposal process this time which means that Typescript is going to be under pressure to add "real" decorators and remove the "fake" decorators that Angular currently relies on. I don't know how hard it would be for Typescript to support both medium/long-term but the transpilation backends for the two proposals are rather different to my understanding. (The new proposal is simpler, at least.)

Angular can certainly migrate to "real" decorators any day now, but my criticism stands that they could have already switched to the desugared form of the new proposal already (which resembles the desugared form of Python annotations) and have been better prepared for a migration. I've got a feeling part of the reason they haven't prepared for such a migration already is that maybe the DI is using too much Typescript-specific support in the "fake" decorators that maybe isn't likely to get carried forward into the "real" decorators.

Re: Angular v14 is now available

#83

Post by veidr »

WorldMaker wrote: post #82
veidr wrote: post #76

Earlier quoted context omitted.

Yeah, that has always weirded me out, too, but I have assumed that because Angular is one of TypeScript's largest and most significant customers, that the flag is highly unlikely to actually be removed. (?) I'm just guessing though.

My understanding is that Babel already removed support for similar decorators to the ones Angular uses because that first attempt at TC39 decorators proposal was entirely revised and replaced with a very different decorators proposal. The "Decorators 2: Electric Boogaloo" proposal has actually made it to Stage 3 in TC39's proposal process this time which means that Typescript is going to be under pressure to add "rea…

Thank you; that is very interesting.

I do think TypeScript's goal to be faithful to / eventually consistent with upstream ECMAScript would outweigh maintaining the current decorators for Angular.

So perhaps the most likely outcome is that TypeScript will at some point announce the deprecation of the current decorators, and this will cause Angular to have to migrate as you suggest.

Re: Angular v14 is now available

#84

Post by 7speter »

jmkni wrote: post #39
flakiness wrote: post #29

Earlier quoted context omitted.

FYI there is 10 Angular vs 99 React (# of word occurrences) in a recent "who's hiring" thread [1]. [1] https://news.ycombinator.com/item?id=31582796

There’s a whole world that exists outside of the Hacker News bubble :)

This can go either way for either tool

Re: Angular v14 is now available

#85

Post by pjmlp »

azemetre wrote: post #81
Zetaphor wrote: post #80

Earlier quoted context omitted.

I work for a Fortune 500 who has clients who range from Fortune 500 to Fortune 1000, I see TONS of Angular throughout the organization. There's also React, but a lot more Angular being paired with Java. Without data we're all just sharing anecdotes colored by our individual experience.

While that’s fair react still absolutely dominates the FE world, until proven otherwise I have a hard time believing angular is more popular or even close. I’d bet money on it if possible. Boot camps, job listings, conferences, paid learning materials, etc all favor react in numbers.

Those numbers across the world are?

Re: Angular v14 is now available

#86

Post by Gigachad »

jcadam wrote: post #33
luisgvv wrote: post #16

Earlier quoted context omitted.

The company I work on has a couple of projects built with Angular, however we are shifting to use React. The reason being: no one around the company likes maintaining those projects because they hate the framework and we haven't been able to hire people willing to learn/work with Angular. I love the framework as it has almost everything you need out of the box. At the beginning I hated it but as any tool/language onc…

When I see Angular in a job description, I think "this is a legacy maintenance job." So not surprised you have trouble hiring :).

Even if they stereotypes aren’t true. They are still extremely damaging to the future of Angular. I also feel the same when the entire history of me hearing angular is of converting old angular 1 code to react.

Re: Angular v14 is now available

#87

Post by Gigachad »

iueotnmunto wrote: post #9
askonomm wrote: post #3

Earlier quoted context omitted.

Because of the whole "master" meaning a slave owner thing that the progressive left seems to think it means and it apparently hurt enough feelings to make it a movement (default main branch on Github repos is now also "main" because of this), and then you have companies that desperately try to be hip and cool, and they do this to get social clout. The whole thing is pretty sad if you ask me, but what do I know.

It takes a few minutes to switch. Maybe a bit more to rebind all CI scripts etc in a project as large as react. There are some things that I don't fully get (slavery was never big in my country). It takes a few minutes of effort to not be an asshole (real or perceived), so I just do it rather than thinking to much about whether or not the wider population should be offended or not.

Not wanting to be seen as an asshole is how we end up with a never ending stream of bullshit because no one is brave enough to stand up. How much time has been wasted on feel good crap that serves only to give the illusion of caring.

Big tech is happy to rename their git branches while doing nothing about the actual evil they commit.

Re: Angular v14 is now available

#88

Post by JohnL4 »

dmitriid wrote: post #28
Karawebnetwork wrote: post #12

Earlier quoted context omitted.

This has nothing to do with left/right. This is a racial issue. People of color exist along the entire political spectrum.

Switching master to main has literally nothing to do with the imaginary (in this particular case) racial issue. Master bedrooms and master records exist. People master their trades. And so on and so on. My understanding is that the absolute vast majority of people of color couldn't care less if git branch was called master or main.

Might want to guess again on "master bedroom".

https://www.homelight.com/blog/buyer-master-bedroom/

Re: Angular v14 is now available

#89

Post by dmitriid »

JohnL4 wrote: post #88
dmitriid wrote: post #28

Earlier quoted context omitted.

Switching master to main has literally nothing to do with the imaginary (in this particular case) racial issue. Master bedrooms and master records exist. People master their trades. And so on and so on. My understanding is that the absolute vast majority of people of color couldn't care less if git branch was called master or main.

Might want to guess again on "master bedroom". https://www.homelight.com/blog/buyer-master-bedroom/

Which part of that meandering article should make me "want to guess again"?

Though I like this sentence: "So it’s not so surprising that the masterminds at Sears came up with the master plan: As masters of their craft, they mastered the art of capturing the imagination of the American homebuyer."

Re: Angular v14 is now available

#90

Post by hellojesus »

mhoad wrote: post #74
hellojesus wrote: post #72

Starting with front end: angular or react? Seems like a good time to make a decision.

Angular comes with the advantage of you can learn “the angular way” and it will always be applicable. With React every time you pick up a new project you don’t know what you’re going to get. I also have some serious doubts about the long term viability of React for what it’s worth. They made some choices early on in the project about how they decided to integrate with the wider web platform that made a lot of sense a…

Thanks!
Post reply on HN