3 ms·
It's seems great for developpers. The minus part of generated code and all those frameworks is of course that it doesn't go in the direction of "view source" re
by plesn 18y ago
It's seems great for developpers. The minus part of generated code and all those frameworks is of course that it doesn't go in the direction of "view source" readability. Is css becoming an "assembly" for style inside browsers?
- Hexstream 18y agoThis problem could be solved with better editors. You could switch between "programmatic mode" (with all variables and fancy stuff) and "view source mode" (with variable values and plain CSS in general) with one keystroke. You could also have semi-programmatic modes that show some programmatic features and "expand" others. Also it would be possible to look at the plain CSS but have values coming from the same variable in a distinct color. We should get more creative with multiple views of the same document in the editing department.
- nex3 18y agoSass actually takes pains to make the source code it outputs readable. This isn't always entirely possible, since by its nature expressing something in Sass can take significantly less code than the CSS counterpart and properly organizing the expanded code automatically is hard. But there are several output styles designed to be readable, and it's possible to add comments that are rendered as CSS comments.
- gommm 18y agoI love the compact output style (Sass::Plugin.options[:style] = :compact) to tell Sass to outpus one-line CSS files.