Answer the question
In order to leave comments, you need to log in
How does the use of the CSS preprocessor and postprocessor affect development?
Hello!
I am a novice coder who wrote in pure CSS, I was faced with the fact of the existence of preprocessors and postprocessors . Their application is not entirely clear, it is only clear that they improve life in some way. So, could you briefly explain to me how they make life easier and whether it is worth using them or continuing to write in pure CSS?
To be more precise:
Answer the question
In order to leave comments, you need to log in
Generally speaking, it becomes less routine - monotonous repetitive actions.
In order not to guess - immediately select SASS in the SCSS syntax. You need a high-speed implementation of libSass, which you fasten to gulp. Then you add an autoprefixer to this, which will allow you to forget about manual prefixing. No more "post-processors" are needed. But before proceeding with this step, you must have a good knowledge of CSS.
Here is a good tutorial for beginners
https://scotch.io/tutorials/getting-started-with-sass
SASS works on the backend, regular CSS comes to the browser.
LESS works in the browser, so the overhead costs on the client increase both due to the additional download of the library and due to its operation.
And both approaches solve the problem approximately the same - to add to CSS something that is not there yet, in particular variables and calculations on the fly ... Well, in general, at least on Google, at least on YouTube there is simply indecently a lot of information, and you can literally do it in a couple of days dabble in theory.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question