4 ms·

To me it goes beyond the looks. Angular terminology and semantics were always very alien. React is no angel either, but it seems influenced by older, more teste

To me it goes beyond the looks. Angular terminology and semantics were always very alien. React is no angel either, but it seems influenced by older, more tested concepts (FP and such). That said, I think client side UI/UX is about to see yet another large wave of change. Hearing chats from solidjs devs make me feel that there's a whole new and saner space to describe simple and fast programmable interactions.

cies 2y ago
React does very little. You still need other libs to go with it before you can compare the set of them to Angular.
- agumonkey 2y ago
  I stopped following the angular world long ago, how much is included in it ? (on my way to read their docs but I'm still open to a short summary :)
  - pjerem 2y ago
    Routing, form handling, dependency injection, testing, services, http requests processing, localization etc etc … In fact the "write a component" part is the center of React but only one of the features of Angular. In my experience, the big advantage of Angular is that you rarely need anything else and so it’s totally possible and reasonable to write a full fledged application without any other dependency than Angular itself. In $prev_job, we had nothing else in package.json than angular, some internal libs and the internal design system (which were exposed as angular providers) and some wysiwyg editor like quill. It’s far from the funniest framework, but for writing boring things in team setting, it’s actually pretty good. In fact having worked on the oldest AngularJS framework, it’s very interesting how it made a full 180 from "magic everywhere" to a boring "enterprise" framework. I would never make a side project in angular because it can be pretty boilerplatey but in a team of 3 or more devs in a multi months dev project that I’ll have to maintain for years, that’d be my choice. Except if I can reasonably do it without an SPA beforehand but that’s a totally inaudible proposition in corporate world anyway.
pjerem 2y ago
I’m going to be the devil’s advocate because I’m from the team "no SPA at all unless you have a real need like real time" but to me, Angular is the less worse when it comes to writing SPAs in teams. Clumsy and hard to learn ? Sure. The code looking less cool than other frameworks ? Of course. Unbearably slow compiler ? Check. But at least you got a full fledged, batteries included framework, with a powerful DI system and an established architecture to follow. Not the funniest framework but it works. The only powerful thing but also big flaw with angular is that they deliberately expose a lot of the framework internals with a very neutral documentation that never explains that you shouldn’t touch this or this in most cases. It allows very nice and clean extensions of the framework but, oh my, if you inherit a codebase from a "smart guy" who knows the framework inside and out and "did better" than the boring angular architecture, then good luck. I know this can happen in any codebase and I’ve seen it everywhere but Angular exposes so much things that you can make horrible things. But in a team who have a boring CRM or SaaS front end it’s a pretty good framework to use. Except if you can do everything server side.
- agumonkey 2y ago
  > an established architecture to follow. Not the funniest framework but it works. yeah, that's worthy, especially in teams, it avoids friction most of the time

cies 2y ago

React does very little. You still need other libs to go with it before you can compare the set of them to Angular.

agumonkey 2y ago
I stopped following the angular world long ago, how much is included in it ? (on my way to read their docs but I'm still open to a short summary :)
- pjerem 2y ago
  Routing, form handling, dependency injection, testing, services, http requests processing, localization etc etc … In fact the "write a component" part is the center of React but only one of the features of Angular. In my experience, the big advantage of Angular is that you rarely need anything else and so it’s totally possible and reasonable to write a full fledged application without any other dependency than Angular itself. In $prev_job, we had nothing else in package.json than angular, some internal libs and the internal design system (which were exposed as angular providers) and some wysiwyg editor like quill. It’s far from the funniest framework, but for writing boring things in team setting, it’s actually pretty good. In fact having worked on the oldest AngularJS framework, it’s very interesting how it made a full 180 from "magic everywhere" to a boring "enterprise" framework. I would never make a side project in angular because it can be pretty boilerplatey but in a team of 3 or more devs in a multi months dev project that I’ll have to maintain for years, that’d be my choice. Except if I can reasonably do it without an SPA beforehand but that’s a totally inaudible proposition in corporate world anyway.

pjerem 2y ago

I’m going to be the devil’s advocate because I’m from the team "no SPA at all unless you have a real need like real time" but to me, Angular is the less worse when it comes to writing SPAs in teams. Clumsy and hard to learn ? Sure. The code looking less cool than other frameworks ? Of course. Unbearably slow compiler ? Check. But at least you got a full fledged, batteries included framework, with a powerful DI system and an established architecture to follow. Not the funniest framework but it works. The only powerful thing but also big flaw with angular is that they deliberately expose a lot of the framework internals with a very neutral documentation that never explains that you shouldn’t touch this or this in most cases. It allows very nice and clean extensions of the framework but, oh my, if you inherit a codebase from a "smart guy" who knows the framework inside and out and "did better" than the boring angular architecture, then good luck. I know this can happen in any codebase and I’ve seen it everywhere but Angular exposes so much things that you can make horrible things. But in a team who have a boring CRM or SaaS front end it’s a pretty good framework to use. Except if you can do everything server side.

agumonkey 2y ago
> an established architecture to follow. Not the funniest framework but it works. yeah, that's worthy, especially in teams, it avoids friction most of the time