What did you not like about JSF? I mean, the whole EE part had its fair share of flaws, but I think the JSF model was way ahead of its time, and I still think that (model-wise, not necessarily implementation-wise) it is just unbeatably productive.
View Model Lifecycle as starters, the amount of HTML, CSS and JavaScript boilerplate code that got generated leading to lenghty debugging sessions, and the way most JSF frameworks were basically incompatible with each other.
Example, using RichFaces, and then trying to use something from PrimeFaces, IceFaces, or something else Faces, was always open to surprises mixing their lifecycle expectations.
I was involved with a RichFaces based JSF framework, during three years, and afterwards going back to something like plain JSP and tag libraries felt quite refreshing.
.NET and Java ecosystems are the only ones with tooling and developer experience that is somehow comparable to the Xerox PARC world. Note for the pedantic, comparable, not exactly the same.
Given the way .NET was born, there is a kind of yin/yang with both platforms.
Some scenarios or guest languages are better in other platform, while some other scenarios or guest languages are better in the other one.
Given this, when would I suggest .NET over Java?
It is closer to C++ in language features (as CLR was designed to accomodate C++ as well), and C# is getting some of those runtime features exposed since C# 7.
Because of this, and XNA/Unity, also got the love from many game studios (Capcom even has their own fork).
Microsoft also understands GUI much better than UNIX shops, so even with the ongoing GUI civil war in Redmond, most of the GUI offerings are still better than what Swing and JavaFX are able to do out of the box.
Blazor looks really cool as technology, however I was in the trenches with WebForms and JSF, so not really something I would like to experience again.