5 ms·

As an ex-AngularJS developer, who worked on porting a LARGE app to Angular - if you're in that boat, look into just rewriting in Vue. It's similar to AngularJS

As an ex-AngularJS developer, who worked on porting a LARGE app to Angular - if you're in that boat, look into just rewriting in Vue. It's similar to AngularJS (more so than Angular) but with some extra niceties.

paaaaaaaaaa 5y ago
We were very close to doing the same but then we discovered Svelte. Svelte has been a dream to work with so far.
tdekoekkoek 5y ago
I worked on AngularJS and moved to Angular ever since 2+. It is a great platform and actually similar to Vue in some respects. No reason to abandon Angular although Vue and others are also good.
- bdcravens 5y ago
  Angular is so different some AngularJS that it's really a different framework. At that point, as long as you're switching to a new framework, you should assess them all equally according to your needs.
  - hbn 5y ago
    I work in Angular, and yeah it's worth noting that Angular can be kind of exhausting to keep up with. While they haven't done as major of a breaking change as the jump from AngularJS to Angular 2 since then (I honestly don't even know why they have the same name, other than cause people knew the name), their release cycle is pretty fast, and there's entire websites dedicated to giving you bullet-point checklists of all the things to change/check as you upgrade from version to version. I'm only a tad familiar with Vue, but it seems like you wouldn't have as many curve balls thrown at you by committing to that framework. Which makes sense with it being essentially 1 guy's project, rather than a giant like Google (who famously is not one to care for backwards compatibility)
bob1029 5y ago
I used to do angular - went for a ride on the first ~3 versions of their rollercoaster. For me, Angular was a fantastic set of training wheels but I eventually hungered for more direct control over my circumstances. Moved to RiotJS for a few years, but then it got a little bit complicated/weird from our perspective. These days, I just do vanilla JS/HTML/CSS. In some cases we serve our pages using server-side rendering techniques via Blazor, so there is no tricky state synchronization game to play over the wire. But, Blazor is mostly just doing what PHP used to do for us. We aren't diving into their component/binding ecosystem any further than we need to. Biggest advantage with a vanilla stack is that you will never get trapped on an old version of one of these things and be forced to "migrate" (i.e. "rewrite") your application each time. Vanilla also means you don't have to submit yourself to any arbitrary package manager, build toolchain, et. al. Your entire product can fit inside 1 html document that just instantly works in any browser.

paaaaaaaaaa 5y ago

We were very close to doing the same but then we discovered Svelte. Svelte has been a dream to work with so far.

tdekoekkoek 5y ago

I worked on AngularJS and moved to Angular ever since 2+. It is a great platform and actually similar to Vue in some respects. No reason to abandon Angular although Vue and others are also good.

bdcravens 5y ago
Angular is so different some AngularJS that it's really a different framework. At that point, as long as you're switching to a new framework, you should assess them all equally according to your needs.
- hbn 5y ago
  I work in Angular, and yeah it's worth noting that Angular can be kind of exhausting to keep up with. While they haven't done as major of a breaking change as the jump from AngularJS to Angular 2 since then (I honestly don't even know why they have the same name, other than cause people knew the name), their release cycle is pretty fast, and there's entire websites dedicated to giving you bullet-point checklists of all the things to change/check as you upgrade from version to version. I'm only a tad familiar with Vue, but it seems like you wouldn't have as many curve balls thrown at you by committing to that framework. Which makes sense with it being essentially 1 guy's project, rather than a giant like Google (who famously is not one to care for backwards compatibility)

bob1029 5y ago

I used to do angular - went for a ride on the first ~3 versions of their rollercoaster. For me, Angular was a fantastic set of training wheels but I eventually hungered for more direct control over my circumstances. Moved to RiotJS for a few years, but then it got a little bit complicated/weird from our perspective. These days, I just do vanilla JS/HTML/CSS. In some cases we serve our pages using server-side rendering techniques via Blazor, so there is no tricky state synchronization game to play over the wire. But, Blazor is mostly just doing what PHP used to do for us. We aren't diving into their component/binding ecosystem any further than we need to. Biggest advantage with a vanilla stack is that you will never get trapped on an old version of one of these things and be forced to "migrate" (i.e. "rewrite") your application each time. Vanilla also means you don't have to submit yourself to any arbitrary package manager, build toolchain, et. al. Your entire product can fit inside 1 html document that just instantly works in any browser.