Skip to content

Commit

Permalink
Updated wording that could be considered insensitive
Browse files Browse the repository at this point in the history
  • Loading branch information
KittyGiraudel committed Feb 27, 2016
1 parent 01f138f commit 67e7395
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion en/_sass.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ That being said, there are many ways to use these features. Some good, some bad,

[Sass’ first commit](https://github.com/hcatlin/sass/commit/fa5048ba405619273e474a50400c7243fbff54fe) goes back as far as late 2006, over 8 years ago. Needless to say it has come a long way since then. Initially developed in Ruby, varied ports popped up here and there. The most successful one, [LibSass](http://webdesign.tutsplus.com/articles/getting-to-know-libsass--cms-23114) (written in C/C++) is now close to being fully compatible with the original Ruby version.

In 2014, [Ruby Sass and LibSass teams decided to wait for both versions to sync up before moving forward](https://github.com/sass/libsass/wiki/The-LibSass-Compatibility-Plan). Since then, LibSass has been actively releasing versions to have feature-parity with its older brother. The last remaining inconsistencies are gathered and listed by myself under the [Sass-Compatibility](http://sass-compatibility.github.io) project. If you are aware of an incompatibility between the two versions that is not listed, please be kind enough to open an issue.
In 2014, [Ruby Sass and LibSass teams decided to wait for both versions to sync up before moving forward](https://github.com/sass/libsass/wiki/The-LibSass-Compatibility-Plan). Since then, LibSass has been actively releasing versions to have feature-parity with its older sibling. The last remaining inconsistencies are gathered and listed by myself under the [Sass-Compatibility](http://sass-compatibility.github.io) project. If you are aware of an incompatibility between the two versions that is not listed, please be kind enough to open an issue.

Coming back to choosing your compiler. Actually, it all depends on your project. If it is a Ruby on Rails project, you better use Ruby Sass, which is perfectly suited for such a case. Also, be aware that Ruby Sass will always be the reference implementation and will always lead LibSass in features. And if you are looking to switch from Ruby Sass to LibSass, [this article](http://www.sitepoint.com/switching-ruby-sass-libsass/) is for you.

Expand Down
2 changes: 1 addition & 1 deletion en/_variables.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ When building a library, a framework, a grid system or any piece of Sass that is

{% include snippets/variables/02/index.html %}

Thanks to this, a developer can define his own `$baseline` variable *before* importing your library without seeing his value redefined.
Thanks to this, a developer can define their own `$baseline` variable *before* importing your library without seeing their value redefined.

{% include snippets/variables/03/index.html %}

Expand Down

0 comments on commit 67e7395

Please sign in to comment.