New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace LESS with Sass #56

Closed
SandHilt opened this Issue Aug 31, 2015 · 32 comments

Comments

Projects
None yet
@SandHilt

SandHilt commented Aug 31, 2015

No description provided.

@donatj

This comment has been minimized.

donatj commented Aug 31, 2015

👍

@andrewconnell

This comment has been minimized.

Member

andrewconnell commented Aug 31, 2015

👍 👍

@una

This comment has been minimized.

una commented Aug 31, 2015

👍 👍 👍

@pascalberger

This comment has been minimized.

pascalberger commented Aug 31, 2015

+1

1 similar comment
@Diablo-D3

This comment has been minimized.

Diablo-D3 commented Aug 31, 2015

👍

@CuddleBunny

This comment has been minimized.

CuddleBunny commented Sep 1, 2015

I personally prefer LESS, perhaps maintaining both wouldn't be out of the question.

@Jahnp

This comment has been minimized.

Collaborator

Jahnp commented Sep 3, 2015

This would be a pretty big change, but we do see the value in supporting SASS/SCSS in some way. We aren't in a position to fully replat our styles any time soon, but like @CuddleBunny mentions, I could see spinning up parallel versions at some point.

Tidbit for the sake of curiosity: we originally started with LESS because it had pretty broad adoption across product teams at Microsoft.

@mrmckeb

This comment has been minimized.

mrmckeb commented Sep 6, 2015

Agreed. Less is no longer the standard, as Sass has gotten much larger traction and a bigger following.

@tidg

This comment has been minimized.

tidg commented Sep 15, 2015

👍 +1 👍

@matthew-dean

This comment has been minimized.

matthew-dean commented Sep 16, 2015

They're used by different groups for different reasons.

LESS is easier to learn as its a intentionally tight feature set to cover the vast majority of use cases, but not all.

Like CSS, LESS is declarative. SASS is imperative. So that also makes it a more familiar concept to web developers. For instance, LESS had concepts like block scoping and cascading values that SASS does not have. So it's more like CSS+ and SASS is more like PHP or Ruby with CSS-like syntax.

So LESS doesn't try to be the standard but a solution to a different set of problems as priority. We (core Less users) regularly suggest Sass when people need a more programming-language-like imperative construct. Basically, Less is the iPod and Sass is the Zune, so, yup, Sass has way more features. :-)

Use what suits your project!

@andrewconnell

This comment has been minimized.

Member

andrewconnell commented Sep 17, 2015

@matthew-dean by comparing SASS to Zune you have just made enemies with web developers at large! 😃

@matthew-dean

This comment has been minimized.

matthew-dean commented Sep 17, 2015

@andrewconnell lol a low blow, I know. But sometimes I hear "Sass is better than Less because it has more features." Which is pretty much exactly the same as saying, "Zune is better than the iPod because it has more features." Fewer features sometimes makes for faster adoption, less confusion, and easier onboarding for new devs, so that's the reason I bring up the comparison.

@SandHilt

This comment has been minimized.

SandHilt commented Sep 18, 2015

@StfBauer

This comment has been minimized.

Contributor

StfBauer commented Sep 20, 2015

I think many web developer switched from LESS to SASS. Support both will be a good option for those who still use less.

@timschoch

This comment has been minimized.

timschoch commented Sep 23, 2015

+1

@matthew-dean

This comment has been minimized.

matthew-dean commented Oct 8, 2015

I mentioned this thread in this post, if you're curious: http://getcrunch.co/2015/10/08/less-the-worlds-most-misunderstood-css-pre-processor/

@ericthompson

This comment has been minimized.

Contributor

ericthompson commented Jan 8, 2016

Hi all! Looping back here to mention to everyone that our latest version, 1.2.0, includes the beginnings of our conversion to SASS - check it out! We've still got work to do, but we're open to hearing opinions/feedback.

@andrewconnell

This comment has been minimized.

Member

andrewconnell commented Jan 8, 2016

Awesome update! How soon can we expect to this to be in the CDN?

@andrewconnell

This comment has been minimized.

Member

andrewconnell commented Jan 8, 2016

Reason I ask – next week we will have our first release of the Angular Directives for Office UI Fabric and our demos reference the CDN links… we’d love to point to the latest stuff…

@SharePointOscar

This comment has been minimized.

SharePointOscar commented Jan 8, 2016

Oh nice now we're really up to par with Bootstrap, since it has AngularJS directives as well.

Stoked, can't wait to integrate them into my boilerplate MEANS open source project http://github.com/SharePointOscar/MEANS

Sent from my 6S

On Jan 8, 2016, at 11:43 AM, Andrew Connell <notifications@github.commailto:notifications@github.com> wrote:

Reason I ask - next week we will have our first release of the Angular Directives for Office UI Fabric and our demos reference the CDN links... we'd love to point to the latest stuff...

Reply to this email directly or view it on GitHubhttps://github.com//issues/56#issuecomment-170104046.

@ericthompson

This comment has been minimized.

Contributor

