My .02 for what it's worth...
One thing that's a major factor for me is that I work at a small startup and my main customer is a Support team made up of only 4 people, and I have a really good understanding of their workflows. They've been using a Service Cloud console up until now, and while it's usable, they could be a lot more efficient with a custom case management system.
I would never have tackled such a thing with Visualforce (either native or as a wrapper) but with Lightning, I'm really feeling like we can develop exactly what we need, use native Salesforce technologies, and explore mobile options for case management down the road.
Maybe frameworks like React, etc, are better in some way, but I wouldn't know because I don't know those frameworks. But just in my short time working with Lightning, my gut instinct is that it just "feels" right. I can learn it, make it do what I want, and develop a great solution using it for our Support team.
And from a maintenance aspect, there's a lot of appeal for using native Salesforce technologies because down the road if we hire additional Salesforce developers, we don't have to worry so much about finding people skilled in both Salesforce and React/etc, but can concentrate on finding somebody really good at Salesfroce development in general and they could probably pick up on Lightning pretty quickly if they don't already know it (like I am today).