How justified is the use of frameworks in serious projects?

Question

Web development

Hello!
It is interesting to hear your opinion.
It seems to me that to create a simple online store / CRM / forum on a turnkey basis (done - handed over - forgot) it is very convenient to use a bunch of popular PHP, JS, CSS frameworks. You don't care what will happen to the project in 1-2 years, who will support it and how. It is important for you to spend as little time as possible on its development, because in order not to make your own bikes, you use ready-made solutions.
But, it's a completely different thing when you've been working on a project for several years. Let's say today you take a bunch of Laravel + Angular + Bootstrap. What will happen in 3-5 years with these frameworks? Paradigms, approaches will change, you will be forced to modify some parts of the framework as you work on the project. As a result, you will not be able to upgrade to Laravel 2020 because you already have your bike. It turns out that from the used frameworks you have only the structure left.
You say "what the hell?". But 5 years ago there was codeigniter, and 2 years ago it was almost dead, its development was stopped. Development was resumed, and codeigniter itself has already become different.
Or my reasoning in relation to long-term projects is in principle not correct and we take the framework as a basis, which in any case we will cut for ourselves. In that case, further support should not worry us?
Thank you!

Answer 1

Frameworks are used in big companies and big projects. The same Yandex and mail ru are used by both Django and perl Frameworks.
Your bike will become obsolete in the same way or even faster than any other Framework.
If the project is large, then a team works on it, which keeps the project up to date. The Framework is outdated, the team starts migrating to another Framework or to an updated version of the current one.
Even if the current MVC paradigm changes by 2020, you will also rewrite your bike to some other one.

Answer 2

Paradigms, approaches will change, you will be forced to modify some parts of the framework as you work on the project

No one can force me to modify anything on the server.
And I won't do it until the customer pays for it.
And if he pays not what he needs, then this is his problem, not the frameworks.

Answer 3

If the duties include keeping the code up to date, then at least someone else’s, at least your own bike, must be supported. There is no difference in this regard.

Answer 4

Regarding "I wrote and forgot" - there is a separate boiler.
Regarding the paradigm - MVC lived, is alive, and will live. The rest is not so important. Here is the frame for you.
As for big projects, there are no very big projects. Any large project is divided into microservices that are not visible to ordinary users. Each service can be written on different platforms for you, but they will communicate in the same language. JSON, XML - they are years old, but they are alive, and no one canceled them. And yes. You can always rewrite a microservice on a new platform if you have a desire or have problems.
Regarding my framework - I tend to think that assembling a framework from different particles is still better. These particles will be updated like Laravel does, and there will be no security holes. You can't follow everything.
In short, microservices will be in vogue!

Answer 5

We need to proceed from the fact that the more parts of our application code are supported by the community or by another company (for money) , the less work we have .
If you yourself would completely write the code, then all the support would immediately be on you from the first day . Yes, your code would be less than the code of someone else's framework, since it would be narrow-minded. But in any case , it would be much more if you didn’t use frameworks and libraries by other authors at all.

Answer 6

That's how they live. A friend of mine is still making new projects in yii1 because he was reluctant to switch to yii2 and a lot of projects were already written in yii1.
There is another approach: take only the frame, the base, throw your own developments on it. You will get your own framework / microframework, then at least you won’t need to update anything, but write a lot of documentation if you need to give the project to other developers.

Answer 7

I myself generate html on my site using a Java program and get somewhere around 300 static html files.
happy as an elephant

Answer 8

You can try background-size: 100% 100%
Although of course it will not be very beautiful