ericthompson commented Jan 10, 2016

@andrewconnell - we're currently pushing to get our CDN updated asap. I don't have a timeframe yet, but we're hoping for the next week or 2.

@andrewconnell

This comment has been minimized.

Member

andrewconnell commented Jan 15, 2016

@SharePointOscar just FYI... we shipped the first drop of http://ngofficeuifabric.com, Angular directives for Office UI Fabric

@SharePointOscar

This comment has been minimized.

SharePointOscar commented Jan 15, 2016

Yummy! Time to start integrating them into my MEANS boilerplate project! Thanks for the heads up AC!

From: Andrew Connell
Reply-To: OfficeDev/Office-UI-Fabric
Date: Friday, January 15, 2016 at 10:39 AM
To: OfficeDev/Office-UI-Fabric
Cc: Oscar Medina
Subject: Re: [Office-UI-Fabric] Transform styles LESS to SASS (#56)

@SharePointOscarhttps://github.com/SharePointOscar just FYI... we shipped the first drop of http://ngofficeuifabric.com, Angular directives for Office UI Fabric


Reply to this email directly or view it on GitHubhttps://github.com//issues/56#issuecomment-172046676.

@andrewconnell

This comment has been minimized.

Member

andrewconnell commented Jan 15, 2016

Np… planning another drop sometime early next week with at least one more directive…

@mikewheaton

This comment has been minimized.

Collaborator

mikewheaton commented Jan 26, 2016

Replacing LESS with Sass is underway, see pull request #279. We plan to have LESS completely removed when we release Fabric 2.0.

@mikewheaton mikewheaton changed the title from Transform styles LESS to SASS to Replace LESS with Sass Jan 26, 2016

@mikewheaton mikewheaton referenced this issue Feb 1, 2016

Closed

Remove LESS #295

@StfBauer

This comment has been minimized.

Contributor

StfBauer commented Feb 1, 2016

👍

@mikewheaton mikewheaton referenced this issue Feb 1, 2016

Merged

Remove LESS #303

@mikewheaton

This comment has been minimized.

Collaborator

mikewheaton commented Feb 5, 2016

Finished in #303!

@mikewheaton mikewheaton closed this Feb 5, 2016

@purtuga

This comment has been minimized.

purtuga commented Feb 7, 2016

Sad to learn that LESS is removed and no longer supported... 😞
Supporting SASS, although may provide you a richer set of features - that you may or may not use - it does add complexity and intimidation around setting up an environment for anyone that may want to use this project to create mashups. It also limits us LESS users in actually taking advantage of Office UI Fabric... In my personal use cases, I have not been able to find a gap in functionality that required me to go use SASS - perhaps you guys have and thus the change in tooling...

That being said, I will eventually move to use SASS, since it seems that tool is moving quickly into becoming the most popular one.. and thus the one with best support.So I'm not a hatter of the tool... but I'm not ready yet either... so with that:


How to use Last release with LESS Support

For anyone that may find this thread and still want to use the LESS source, there is what I did:

The instruction below are for v1.2.1 - which seems to be the last tagged version that had LESS support.

From the command prompt:

$ git fetch --tags
$ git checkout -b release_1-2-1 1.2.1

If using Bower, just run this command instead of the default approach:

 bower install --save-dev OfficeDev/Office-UI-Fabric#1.2.1

now... back to using Office UI Fabric on custom widgets.... 😁

/Paul

@matthew-dean

This comment has been minimized.

matthew-dean commented Feb 7, 2016

since it seems that tool is moving quickly into becoming the most popular one

Sorry, but under what metric have people determined that Sass is more popular than Less?

https://twitter.com/matthewdeaners/status/693228336814817280

@mikewheaton

This comment has been minimized.

Collaborator

mikewheaton commented Feb 7, 2016

We understand that this isn't a welcome change for everyone. We've communicated that it's coming (in this issue, our prior release notes, and in our roadmap) but we know it will be a surprise to some.

For us it's not a question of the features of LESS vs Sass or the wider popularity or trendiness of either one – what we've heard from our users, both inside and outside of Microsoft, is that Sass is preferred. We considered supporting both but this would burden our development process and keep us from fixing bugs and developing features. As a small team we have to be careful about where we spend our time. Thanks for your understanding.

@matthew-dean

This comment has been minimized.

matthew-dean commented Feb 7, 2016

For us it's not a question of the features of LESS vs Sass or the wider popularity or trendiness of either one – what we've heard from our users, both inside and outside of Microsoft, is that Sass is preferred.

That's a good answer, and makes sense.

@purtuga

This comment has been minimized.

purtuga commented Feb 7, 2016

Hi @matthew-dean... You are right: I don't have a metric I can point you to... its simply my personal opinion based on my recent encounters. I'm a LESS user and I have been feeling as if perhaps its time for me to move on from it... Several of the libraries/widgets I have used recently all had their CSS written in SASS...

@mikewheaton Thank you for our response. I understand the motive and agree with @matthew-dean : its ultimately what makes more sense for this project and the majority of its users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment