Re:Principles we use to write CSS for modern browsers
by shabda on Thursday September 22, 2016 @09:22AM
(#12556623)
Both the tools mentioned above LESS/SASS have been for 5+ years. There is churn in frontend tooling, but it is not a valid reason for not using LESS.
Re:Principles we use to write CSS for modern browsers
by t4nkd on Thursday September 22, 2016 @09:25AM
(#12556637)
Usually this kind of attitude could be justified even if it was just a shitty anecdote, but with SCSS and LESS in particular I'm afraid you've chosen long lived, bulletproofed software that has tremendous adoption and community. Neither would be what anybody would call "the tool of the month".
Re:Principles we use to write CSS for modern browsers
by Tloewald on Thursday September 22, 2016 @10:24AM
(#12556971)
If you're using React but not LESS or SASS then you have a strange attitude to "tool of the month" but it does explain antipathy towards DRY.
Re:Principles we use to write CSS for modern browsers
by andruby on Thursday September 22, 2016 @10:47AM
(#12557139)
SASS is almost a decade old [0] and has been in wide-spread use for a long time. The tool churning you talk of is something I have only seen in JS land to such a degree.
Moreover, the barrier to entry to learning SCSS/LESS is really low if you know CSS.
[0] https://github.com/sass/sass/tree/4acf5158734013f08fca4be6e2...
Re:Principles we use to write CSS for modern browsers
by exceptione on Thursday September 22, 2016 @10:05AM
(#12556867)
Both are proven tools and should be used by any serious frontender.
Pick SCSS, it's your most advanced option; you won't hit a limit in what you ultimately want to achieve.
Because there is so much tooling churn + barrier to entry. The point is that sometimes it's better to repeat yourself than to use the tool of the month.