do you know the tech and the framework matches all requirements ? why not .... you can even couple it with react and d3 if you're bored. Since Angular1 has been adopted by a lot of java companies (at least in the german speaking area) I think you're still save using it.

but I'm not a frontend-dev and this just my feeling / opinion based on my personal observations of the market. Maybe some more eager and religious people raise their torches for react, vue, ember, [add another framework here] and will explain you why it's an bad idea or good idea to follow their advices :)

I personally won't use anymore angular 1 not because it's bad just because I don't like the DSL that much and cross scope communication needs to be structured and planned before hand (try to get a communication tree so you don't end up to emit via the rootscope ... anyhow not important :)

good question, I would say do what you're comfortable with :) others may wanna stone me for that ;D .....

I'd be surprised if someone doesn't ultimately create a fork (if that even becomes necessary) keeping the same paradigms.

One of the beauties of programming is that there are as many ways to do it as there are programmers (roughly) and there are people who like doing stuff the Angular1 way.

So, to answer your question, the use cases to Angular 1 solved before are still the same use cases now; if you think that that framework is a good fit for your project, why not? It is still actively developed, according to github anyway.