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

Angular 9.0

blog.angular.io

Post reply on HN
Print view View original

301–308 of 308 posts

Re: Angular 9.0

#301

Post by orange8 »

doczoidberg wrote: post #172

Just want to say that all the Angular React comparisons are dumb. It is comparing apples to oranges. Angular is a bigger framework for developing more complex stuff. Therefore of course there is a steeper learning curve. Here are comments like "react is so much more easier because it is just functions". Why not just using vanilla js because you have nothing to learn then? Or just use binary code? It is just 0 and 1.

The comparisons are valid because for 99% of the web apps out there, the makers could have gone with either angular or react.

Regardless of the underlying philosophies, the choice between React, Vue and Angular is a very real one businesses have to make everyday, so it makes sense to compare them.

Re: Angular 9.0

#303

Post by gridlockd »

hmcdona1 wrote: post #292
gridlockd wrote: post #274

Earlier quoted context omitted.

I don't think so, the point is that Angular breaks user code often, whereas React rarely does. An Angular 2+ app built in 2016 (when Angular 2 came out) wouldn't build anymore. An Angular 1 app didn't even need a build step, so that would probably still work fine.

lol it would work fine. I've had a joke app running Angular 2.0 in production for years. The code doesn't just expire and break. If you upgrade to Angular 8 in your package.json without running the upgrade schematics, yes it will break...because there were breaking changes. In 2016 React was on version 14. Are you telling me that from version 14 to 16.12 React has had ZERO breaking changes? Because they definitely ha…

> I've had a joke app running Angular 2.0 in production for years. The code doesn't just expire and break.

Nobody claimed that stuff which has been built and never touched again stops working.

> In 2016 React was on version 14. Are you telling me that from version 14 to 16.12 React has had ZERO breaking changes?

No, I'm not saying that. If they had zero breaking changes, I would have said exactly that, it would be remarkable.

Nevertheless, there have been very few breaking changes in that timeframe[1] and they are highly unlikely to affect if you're doing ordinary stuff.

[1] https://github.com/facebook/react/blob/master/CHANGELOG.md

> Because they definitely haven't. That ecosystem has also changed recommended patterns countless times.

You can just ignore the "ecosystem". You don't need it. React pretty much only does one thing. It doesn't impose an architecture on you. If you want to go all-in on the ecosystem, maybe it's as bad or worse than Angular. That's besides my point.

> Same goes for any library or framework across major versions...

No it doesn't. Some or even most people working with Javascript are completely out of touch with software engineering practices outside of the web bubble. Breaking changes are supposed to be avoided at great cost. Of course there's no real incentive for that if you're a random person pushing something to npm, or if you're Google and your business model is selling users instead of software.

Re: Angular 9.0

#304

Post by pjmlp »

e12e wrote: post #287
momento wrote: post #178

Earlier quoted context omitted.

Angular has a lot of unique concepts that people find difficult to wrap their heads around. The Observable pattern, decorators, typescript, etc. When you throw things like NGRX and effective management of state / side-effects in the mix; things get exponentially more complex and difficult to scale. I have personally witnessed companies take guys who have been slapping together "apps" in jQuery / .NET for the past 10…

> "we're going with Angular because we're a Microsoft house" Is ms invested in Angular? It's a Google project, isn't it? Is it first-party in dot.net? I though that was Blazor?

Angular is the framework of choice for most Java/.NET shops, because it is basically JEE/Spring/WebForms/MVC, but in JavaScript, besides being written in TypeScript which is quite appealing.

Before Angular, those developers would probably have chosen Knockout.js instead.

Re: Angular 9.0

#305

Post by Phenix88be »

bdcravens wrote: post #255
Phenix88be wrote: post #136

After 2 years of Angular madness I will send my resignation and I hope I will never work with it again. My app is a big stack of workaround stuff that might break anytime. Because that is how angular work. Some stuff work in a context and doesn't in an other. Nobody's know why ! They have so much issue on Github that they need a bot to close them after a while. They hope the bug disappear by himself ?

What framework would you use to avoid those workarounds (or others in different parts of your app)?

I want to move away from the frontend job et do backend stuff. I really hope to stay away from javascript for a while.

Re: Angular 9.0

#306

Post by levythe »

jaywalk wrote: post #249
node-bayarea wrote: post #246

Earlier quoted context omitted.

Use things like Svelte. It's a framework that lets you hack. You don't need 'best practices'.

>It's a framework that lets you hack. Translation: It's a framework that does less.

This isn't a bad thing if the things the framework does aren't terribly useful for what you want to accomplish.

Re: Angular 9.0

#307

Post by dfsegoat »

ErikAugust wrote: post #99
filoeleven wrote: post #85

Earlier quoted context omitted.

AFAICT the upgrade path is still the same (0) and...it looked pretty painful when I first looked at moving from 1.x to 2. I maintain a sizable 1.x codebase and am deciding what to move to, since 1.x is dead next year. I just don’t see a good reason to go to 2+. It’s a different framework. All of the UI libraries we built upon (ng-grid, angular-ui) are either gone or different enough that we will have to redo all of o…

AngularJS is dead next year, but really that doesn't stop you from using it indefinitely. Of course it can be fun to rewrite everything.

FWIW, A lot of AWS Console apps are on 1.5.x. TurboTaxes interface is still using it as well I believe.

Re: Angular 9.0

#308

Post by treeman79 »

jcheng wrote: post #16
treeman79 wrote: post #10

Earlier quoted context omitted.

Saw a 2 man team that got features done in a couple of weeks on jquery move to angular and turn into a 15 man team that took months on each feature. Management was very happy with how modern the stack felt Sales came to a halt for 2 years since features came to a halt. Turns out Angular is freaky hard to do right.

Was this AngularJS (i.e. Angular 1) or Angular 2+? I could believe it either way, just curious.

Angular 5-7
Post reply on HN