

I better understand your way and your approach, and, in fact, I realise that we clearly live in two differents worlds for writing code.

My opinions are purely based on what I have encountered.
#Read adobe dreamweaver cc classroom in a book 2017 online code
Do I think code indentation is easier to read than no code indentation, or dark colored UI's/editing environment are useful to me, no. Maybe there are editors that know what color is stored in the variable and can show it as a block of color next to it but the ones I've used dont.ĭo I find nesting styles easier to read that lisiting those styles long-hand, no.īut then again each to their own. I'm not really going to know what $mySpecialBlueColor is unless I travel all the way to the list of variables, usually at the top of the page, to see the block of color next to it. If I was at the foot of SASS file and wrote: I dont know even if its a good idea to store colors in variables as you can never see those colors in a SASS file I'd have to think about coming up with a descriptive variable name which may clash with something in the future so I may have to re-write it later on in the process Why would I wantto store padding: 0 20px 10px 0 in a variable? Variables - both use a similar workflow, assigning properties to variables mostly which you would store at the top of your page and mostly you can never remember what those variables attributes are, which in my opinion if you can do without is much better. Or why are you comparing PHP to Less/Sass ?
