If you're using dependency managers like bower you either have to import the stylesheet in your <head> or use the @include in a sass stylesheet, both will be a new HTTP request. Whereas if you compile it in one file, you save an extra request (now imagine you use multiple dependencies each with their own css file). Renaming a file would defeat the whole point of dependency management.
Comments
Still can't import pure CSS files without having to rename them to .scss. It's been in talks for over two years now, very disappointing.
I don't remember if I've tried it but I thought this was fixed in 3.0.
http://sass-lang.com/documentation/file.SASS_CHANGELOG.html#...
That adds a CSS import rule, doesn't embed the content.
What's so bad about having to rename a file?
If you're using dependency managers like bower you either have to import the stylesheet in your <head> or use the @include in a sass stylesheet, both will be a new HTTP request. Whereas if you compile it in one file, you save an extra request (now imagine you use multiple dependencies each with their own css file). Renaming a file would defeat the whole point of dependency management.
Just use the link to the CSS file in development an have your build tools concatenate everything for production. Certainly not a show stopper.