nex3

12 ms·

91.
by nex3 17y ago
Sass is definitely not targeted at programmers, and it certainly doesn't just solve "a programmer's problem". As one of the users (a designer, incidentally) put it recently on the mailing list: Sass is for people who write CSS. This include
92.
by nex3 17y ago
CleverCSS has a significantly smaller feature set than Sass. It doesn't support mixins, dynamic selectors, and a host of other Sass features.
93.
by nex3 17y ago
The idea is that it's the demise of CSS as the primary language used to style webpages . CSS would still be used as a compile target, but most people would write in higher-level languages like Sass or its descendants. "Demise" here is prob
94.
by nex3 17y ago
I suspect you aren't using it to its full potential. It's not enough just to take bits of CSS that are exactly the same and put them into mixins. When you start seeing patterns, places where you're using the same idea with slight variations
95.
by nex3 17y ago
The Sass site has made the conscious decision not to support IE6, seeing as it only comprises about three fifths of a percent of its visitors.
96.
by nex3 17y ago
But that's not the first example. The first example is the clock, which the page says is "terse but complete", and which uses very few names longer than three letters and very little whitespace.
97.
by nex3 17y ago
Agreed. I was happily playing through until, in the course of a particularly involved battle, I paid too much attention to my enemies and stepped a little too far up and had to go back two rooms. This was frustrating enough that I decided t
98.
by nex3 17y ago
Any CSS preprocessor is basically transparent in its native language (in this case, PHP). The only time systems like Sass need a compile step is when they're being used with languages other than those they're written in, or with static CSS.
99.
by nex3 17y ago
When I'm signing up and I have focus on the last form element, I expect the tab key to go to the "Go" button, not to some "About" link that'll clear my form and make me start all over again.
100.
by nex3 17y ago
The idioms you're familiar with and the idioms the parent is familiar with may not be identical. I've heard "easy as cake" used reasonably widely.
101.
by nex3 17y ago
Why does a screensaver have permission to write to /usr/bin in the first place?
102.
by nex3 17y ago
I don't quite understand why phone manufacturers see it as necessary to make it so hard to attain root.
103.
by nex3 17y ago
I do so because it would get crowded in the front. I carry a lot of stuff in my pockets: keys, phone, notebook, pencil, and wallet. None of those would work well in my back pocket but the (relatively thin) wallet, and trying to stuff more t
104.
by nex3 17y ago
Here's hoping Google News gets an easy way of ignoring articles behind paywalls...
105.
by nex3 17y ago
"Google users may start seeing registration pages appear when they click for a sixth time on any given day at websites of publishers using the program." It's not entirely clear to me that this means that it's five pages from the same source
106.
by nex3 17y ago
Interestingly, just a couple days ago I was talking about Mint to my friends...
107.
by nex3 17y ago
This would require a compatibility layer for the MRI C API, which would be difficult but probably doable. It would only solve part of the problem, though: many of the C extensions exist as bindings to existing C libraries. This wouldn't sol
108.
by nex3 17y ago
Haml, the 10th most downloaded gem on there, still hasn't switched to Gemcutter.
109.
by nex3 17y ago
See http://www.joelonsoftware.com/articles/Wrong.html , particularly the section "I'm Hungary", for a comparison between two different styles of Hungarian notation.
110.
by nex3 17y ago
Yes, we intend to do this as much as possible in the future.
111.
by nex3 17y ago
Requesting an entirely new file for CSS and Javascript is probably significantly more expensive (time-wise if not bandwidth-wise) than sending down more bytes for this one page.
112.
by nex3 17y ago
A follow-up: http://news.ycombinator.com/item?id=662669
113.
by nex3 17y ago
One big problem with making selectors into mixins is that then every mixin takes up valuable space in the CSS file. This is enough of a problem as-is with Sass, although work is going to go into space optimizations in version 2.4.
114.
by nex3 17y ago
Sass actually does have local variables. All variables are local to the level of nesting at which they're declared. Also, multiple properties on a single line is a feature planned for version 2.4.
115.
by nex3 18y ago
Sass 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 t
116.
by nex3 18y ago
For comments, why not just use GitHub's built-in comment feature?
117.
by nex3 18y ago
I'd like to come, but I'm under drinking age I couldn't do it in a bar proper.
118.
by nex3 18y ago
1990, so solidly Gen Y. I remember not having internet access, but I don't remember not having a computer at home. Some of my earliest memories involve playing DOS games. I think 9/11 is a pretty defining moment. I was in 6th grade that yea
119.
by nex3 18y ago
This is even worse than forcing people to set their tab width to a certain value to read your code. If their editor isn't set up for it, they don't just have to change a setitng; if they're lucky, they just have to install a plugin, but if
120.
by nex3 18y ago
I'm a fan of the default syntax offered by [RedCloth]( http://whytheluckystiff.net/ruby/redcloth/ ). It's Textile, but with bits of Markdown thrown in, such as link syntax. It's only available for Ruby, though.

More ›