Waltz UI migration

[meenakshi-saraf-db]

Waltz UI is on the obsolete stack of Angular1( angular v1.8.2) and in past attempts have been made made to migrate some components to Svelte (svelte 3.52.0). Waltz UI needs to go migrate to new technology stack to meet the organization internal requirements for vulnerability management and modernization. This is an important undertaking and will need through analysis. Introduce React using the the bridge pattern and continue to iteratively migrate components.

[kamransaleem]

hi @meenakshi-saraf-db

Thanks for sharing, I’m a bit concerned, though, about the move to React instead of continuing with Svelte, which seemed like a more natural evolution for Waltz.

Svelte’s lightweight architecture, smaller bundles, and minimal runtime make it ideal for a product like Waltz that doesn’t rely heavily on complex client-side state. It also has far less boilerplate and a lower maintenance burden. In contrast, React adds significant complexity — dependency sprawl (React, ReactDOM, router, state libraries), heavier build pipelines, and a steeper learning curve — all of which could slow adoption and increase upkeep effort over time.

Would it be possible to revisit the earlier Svelte evaluation and compare it head-to-head with React across migration complexity, bundle size, and long-term sustainability before committing to the new stack?

Happy to help with that analysis if needed.

[davidwatkins73]

I agree that migration away from Angular 1 should continue.

However, I do not agree with the statement: 'past attempts have been made to migrate some components....' (emphasis mine).

Approx 30% of the app has already been successfully migrated to Svelte by 2 developers over a relatively short time period given their other commitments.

A detailed list of pros and cons should be produced with regards to introducing more dependencies and complexity to the application code. This concern is especially warranted if React is being evaluated, due to the large ecosystem that get's brought in alongside it.

There is a notable shift towards lightweight frameworks/libraries and leaning more heavily on the the native capabilities of ever-green browsers. Embracing another all-in-one solution (like Angular and like React) misses an opportunity to do a genuine technology overhaul/modernisation.