Where the design community meets.
San Francisco Head of Design at Amino Joined over 6 years ago
Awesome! Had a bit of friction updating my old Library (most groups had stuff out of order), but it's totally worth it to have text styles support everything that Sketch's text styles support. Previously, Library's text styles didn't support character spacing, baseline shift, and other text fine tuning options. Now it does.
Makes sense. Thanks!
$ python -m SimpleHTTPServer 8000
$ ruby -run -e httpd . -p 8000
$ php -S localhost:8000 -t .
Duplicate post deleted.
Cute, but I gave up waiting to see how it ended. Here's the whole
"The requested document is no more.", 'No file found.', "Even tried multi.", "Nothing helped.", "I'm really depressed about this.", "You see, I'm just a web server...", "-- here I am, brain the size of the universe,", "trying to serve you a simple web page,", "and then it doesn't even exist!", "Where does that leave me?!", "I mean, I don't even know you.", "How should I know what you wanted from me?", "You honestly think I can *guess*", "what someone I don't even *know*", "wants to find here?", "*sigh*", "Man, I'm so depressed I could just cry.", "And then where would we be, I ask you?", "It's not pretty when a web server cries.", "And where do you get off telling me what to show anyway?", "Just because I'm a web server,", "and possibly a manic depressive one at that?", "Why does that give you the right to tell me what to do?", "Huh?", "I'm so depressed...", "I think I'll crawl off into the trash can and decompose.", "I mean, I'm gonna be obsolete in what, two weeks anyway?", "What kind of a life is that?", "Two effing weeks,", "and then I'll be replaced by a .01 release,", "that thinks it's God's gift to web servers,", "just because it doesn't have some tiddly little", "security hole with its HTTP POST implementation,", "or something.", "I'm really sorry to burden you with all this,", "I mean, it's not your job to listen to my problems,", "and I guess it is my job to go and fetch web pages for you.", "But I couldn't get this one.", "I'm so sorry.", "Believe me!", "Maybe I could interest you in another page?", "There are a lot out there that are pretty neat, they say,", "although none of them were put on *my* server, of course.", "Figures, huh?", "Everything here is just mind-numbingly stupid.", "That makes me depressed too, since I have to serve them,", "all day and all night long.", "Two weeks of information overload,", "and then *pffftt*, consigned to the trash.", "What kind of a life is that?", "Now, please let me sulk alone.", "I'm so depressed."
Why do I agree? Because Compass seems bloated to me too, and philosophically I prefer a bunch of mixins that work on top of Sass vs. an alternate/enhanced preprocessor that works with Sass.
Fewer keystrokes per declaration, yeah. But easier? Maybe, but not for me. See my reply to Daniel above.
And here I respectfully agree. :-D
Good question. I do use variables for colors too.
When I'm implementing a design or coming up with new styles, I like to just type $medium-weight when I want the medium weight. It's less friction than having to remember whether I assigned medium to 500 or 600.
It's especially helpful if I don't have all nine weights assigned and don't want to remember which ones I explicitly assigned using @font-face.
It's also a little more maintainable. If you swap out your typeface with one that uses slightly different weights, you might want to shift things around in your @font-face declarations but not necessarily go through all your CSS replacing every 300 with a 200. You just keep it as $light-weight everywhere and make the adjustments in your _fonts.scss partial.
I respectfully disagree that it's the wrong way to use variables. :-)
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.