C
C
Crash2015-02-15 10:01:47
CMS
Crash, 2015-02-15 10:01:47

Why are the vast majority of projects still being done on CMS, and not on frameworks?

It is clear that even the most typical project will eventually require customization if it is alive and needed by someone. And if it is made on the engine, then you have to fence crutches. Do many people still not understand this?

Answer the question

In order to leave comments, you need to log in

5 answer(s)
I
Inav, 2015-02-15
@Bandicoot

Because development is cheaper on cms,
because no one wants to write an admin panel for the site, especially if its development is comparable in labor costs to the public part,
because the customer wants standard content management mechanisms, and not what the developer comes up with,
because the customer wants to have the ability to go to another developer at the lowest cost,
because the entry threshold for cms is lower => there are more developers,
because the capabilities of frameworks are not needed for most sites, and for customizing cms, a knowledgeable person needs crutches not much more often than for a framework;
and because the vast majority of sites are not highload with dozens of servers, which is constantly sawed by a team of programmers.

K
killmeslow, 2015-02-15
@killmeslow

1st option = You sell 10 Bitrixes per month
2nd option = 0.5 sites on the framework per month

I
iliyaisd, 2015-02-15
@iliyaisd

Remember the joke about the programmer and the washing machine?)
Well, so, it turns out that there are people who find it easier to master the interface of the washing machine...

S
shane89, 2015-02-15
@shane89

It depends on what cms and what project.

D
DevOpsEngineer, 2015-06-01
@DevOpsEngineer

Сейчас актуальнее API, а не CMS или фреймворки.
Например, мобильный API Facebook-приложений. Разрабатывайте сразу на нём.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question