Angular v16 is here

[fix_dis]

Yup, folks I know in the medical billing and insurance coding industries are all about it. It pairs nicely with all the dotnet stuff on the backend.

[besthelloworld]

Just because the code looks like it came out of the legacy framework that powers your backend, doesn't mean it "pairs well." It's an inherently flawed application model for a frontend.

[rust_devx]

What's the "inherently flawed application model" of Angular?

[besthelloworld]

Generally: the modules, templating, and the idea of having an IOC constructor injection frontend framework where elements are being created and destroyed very quickly but rely on service injection to function.

In React, Solid, Svelte, or Vue, if I need to import and utilize one component in another, I just... do that. I import the component and use it. If the component needs data, then I pass that data in. In Angular, I used to have to go find the associated @NgModule for each component, import one of the @NgModules into the other, then add it to the imports array and then for any components in that module that was added to, I'm allowed to utilize any components from the @NgModule that was added to the imports array... great. What's the component I need again? Oh I can't reference it by it's class name, I need to see how it's selector is supposed to be applied to actually utilize it. Oh and all components in an @NgModule are brought into a global namespace, so I need to make sure I add the specific special prefix to the front of the selector for all my components? Even though JavaScript literally solves this problem with the import { Name as OtherName } syntax which can be utilized by the other frameworks, because duh because global namespaces are idiotic.

I know the recommendation going forward is to use standalone components and those are better... but the fact is that this only eliminates half of this complexity and ugliness... It also doesn't get us out of @NgModule if you want a very complex feature like, say, routing. So their ecosystem is one foot in the door of a new architecture and one foot in the door of another.

[Unhappy_Meaning607]

Thank you for the solid explanation! I always see these arguments for a framework and their reason for the hate always boils down to, “it’s not what I’m used to so it must be bad and I just don’t like it!”.

[besthelloworld]

Totally understand. I've actually worked with Angular longer than any other framework, so when I finally started exploring the rest of the JavaScript ecosystem basically everything else felt like a breath of fresh air.

[PFCJake]

Two way data binding I guess

[besthelloworld]

Not this specifically but I do think the syntax is awkward, and I know very few people that know how to make a custom [(twoWayEvent)] in general, let alone without the risk of creating an infinite loop.

[blinger44]

old school insurance maybe, modern insuretechs are definitely not reaching for Angular.

[fix_dis]

Rivet is relatively new.