Just to be clear, Angular is now also built on components, transpiled and a rich toolset, including debugger, unit testing, end-to-end tests, CLI with scaffolding for adding new components/services etc.

Building using components will also help prepare the new UI for a plugin architecture where Solr contribs/plug-ins add their own UI menu items and screens dynamically (dynamic loading vs build-time compiling).

The old UI grows with more screens and features week by week so the burden of switching does not become smaller if we wait.

Upayavira, moving from jQuery to AngularJS took the approach of building a clean parallel  code base, with the downside of years of maintaining two UIs. Do you see any better approach this time around?

Jan

Sendt fra min iPhone
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB