I don't like that having an extension behaves differently than not. That is
sure to trip some people up. In my ideal syntax we'd have the following:
@import => A browser-based import with no special meaning
@include => Does what @import does now for sass/scss files
@mix => Does what @include does
I agree that @import foo.css should work as in regular CSS, but the
proposal for @import foo makes a lot of sense to me. The proposed
behavior would be a win because it would automatically remove an extra
GET request by inlining the CSS. It would also be more consistent with
importing sass or scss
