How painful is it to switch from MVC approach to Drupal?

Question

Drupal

Greetings)
Not so long ago I started trying to delve into Drupal and now I started to wonder if it's worth it.
I'm so used to the MVC approach, template engines, that now, when I do something in Drupal (in the 7th version), I feel pain with all my heart. They write in books, they say, "if you want to do something in Drupal, then look for a module for this, for sure it is there." Okay Google, find me a module for a stepped menu (so that I can assemble it from other menus), into which, logically, I would have to transfer an array of links, titles of the desired nesting level and everything is OK, then I would configure its frontend part and that's all the thing is. Now I shoveled a bunch of modules, they all do about what I need, okay, I'll survive that they are stubborn in their functionality. But the fact that working with effects and, in principle, the output method is supposed only from the admin panel, is stupid. I think, ok, now I'll see how it all comes together and correct it in this place.
The topic is not so much for pouring out boiled or holivars, as I want, having described the situation, to understand whether I see it correctly (or I just haven’t had time to work with it normally yet).
That is, if I want to have something that works according to my Wishlist, I still have to write it myself? And taking into account that I have only written on MVC engines (oc, presta), will mastering Drupal be pointlessly difficult?
--
(By meaningless, I mean that using the logically correct approach of separating logic and presentation, I could look for more relevant CMS|CMF, although I don’t know of any other than Bolt CMS or October).

Answer 1

when I was tinkering with dryupal (about three years ago, but rather stubbornly and for a long time), I used the https://www.drupal.org/project/devel_themer module or similar, I don’t remember exactly. it shows which functions were used when rendering a particular block. the right way is to redefine them in your module or theme, not to patch dryupal.
there are many steps where you can override and a lot of hooks in api, not everything is so bad, although you need to get used to it, at least imagine the call stack in general terms, where which hooks are called. I sometimes even look at the code for this.
+ xdebug can be a great help in this, when you start working with it, go through what functions are performed several times, then it becomes clearer and more familiar.
although I haven’t used it for a long time, mostly warm memories remain about it, although I also had to make my own modules)

Answer 2

With the 7th, everything is approximately as you described. It's hard to find something in class. But Drupal has a hook for almost everything :) You get used to it with experience.
I would recommend that you start learning 8-ku. There is already MVC, it will be easier for you to figure it out. Yes, and it will be more powerful than 7k :)
But not all modules are imported for 8k yet, but this will be decided very soon.