Why i love drupal

topic answer to the opposite look


It has been 2 years since I use exclusively Drupal for my projects and customer projects. From my own experience I can say that life and work with this system follow this biorhythm:
Depressions are where you run into a problem, for the solution of which you need to read the documentation, increase your programming knowledge or leave the apartment and relax a bit. You need to keep this in mind when reading such articles and listening to such reports (a recording from RIT of the famous report by Ilya Azarov).

Peaks - sudden insights "Damn, it turns out this could be done without resorting to a hammer and chisel."

Basic problems of beginner-middle Drupal programmers

1. Ability to make hasty conclusions.
The figure on the left shows the general scheme of the work of Drupal's theming, or rather, how a beginner sees it right away. Naturally, seeing only the tip of the iceberg, he thinks he “drunk the Sax” and does not dig further.

2. Fear of writing your own modules.
If we talk about Drupal, then the fear of writing our modules from our developers can be compared with the loss of virginity. Before that , it’s very scary. After - you do not know how without this I lived earlier. This is probably because the meaning of the word “module” is associated with something important and special (the module for docking a space station), and the idea that there might just be a custom piece of code does not occur to him.

3. Fear of someone else's code.
Many questions could be avoided if the developers looked at the source code. Some do not know where to start, others simply disdain to "climb into someone else's code." And meanwhile, it helps a lot both in studying the system and in raising one's professional level, since the bulk of the Drupal code is licked stronger than a plate of another cat after absorbing whiskas.

4. Fear of patches.
For the most part, there is nothing extra-bad about using custom patches in projects. In the last site I made used 16 patches. For the most part, they were caused by special, not quite standard, requirements for the project. However, I don’t have any particular headaches when updating the system, because if you did everything correctly, applying the project patch in SVN takes place in two clicks of the mouse.

5. Ignorance of English.
I actively participate in the life of the drupal.ru support form , and I can assure you that freelance schoolchildren who do not know English are the most screaming about the squalor of Drupal. I will answer briefly on this point: you call yourself a programmer - so be kind, learn English, everything is documented in English .
To be honest, it’s worth noting that the Russian documentation is enough.

The "Problems" of Drupal Himself

1. Caching

Time: a year ago
Location: sourcemaking.com
Hosting: average VDS
Optimization: none, standard cache (then I didn’t know much yet;)
I’ll be brief:

2. All-in-one-file

The problem is sucked out of the finger. If a programmer has such a situation, he is simply inexperienced.
Especially for those who do not know or can not - require / include .
And in the sixth Drupal, there is also support for separation in menu hooks.

3. Conflict of module X and module Y

Yes, such a problem exists. How can 2 things that do some operations on one entity not conflict? Of course, Drupal is to blame for everything, he also provides flexibility and access to literally everything. The problem partially disappears after a long acquaintance with the system and a careful selection of modules. And until then, screams will be heard that from this: the
spoiler from the lamborghini falls.

Drupal is not for the lazy

Unfortunately or fortunately, but it is. If you want to make a solid site in two days, you won’t succeed. One must go into Drupal and enter at least six months in order to consider himself his master, and not vice versa. Here is the same learning curve that everyone is talking about, but no one has seen:
(the graph is localized specifically for Russian-speaking users)

Yes, there are problems, but

The improvement of the kernel is ongoing.
Bugs are fixed promptly.
New modules come out every day.
The documentation is gradually being translated into Russian.
Users on support forums receive replies every minute.

And finally - more and more new sites built on Drupal come out.

And most importantly, all this is done not only by some abstract people across the ocean, but also by us , the Russian-speaking Drupal community .