Bitrix how to develop on it correctly?

Question

1C-Bitrix

Good afternoon, I'm trying to understand all my experience of working on Bitrix. The Bitrix component structure is such that it already contains ready-made layout and css styles. I, as a "Smart" person, demolished all their redundant code, and made up a new template, using PHP, of course. style.css that came with the components did not use at all, I always have a style sheet, or style modules in the main folder of the component. And in the studios that I worked (there are few of them and not all of them are good) they also did this.
And now I thought, maybe this is not right, maybe you need to edit the component code and not rewrite everything? And does anyone even use style.css? In my opinion, this is terribly inconvenient. As they do in professional firms. Tell...

Answer 1

They do everything as God puts on the soul. He also worked in Bitrix a lot.
The development style that Bitrix conceived is the best option for full-stack or front-end developers who have at least passed the layout implementation exam. It does not load extra js and css where it is not needed. And the larger the project, the greater the benefit.
In general, all the problems of people who like to collect everything in one js and one css file are ignorance of the architecture of the CMS with which it works. Moreover, almost always it is a stupid layout designer who does not know where his layout will go, and does not want to know. He also does not know how to use BX, which ultimately leads to the fact that a bunch of his scripts and forms are inconvenient to use, because. there are much more convenient native things. This is especially true for shopping carts and checkouts.
But I'll tell you a secret - webpack can also be configured so that it will generate component templates in the right folders with styles and js, and generate common styles into common css and js. And the frontender can still work with its postcss and ejs. But yes, to set up scripts, you need a specialist in Bitrix.
I had a big optimization project, where I got rid of such an assembly and scattered everything into components. Why? And how do you like css + js - 27 megabytes? Then, over time, he got off Bitrix, because. already grown enough.
What is the conclusion? People who do not have the necessary knowledge to work with it are taken to work with a complex CMS, and so they begin to scold Bitrix. Nothing to blame the mirror ...