So far, not a fan of Angular

[Mike Austin]

Things were going well for a bit making a few components. Then I wanted to fetch data on a route change. It’s still not working. Observables, signals, RxJS… it can’t be that complicated.

Oh, computed also. I mean there can be hairy stuff with React useMemo, but as least I can just plain values and React will handle the reactivity.

It’s time for a real reactive language, not these libraries tacked on. I don’t want to think about dependencies. I don’t want to think about imperative signals, memory leaks, and patterns you need to follow for things not to completely break.

[Mike Austin]

There's no input/props spread-type operator in Angular? In React I've built component delegation hierarchies exclusively spreading props:

const Button = ({ children, solid, ...props }: Delegate<...>) => {

  return (

    <View as="button" className={solid && styles.solid} {...props}>

      {children}

    </View>

  );

}

Now Button has all the props available to View - backgroundColor, etc. It's all type safe. I don't know how to do this in Angular... yet?

[Mike Austin]

Still not a fan of Angular. Import your imports into components? Import like 5 things to get basic forms working? Google Gemini has helped find how to do things, but often wrong because of different versions of Angular and Material. I started the project only a few days ago and there were already vulnerabilities to patch.

The only think I like about it so far is the @for () {} @else {} @empty {} syntax, which is not new – similar to Microsoft's Razor language. I say this because in React the { ? : } can get a little unreadble with nested (s and {s trying to match them.