A
A
Adderall2017-07-21 21:39:58
css
Adderall, 2017-07-21 21:39:58

Should a beginner use preprocessors?

Can a beginner use sugar or is it better to write on clean?

Answer the question

In order to leave comments, you need to log in

7 answer(s)
S
sim3x, 2017-07-21
@sim3x

Yes
Differences from css are purely symbolic and at the same time without loess / sass it will not be possible to use bootstrap normally

D
Dima Pautov, 2017-07-21
@bootd

My opinion is No! I have never used them at all. Don't touch them. All you need is just to learn css very, very well. And then, if they are not yet extinct, you can use them for supposedly faster style writing! Maybe 2 years ago, they were good, but now they are useless.
Personally, for those who will be cococo about saying just my opinion regarding preprocessors, here is a video of what I mean.

V
Vasily Nazarov, 2017-07-21
@vnaz

For learning it is better to start with absolutely pure CSS.
When you want to optimize something in writing styles - SASS / LESS will come in by themselves (if they don’t die out by that time)

B
BB 8, 2017-07-22
@fruity4pie

Write a couple of sites using pure css, master gulp, and write a couple of other sites in sass (not scss).
You will draw your own conclusions.
From personal experience: sass is like a breath of fresh air. When I was a beginner, I also did not understand all these preprocessors and the noise around them :)

Z
zooks, 2017-07-21
@zooks

Without knowledge of CSS, preprocessors are not needed.
Moreover, while you set up the collector, all the desire to study can be beaten off.
So only switch to Sass when you already get something in pure CSS.

F
Froggyweb, 2017-07-31
@Froggyweb

For a beginner in preprocessors, mixins are the worst. Which do not give an idea of ​​\u200b\u200bwhat's going on inside, like all sorts of bootstraps
. I'm wondering what it means to know bootstrap at least 3.sersii? Is it to remember all his classes by heart? :)

S
Sergey Rybakov, 2017-08-04
@kyctarnik

Preprocessors for the most part make it easier to write code and maintain the project in the future.
Creating variables in the code allows in the future to replace the gamut of elements not to manually change all the elements that use this color, but to change the value of the variable.
It is also worth mentioning the simplicity of writing, for example stylus let you write like this

h1fs = 2em
body
  height 100vh
  width 100%
  h1
     font-size h1fs
  div
     padding 20px
     h1
        font-size h1fs

and eventually it will compile to
body
{
  height: 100vh;
  width: 100%;
}
body  h1
{
     font-size: 2em;
}
body  div
{
  padding: 20px;
}
body div h1
{
  font-size: 2em;
}

And along with them, after all, you can use other modules, such as minify and immediately create minimal files. Autoprefixer - allows you to forget about -webkit spacing.
Of course, you shouldn’t rush into battle with it from the very beginning, but it’s worth mastering CSS at a small / intermediate level and you can already get used to preprocessors.
From personal experience, I advise stylus, but SCSS is also among the pretty strong ones.
In variations there will be pure holivar and everyone will defend their position.
Even this review is mostly biased.
But again, from experience: Stylus is easier to learn and is on par with SCSS, albeit still young.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question