The list of reasons and that are
enormous. A common one is that you get a view that does a horrible
query and bogs down your database, so you decide to alter the
query. Now you need a custom module for that, so why not go ahead
and just do a custom module for whatever it is you're trying to
produce?
I always weigh out the needs of the site I'm building and rather I
need views or not. If they want something as simple as a couple
latest nodes from X type in a block, then I'll just do a quick,
custom module. Why put all the weight of views in there, for
something I can do in a couple dozen lines of code? But if I
detect that this is going to be a client that wants to constantly
make changes and that, then I'll go ahead and throw views in
there. Having said that, this part basically becomes moot in
Drupal 8, since views is in core.
My best advice is look at the task at hand. If you're going to
need a lot of custom views, then go ahead and use views. If you
only need a couple of simple blocks, then Views is overkill, so
long as you don't plan on changing things around a lot later. Of
course if you do plan on changing things around, then you can
covert your custom blocks to views relatively easy.
Jamie Holly
http://hollyit.net
On 4/18/2014 3:46 PM, Drupal wrote: