Express: yes
Neo4J: why not
Angular: rather not
Express: yes
Neo4J: why not
Angular: rather not
Express: no
Neo4J: rather not
Node: fuck no
My point: your opinion is exactly that... everyone has their own, and it's as useless as mine, in these comments, until you add some weight behind it.
Why not angular ? hmm i'd say , the angular team fucked up with version 2.x announcement. I personally don't like this atScript/Typescript thing ,It's no longer safe to begin an angular project that will have to be maintained for years as devs don't really know if angular 1.x will still be maintained by Google 2,3,4,5 years from now.
With 1.x if you were into jQuery plugins, you could easily include them into any angular project which makes development really easy. You don't need to write classes or stuff like that, just write a function , put a bit of markup into the HTML and voila, you have a functional angularJS app.
I'm still using angularjs because it's just the best MVC framework out there.React isn't a framework but a view engine. React doesn't solve any architectural problem other than the view.
Fair enough. But, when coupled with a flux implementation (like Reflux) and a router (like React Router), what do you find missing in the React toolkit?