Two years earlier, CSS preprocessors were scolded for extra code, arguing that they couldn’t be used for mobile-friendly. What do we see today? What is your opinion?

Question

css

Good morning, friends
I remember 2-3 years ago, LESS, SASS, SCSS and other preprocessors were praised for the speed of development ... and scolded for the extra code that appears after compilation.
On a PC, this is still okay, they said, but when making layouts for mobile devices, this is extremely critical.
And it seems quite logical.
However...
What do we see today?
LESS SASS SCSS are used today, to a greater extent, just for layout of websites with adaptive design.
(For layout for one screen, preprocessors are used much less often ....
And if you roam the pages of the forums, you can see that questions regarding css preprocessors, 90% consist of those questions that are somehow related to the adaptive)
It is thanks to this popularization of responsive websites that preprocessors are in such great demand today.
Question.
Why did it happen?
Hardware has become more powerful, and so on, this is understandable .... but the Internet has remained the same ....
Yes, and preprocessors have wised up, but not so much?
Responsive websites are much more extensive than conventional websites. Naturally, to support them, due to their volume, it is more convenient to use preprocessors, but for some reason everyone forgot about minimizing the code, because we end up typesetting for users.
And they, our convenience of developing web sites, are not interested at all ...
The user is interested in the site loading speed, which falls due to extra code.
What is your opinion on this?

Answer 1

Well, let's say yes, in part. If you work on the same mixins, then the code could swell. But here we are talking about numbers like +5kb with a total file size of 20kb. etc. This could be critical only if you surf via EDGE, but on 3G it is no longer felt, and even more so on LTE. Mobile Internet has really become much (!) Better today than 3-4 years ago. So now, this is already saving on matches. In addition, preprocessors have become smarter, in addition to mixins, there is, for example, extend now, which arranges selectors separated by commas, and does not copy the code. There is no more swelling in general.

Answer 2

yes, it seems they didn’t swear before, well, except perhaps in a small town and without telling anyone.

Answer 3

Smartphones, tablets... this doesn't always mean 3G, a lot of people access the Internet via wi-fi, both at home and in cafes, shopping centers, etc.
Take the same bootstrap minified CSS 119kb, plus icons fonts 210kb and JS - 36kb
and plus your custom CSS, it will also come out at least 100kb (of course it depends on the project)
And it is also for mobile development...

Answer 4

Now the fashion for "CSS post-processors", which are not.
Extra code? What you write is what will happen.
As for the connection with the adaptive - google Susy, Bourbon. But two years ago they already existed.