Sass -> SassC

[glebm]

The Ruby version of Sass is deprecated, see http://sass.logdown.com/posts/7081811

[GBH]

Yeah. I remember reading that sass is not going to be in ruby now. How does this change affect apps on jruby? There was a PR that switched markdown parser to pure ruby at one point.

[glebm]

sassc-rails currently doesn't work on JRuby (sass/sassc-rails#92), likely due to this JRuby bug: jruby/jruby#4108

JRuby users will have to stay on CMS v2.0.17 until the issue is fixed in JRuby or sassc-rails.

[robmathews]

This change broke my ability to precompile assets and deploy my code. It is also unnecessary -

"(That said, the sass-rails folks hope to be compatible with sassc under the hood at some point, so maybe this will be a moot point and we won't have to switch.)"

Can we please wait until it is compatible? Waiting a few months won't hurt us.

[glebm]

I'd like to avoid an unnecessary dependency on the sass gem downstream. Why are you still using sass-rails instead of sass-rails?

[robmathews]

It's all about the timing. Currently rails-sass is still supported, and will continue to be supported until Rails 6.0 comes out, from what I can tell here rails/rails#32896 Realistically, there are still lots of folks like me who depend on it, and lots of gems that also depend in it.

…

On Sat, Dec 8, 2018 at 3:04 PM Gleb Mazovetskiy ***@***.***> wrote: I'd like to avoid an unnecessary dependency on the sass gem downstream. Why are you still using sass-rails instead of sass-rails? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#852 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGqgCewopKY10S7c65QmMMePcEiVzXPks5u3BtPgaJpZM4YWVyf> .

[glebm]

sassc-rails v2.1.0 has been released just now, it is now JRuby-compatible