• TrickDacy@lemmy.world
    link
    fedilink
    arrow-up
    22
    arrow-down
    1
    ·
    3 months ago

    I’m so glad I never had to work with angular. Those constructs always disgusted me

    • Sinuousity@lemmy.world
      link
      fedilink
      arrow-up
      8
      ·
      3 months ago

      Confusing syntax to replace confusing syntax, library dependencies that let you do nothing you couldn’t do without them. Generic solutions are always the best for specific problems, right?

    • dandi8@fedia.io
      link
      fedilink
      arrow-up
      10
      ·
      3 months ago

      For me, as primarily a backend dev, the argument was that it’s a framework, unlike React, so you get an everything-in-one solution which is quite easy to setup and use.

      Given that Google still hasn’t killed this one yet, it’s also a mature platform with plenty of articles online on how to use it.

      IIRC the license was also better than React’s, at least last time I checked.

      Not sure on what the landscape looks like today, but when I was making the choice, the internet didn’t seem to consider other solutions to be competitive with either React or Angular.

      • Eiri@lemmy.ca
        link
        fedilink
        arrow-up
        3
        ·
        3 months ago

        Vue and React are popular alternatives.

        Lit is a less popular alternative that’s 100% compatible with native WebComponents, and I’ve been interested in it ever since I first heard of it.

    • Zangoose@lemmy.worldOP
      link
      fedilink
      arrow-up
      2
      arrow-down
      1
      ·
      3 months ago

      To me at least angular makes a bit more sense than React’s way of doing things does. React tries to be functional with its components and yet it seems like they end up basically trying to mimic classes with useState and useEffect. To me Angular’s class-based approach makes a bit more sense (though I am primarily interested in backend development more than frontend so that could be why)

      It does kind of fall into a lot of the traps of Object-Oriented programming though so I can see why a lot of people don’t like it

  • OpenPassageways@lemmy.zip
    link
    fedilink
    arrow-up
    6
    ·
    3 months ago

    I think it was 5 to 6 that was a really tough one for me because we had an in-house state management library that broke with the major breaking changes to RxJS. After that was pretty much no issue all the way from 6 to 17.

    • Zangoose@lemmy.worldOP
      link
      fedilink
      arrow-up
      1
      ·
      3 months ago

      There are a few libraries we’re using that stopped being developed after Angular ~9-10 and one we use extensively with breaking changes between 10-12. Updating to 8 wasn’t too bad but for some reason Angular’s update tool didn’t actually do anything so I had to update the package.json manually and fix stuff by hand (luckily the only change was fixed with a bulk find/replace)

    • Eiri@lemmy.ca
      link
      fedilink
      arrow-up
      4
      ·
      3 months ago

      The old version, AngularJS, died. The newer Angular lives on, and I heard it’s a much better experience.

  • bleistift2@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    3
    ·
    3 months ago

    If only their “automatic” updater worked without throwing errors on every migration…