95 pointsby Klaster_16 hours ago15 comments
  • vyrotek6 hours ago
    I must admit, modern angular has been a pleasure to use. It's a shame that the ecosystem is a little rough. Luckily you get so much out of the box already.
    • Klaster_16 hours ago
      Same experience here.

      I wish Angular dropped their weird compiler that's tight coupled to tsc and moved into more pluggable approach so you can use it with whatever TS compiler. App and unit test cold build times are still crap, but at least with a coding agent you care about this less.

      • spankalee5 hours ago
        Angular should ditch the compiler altogether - it really hinders them in so many ways, especially now with AI-codegen where tools have to specifically choose to do the work to integrate the Angular toolchain instead of using plain TypeScript and HTML.
        • embedding-shape4 hours ago
          "plain TypeScript"? Just like Angular, TypeScript depends on a compiler too, regardless of where in your toolchain it is, unless I missed browsers somehow being able to straight up run TypeScript nowadays. Bit ironic to cite "ditch the compiler" as the reason to switch from one compiler to another.
        • bpavuk4 hours ago
          [dead]
    • majora20074 hours ago
      What is rough in the ecosystem? I haven't had any issues finding packages. Most packages have been keeping up with the signal trends as well.
    • mhitza5 hours ago
      Are projects still chosing to pick RxJS (or equivalent) which make the code heavily layered and a pain to debug?

      Or has sanity reached the Angular ecosystem by now?

      • jonkoops4 hours ago
        I believe Signals are the go-to now, but surely RxJS is still present for complex use cases. Are Zones fully gone?
        • vyrotek4 hours ago
          As of v21, zoneless is the default

          https://angular.love/angular-21-whats-new

        • andriy_koval3 hours ago
          Now we have promises, observables and signals.

          I would be more happy if it would be just one of those..

          • halflife2 hours ago
            Each one of these solves a different problem.

            Promised - async

            Observables - streams

            Signals - reactivity

            • wartijn_25 minutes ago
              In theory that’s true (although observables are for reactivity too), but Angular uses observables for its http library and http requests are very much not streams. It’s one of the main downsides of working with Angular, the http library is mediocre and does come with the added overhead and complexity that rxjs brings.

              Until this release (if you only use stable features) using forms meant dealing with observables too, even if you just want to read data when submitting a form and validating some data on change/blur.

              And often you’ll find that your data from promises, observables and signals need to interact with each other, which can be annoying.

              Fortunately the situation with signals and their async usage is improving, and iirc the Angular team wants to make rxjs optional, but until it is Angular can be a confusing mess on some points.

            • azangru36 minutes ago
              > Observables - streams

              > Signals - reactivity

              The r in rx stands for reactive.

      • thevillagechief5 hours ago
        Everything is signals now.
      • throw3108223 hours ago
        The problem with Angular is that the http client service used to return observables by default and that made people think that you had to use them as such. It was a mostly useless, massive pain. Working with Angular became a pleasure the moment we decided to just cast our service calls to promises.

        For the rest, RxJS is cool where you actually need it and want it.

  • hmokiguess24 minutes ago
    I enjoyed Angular before React, had a good run with it, it was a vibe, now if I'm being honest I totally forget it ever existed. Not to praise React either, lately I've been actually digging the htmx way, though I feel like the battle is now which framework/language is the agent more proficient with and the static/compiler level tooling can help catch mistakes.
  • kaicianflone4 hours ago
    Wow Angular Aria looks fantastic. Even have full docs for the more complicated scenarios like autocomplete. Can't wait to get this in my hands and see if it replaces the custom screen reader autocomplete I had to make.
    • embedding-shape4 hours ago
      Maybe I'm dumb, but I go to: https://angular.dev/guide/aria/overview#showcase and try out the keyboard controls, somehow they've decided that those elements should be navigated with the arrow keys instead of much more commonly used tab and shift+tab? Even the tabs from their own documentation, right above that example, also uses tab/shift-tab for moving focus between them.
      • miguel-munizan hour ago
        A lot of those behaviors aren't their decisions, they're specs from the W3C[1]. The tab behavior may be an oversight though, the W3C page specifies subsequent tab presses should move the focus outside of the tab list, but it could also be an exception. I'm not an expert but sometimes there are exceptions made due to the realities that operating systems, browsers, and screen readers all have varying degrees of support for accessibility features. Accessibility is a very deep rabbit hole, which is why these kind of libraries are popular in the first place.

        [1] https://www.w3.org/WAI/ARIA/apg/patterns/toolbar/

        [2] https://www.w3.org/WAI/ARIA/apg/patterns/tabs/

        • embedding-shape41 minutes ago
          Yeah, sure, I'm well aware of that, it was more a reaction to parent saying that specifically the accessibility stuff looks amazing, but seems they haven't even nailed the basics yet, so I'm wondering where the amazing parts are.

          With that said, the autocomplete example which parent mentioned, does seem well made. Was just surprising to see such a basic mistake in the documentation for the accessibility stuff, one would think they would take extra care to get it right there, as that's what people (and LLMs...) will read and retain.

  • etothetan hour ago
    I haven't been involved in Angular for quite some time. As someone who uses other JavaScript frameworks (Vue, React, Svelte), what am I missing out on? I'd be curious to hear from people who would pick Angular over any of the other big frameworks.
    • eatsyourtacos19 minutes ago
      I would just say in general Angular is best if you basically want to build an old school application as a website.. and especially if you kind of hate javascript and web development but focus on the backend as the main part.
  • TheChaplain5 hours ago
    I like Angular, it feels a bit like Django. Easy to use with everything included.
    • sgt4 hours ago
      Or I mean, you could just use Django (or some faster backend with templating and SSR). Using that with htmx you get the SPA experience and still without the madness of an actual rotten JS ecosystem.
  • majora20074 hours ago
    Really excited for this. I've been dying to use signal-forms and resources since they were experimental. Once I got on the signal train, I could never go back and having to use RxJS for forms became a major pain point.
    • darkteflon3 hours ago
      Could you say more about signals? Is it are all analogous to, say, game engine signals paradigms (eg Godot) - components at any depth emit signals and any other component can subscribe? Or something totally different?
  • healthDev4 hours ago
    Angular has made my programming career joy and it has not felt like work at all, all the best to angular dev team! Nothing better than getting to work with favorite language, learning better and getting paid :D
  • pan693 hours ago

       import {signal} from "@angular/core"
       import {form} from "@angular/forms/signals"
    
    So, signal comes out of core and form comes out of forms/signals. This must be a terminology thing I don't get.

    Other than that. Looking forward to try Angular again after a decade of absence. I think it looks pretty good.

    • majora20072 hours ago
      Signals are a privative data structure in Angular, hence core. Signal-based forms are part of the Forms module. You aren't using forms, you don't get the overhead.
      • exac2 hours ago
        primitive
    • vyrotek3 hours ago
      There are a lot of ways to do Forms in Angular. I assume that's importing the new "Signals" based form.
  • fsuts2 hours ago
    How does modern angular performance compare to the alternatives? Is it as fast?
  • merb4 hours ago
    the biggest problem in angular is that it is so hard to use a custom toolchain, i.e. not their angular/cli product instead mix it with other stuff in lets say vite
    • zcdziura4 hours ago
      What kinds of features or workflows are you missing that Angular's CLI doesn't cover? Or is it just that you're used to Vite (or something else) and wish you could use that instead of Angular's own tooling?

      I'm not on the Angular development team or anything, though I do use Angular at $DAY_JOB and I'm overall perfectly fine with the framework and its tooling. However, the grass might be greener elsewhere; I'm just not familiar with it!

    • anthonypasq4 hours ago
      for many people this is the biggest bonus
    • equasaran hour ago
      explain your use case, I always wonder what kind of scenarios people do have, it is something easily solved? it is complicated? what is stopping you?
  • shay_ker4 hours ago
    Seems like Angular has gotten better since v2 (my last experience).

    Has anyone done a modern Angular vs. React comparison that's not an AI slop article?

    I'm also curious if it's "simple made easy" for performant applications. React is arguably "simple made hard", but there are notable, highly performant applications written with it (Linear comes to mind).

    • vyrotek4 hours ago
      Angular Control Flow alone is a massive QoL improvement compared to the React way to do template conditions, switches, loops, etc.

      https://angular.dev/guide/templates/control-flow

      • shay_ker2 hours ago
        I do wonder - why not add this to jsx?
        • hungryhobbitan hour ago
          Because the React team 100% cares about miniscule optimization enhancements, and 0% about otherwise making the tool better.

          Source: Just look at what's been in the last couple years of updates.

    • zcdziura4 hours ago
      Modern Angular is MUCH nicer to use than the v2 days (or even the v4 days when I first started working with it). A lot of the required boilerplate is unnecessary nowadays. And even RxJS and NgRX are becoming less and less necessary to use too, which is great.
  • woodpanel2 hours ago
    Out of curiosity I’ve progressed away from Angular around 2018. My peak spa-ish reduxian state management experience was building an NgRX combo with @ngrx/effects for side effects.

    Till this day I remember this fondly as it gave me so much ease of control of the application’s many complex states. Especially when I nowadays deal with all sorts of false-prophets in forms of hooks and what ever reactive primitive du-jour (don’t get Me wrong they are 80% of the time the better choice, it’s just that they don’t scale).

    What’s today’s version of complex state management in Angular-Land?

  • partsch4 hours ago
    Using angular in 2026 is mad :D
    • thm763 hours ago
      When I look at job postings and see "React" I go "ugh" these days and find myself looking for Angular instead. That's the complete opposite of my thoughts from just two years ago.

      I would still rather use something else (instead or React or Angular) but 1) most jobs in my area are asking for one of those, and 2) I'm actually starting to lean towards Angular even for personal projects.

      Angular is great these days, and they're making really nice improvements.

      • rezonantan hour ago
        Absolutely same. I have been with Angular the whole time and it's only getting better and better.

        I hope more teams give it serious consideration as I just am not excited about dealing with React and it's numerous spinoffs.

    • javier1234543214 hours ago
      Have you used it in the last 8 years? Its actually quite a good piece of software.
  • coolThingsFirst4 hours ago
    Overkill. React mogs.
  • hnarayanan2 hours ago
    Wow, a post about Angular published on Medium!