"jquery based language" doesn't make any sense.
Anyway, I'm increasingly cautious about going all-in with any framework. As soon as that framework does something you don't like, it's difficult or impossible to make a change. IMO it's safer to go with a sensibly composed collection of best-of-breed libraries. If you glue them together in the right way, you minimize churn if you hit a wall with one of the libraries and need to look for a replacement.
I've read probably the same blog post as you. But I don't get how you avoid going 'all in' with a data binding library. I mean it's going to involve itself pretty much everywhere you link I/O to presentation, which for web apps is mostly what they do. So everywhere.
So maybe you don't use data binding and that's fine for most traditional web apps, but declarative data binding is really nice for the kind of highly interactive/async web apps people want to make these days. So you are probably going to want Angular or another framework like it, and you are going to invoke these frameworks one way or another a lot.