Why not Joomla?

Question

Joomla

I welcome everyone.
1. Many specialists scold Joomla. In vacancies, in her city, the requirements of her knowledge are few. However, the knowledge requirements of popular frameworks (YII, Zend, Symphony etc) prevail. The question arises - why? She (Joomla) has more than 10,000 ALREADY ready-made extensions that you set, set up and forget. On YII, as I understand it, when I need to put a comment component, a photo gallery, or something else, wild pandemonium will begin. Do you need to write it yourself? Manually? Whereas there the same JComments has already been polished to the point of being impossible. Delivered, 5 minutes of adjustment, and all. Or is it just to amuse the CSF that they say the site / store / portal is based on a super-duper fashionable framework?
I would like to hear an argumentative opinion, and not throwing mud at one or the other.
2. I am at a crossroads. Take Joomla 3.x (because I have already worked with it a lot), improve front-end/server-side knowledge, and develop websites/modules/components. Those. 1st option - "orchestra". 2nd option: more professional, take on PHP (there is also an interest to study JAVA, Python), frameworks with best practices, study OOP, databases well, write on them, go thoroughly to the server side. Most, more, hunting to go the second way. On the other hand, why NOT a ready-made CMS? Why create tasks for yourself? Or am I misunderstanding something?

Answer 1

Joomla is a completely normal CMS based on the framework of the same name. ( habrahabr.ru/post/175237 )
It is fashionable to scold her only because many different shit sites have been made on her basis, from schoolchildren's crafts to doorways and various file wasomers.
This is partly due to its (Joomla) popularity, and partly due to the low entry threshold. The unreliability of Joomla is a myth, since if you update it in a timely manner and monitor the safety of extensions, everything will be fine. Also, a huge number of extensions for Joomla have many holes, paid extensions that are posted on warezniks often contain backdoors and bookmarks. All this in total brings Jooml so much negativity from professionals.
As for point 2, it's up to you to decide, because if you are not ready to work closely with programming and you only need a working site, why waste time learning PL and frameworks. Take it and use it, only wisely of course. If you still want to learn a programming language, then of course creating a website on your bike built on the basis of a framework will be a good experience.

Answer 2

It is very easy to write your own component, module or plugin on joomla. The API is fairly well documented. And using Joomla not as cms but as cmf is quite realistic. Documentation and approach is in many ways superior to other cms / cmf (for example, 1s Bitrix)

Answer 3

A framework is needed when you need to write a highly specialized application, when there is sufficient financial support for the project in order to have enough time for development. For everything else, there is Joomla. In the "troika" you can generally create a site very quickly using only the admin panel and the "arbitrary code" module. And the specialists always scold something, don’t pay attention, I don’t see anything for which it could be scolded, I’ve been using it for 4 years now.

Answer 4

Here above they wrote about schoolchildren and I agree with this. The second is fucking logic, the third is lousy design. I rarely come across something serious on Joomla, mostly wordpress and drupal

Answer 5

The answer is very simple: they choose the cheaper (in terms of price, terms, reliability, availability of specialists) option.
If the Joomla functionality is enough or almost enough, they take it.
If it will be cheaper to write on a framework, they take the framework.
For example, in the project that I am developing now, there is not a single component that could be taken from Joomla or plugins (even authorization!)

Answer 6

gnarled thing

Answer 7

Only one phrase is suitable here: "One thing does not interfere with the other."
in the first case it is not clear what you want to do? configure joomla plugins and that's it?
in the second case, do you want to study technology and write joomla plugins from scratch?
tell me how it conflicts with each other? tasks are different ...
in general, the server side, roughly speaking, you need to know even before you spoil the zhumla, because what are you going to raise it on?

Answer 8

HA! I am using Joomla. And I'm not going to switch to something else. Now with version 3.5 big changes await...