Why I love Drupal
topic answer to the opposite view
It's been 2 years since I exclusively use Drupal for my projects and projects of customers. From my experience, I can say that life and work with this system occurs according to this biorhythm:
Hollows - this is where, you run into a problem, to solve which you need to read the documentation, increase your programming knowledge or leave the apartment and relax a little. One should remember this when reading such articles and listening to such reports (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."
')
1. The ability to make hasty conclusions.
The figure on the left shows the general scheme of the themeization of Drupal, or rather, how the newcomer sees it at once. Naturally, seeing only the tip of the iceberg, he thinks that he was “Drupal Saks” and doesn’t dig further.
2. Fear of writing their 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 , very scary. After - you do not know how without this and lived earlier. Probably, this is because the meaning of the word “module” is associated with something important and special (the docking station of the space station), and the idea that there might just be a custom piece of code does not occur to it.
3. Fear of someone else's code.
Many questions would be avoided if the developers looked into the source codes. Some do not know where to start, others simply disdain to "climb into someone else's code." Meanwhile, it helps a lot in studying the system, and in raising its professional level, since the bulk of the drupal code is licked more than a plate of a different cat after absorbing whiskey.
4. Fear of patches.
For the most part, there is nothing extra-bad about using custom patches in projects. In the last site , which I did, 16 patches were used. For the most part they were caused by special, not quite standard, project requirements. However, I do not experience any special headaches during system updates, since, if you did everything correctly, applying a patch to a project in SVN happens in two mouse clicks.
5. Ignorance of English.
I actively participate in the life support form of drupal.ru , and I can assure you that freelance schoolchildren who do not speak English cry most loudly about the wretchedness of Drupal. I will answer briefly on this point: call yourself a programmer - so be kind, learn English, everything is documented in English.
For the sake of truth, it is worth noting that there is enough in Russian documentation.
Time: a year ago
Location: sourcemaking.com
Hosting: average VDS
Optimization: no standard cache (then I didn’t know much about it;)
I'll be brief:
The problem is sucked from the finger. If a programmer has such a situation, he is just inexperienced.
Especially for those who do not know or can not - require / include .
And in the sixth drupale, there is also support for sharing in menu hooks.
Yes, such a problem exists. How can not conflict 2 things that make some operations on a single entity? 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 careful selection of modules. Until then, shouts will be heard that from this:
The spoiler from Lamborghini falls down.
Unfortunately or fortunately, but it is. If you want to make a good website in two days, you will fail. In Drupal it is necessary to delve into and enter at least six months to consider himself his master, and not vice versa. Here is the learning curve that everyone is talking about, but no one has seen:
(the schedule is localized specifically for Russian-speaking users)
The improvement of the core work is ongoing.
Bugs are fixed promptly.
New modules come out every day.
Documentation is gradually being translated into Russian.
Users in support forums get answers every minute.
And finally - there are more and more new sites built on Drupal.
And most importantly, all this is done not only by some abstract people across the ocean, but by us , the Russian-speaking community of Drupal .
Prehistory
It's been 2 years since I exclusively use Drupal for my projects and projects of customers. From my experience, I can say that life and work with this system occurs according to this biorhythm:
Hollows - this is where, you run into a problem, to solve which you need to read the documentation, increase your programming knowledge or leave the apartment and relax a little. One should remember this when reading such articles and listening to such reports (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 beginning-average Drupal programmers
1. The ability to make hasty conclusions.
The figure on the left shows the general scheme of the themeization of Drupal, or rather, how the newcomer sees it at once. Naturally, seeing only the tip of the iceberg, he thinks that he was “Drupal Saks” and doesn’t dig further.
2. Fear of writing their 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 , very scary. After - you do not know how without this and lived earlier. Probably, this is because the meaning of the word “module” is associated with something important and special (the docking station of the space station), and the idea that there might just be a custom piece of code does not occur to it.
3. Fear of someone else's code.
Many questions would be avoided if the developers looked into the source codes. Some do not know where to start, others simply disdain to "climb into someone else's code." Meanwhile, it helps a lot in studying the system, and in raising its professional level, since the bulk of the drupal code is licked more than a plate of a different cat after absorbing whiskey.
4. Fear of patches.
For the most part, there is nothing extra-bad about using custom patches in projects. In the last site , which I did, 16 patches were used. For the most part they were caused by special, not quite standard, project requirements. However, I do not experience any special headaches during system updates, since, if you did everything correctly, applying a patch to a project in SVN happens in two mouse clicks.
5. Ignorance of English.
I actively participate in the life support form of drupal.ru , and I can assure you that freelance schoolchildren who do not speak English cry most loudly about the wretchedness of Drupal. I will answer briefly on this point: call yourself a programmer - so be kind, learn English, everything is documented in English.
For the sake of truth, it is worth noting that there is enough in Russian documentation.
"Problems" of Drupal himself
1. Caching
Time: a year ago
Location: sourcemaking.com
Hosting: average VDS
Optimization: no standard cache (then I didn’t know much about it;)
I'll be brief:
2. All-in-one file
The problem is sucked from the finger. If a programmer has such a situation, he is just inexperienced.
Especially for those who do not know or can not - require / include .
And in the sixth drupale, there is also support for sharing in menu hooks.
3. Conflict of module X and module Y
Yes, such a problem exists. How can not conflict 2 things that make some operations on a single entity? 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 careful selection of modules. Until then, shouts will be heard that from this:
The spoiler from Lamborghini falls down.
Drupal is not for the lazy
Unfortunately or fortunately, but it is. If you want to make a good website in two days, you will fail. In Drupal it is necessary to delve into and enter at least six months to consider himself his master, and not vice versa. Here is the learning curve that everyone is talking about, but no one has seen:
(the schedule is localized specifically for Russian-speaking users)
Yes, there are problems, but
The improvement of the core work is ongoing.
Bugs are fixed promptly.
New modules come out every day.
Documentation is gradually being translated into Russian.
Users in support forums get answers every minute.
And finally - there are more and more new sites built on Drupal.
And most importantly, all this is done not only by some abstract people across the ocean, but by us , the Russian-speaking community of Drupal .
Source: https://habr.com/ru/post/46899/
All Articles