Closed lewismorris closed 10 years ago
This is going to be a tricky one, as I think with SCSS being the preferred syntax and more future proof, it may be the case we go forward with this.
Good thing is you can work with both, so its not a huge issue if we do go down that route.
With regards to your opinions on SASS, if you provide resources and examples of how it can benefit the team, we will discuss as a team on the best approach.
Ben
Personally throw in with SCSS... more for syntax than anything concrete
Hey Ben,
I think finding documented reasons to use Sass and Scss would be difficult as they're are still the same language with the same features and capability. I'd say this is more down to personal preference and obviously the one to go with would be the one that most team member would prefer to use.
Just a few reasons i prefer to use Sass over Scss:
I know you also raised the issue of Sass been depreciated in favour of Scss @Passenger-Inspired here are a few articles from circa 2010/2011 which say that this is not true. If you can find anything from closer to now i'll be happy to go with Scss as this would be the best for the long term.
http://thesassway.com/news/sass-is-here-to-stay http://nex-3.com/posts/102-the-indented-sass-syntax-is-here-to-stay
Nice find. I think I may just have seen a tweet regarding this or something.
Personally, I can't really comment on the pro's and con's of each, as I don't have enough experience with either.
I think the aim is we understand it as a team, what is easier to pick up as a new starter (beginner or experienced), what is more future proof and what will work better with our style of coding (e.g. OOCSS, if this is the way we go).
Overall the differences between SCSS and SASS are small, so if we have to move away from our preferred syntax, it shouldnt be too hard either way.
Let's just make sure it works for us as a team, and make a decision.
Ben
I don't really know of differences between SCSS and SASS either, though by preference, as far as syntax goes SCSS is my choice. From what I know, any differences are superficial and have no other benefits. I'd be happy to be proven wrong with that one though.
When it comes to Preprocessors, I've a fair amount of experience with LESS and was my go to, but I'm much more comfortable with SASS/SCSS. But at the end of the day, you guys are more than likely be going to be doing the heavy lifting when it comes to Front-End, so I'm supportive of any choices made in terms of syntax and preprocessor.
I'm with @ampersarnie.
I'm happy either way.
One thing I would say is that the decision to go with either syntax is a fairly minor concern, as I'm sure those who prefer to use the original approach would convert for the good of establishing a consistent, maintainable code base.
Agreed. I think with the syntax's being so similar, the switch from either camp is not going to be a big thing.
We will focus on this later down the line.
Ben
Quick question. Did we agree upon SCSS?
Need to add this as a general Presentation standard.
B
+1 SCSS
Think the general agreement was for SCSS. +1 for SCSS from me.
+1 SCSS
SASS :-)
Much cleaner, less to type and my fingers are not used to having to type { } or ; anymore :-(
+1 SCSS
+1 SCSS.
+1 SCSS
+1 SCSS
+1
SCSS it is :)
B
You MUST use SCSS as your pre-processor of choice
SCSS is the approach which the team have chosen to adopt moving forward.
The decision to use SCSS over Sass, is down to the syntax being more familiar to a future Clicksco Front End Engineer who has no experience with pre-processors.
Resources:
Opening this as a talking point around which Preprocessor to use following on from @iamrossgrant recommendation in #2.
I'm not defining any standards here, purely opening this issue as a talking point so we can decide what Preprocessor to continue with.
My personal preference would be to use Sass with the Bourbon extension.