With the rise of NoSQL, Is it more common these days to have a webapp without any model?
I don't think "NoSQL" has anything to do with "no model".
For one, MVC originated in the Smalltalk world for desktop applications, long before the current web server architecture (or even the web itself) existed.  Most apps I've written have used MVC (including the M), even those that didn't use a DBMS (R or otherwise).
For another, some kinds of "NoSQL" explicitly have a model.  An object database might look, to the application code, almost just like the interface that your "SQL RDBMS + ORM" are trying to expose, but without all the weird quirks and explicit mapping and so on.
Finally, you can obviously go the other way, and write SQL-based apps with no model.  It may not be pretty, but I've seen it done.
With the rise of NoSQL, is it more common these days to have a webapp without any model and process everything in the controller? Is this a bad pattern in web development? Why should we abstract our database related function in a model when it is easy enough to fetch the data in nosql?
Note
I am not asking whether RDBMS/SQL is not relevant because that will only start flamewar.