nex3

9 ms·

31.
by nex3 16y ago
Running a compiler in the browser in production will never be a good idea. If you care about the speed that your website displays -- and you should -- the slowdown caused by parsing, processing, and concatenating large amounts of CSS will d
32.
by nex3 16y ago
Subversion doesn't have a built-in notion of branches in the same way that distributed systems do. Instead of being names for nodes in the DAG of commits, branches in Subversion are usually handled by manually maintaining separate versions
33.
by nex3 16y ago
I can see arguments both ways. Having the wiki separate means that the repo doesn't get polluted with unrelated commits (especially important for SVN which doesn't have branches), and it makes setup at least somewhat easier, since an extra
34.
by nex3 16y ago
That's an interesting point in light of Rails' recent movement towards more modularity. It suggests that there may be room for a Fossil-like abstraction over Git that has (pluggable?) built-in cloned-by-default issues, wiki, etc.
35.
by nex3 16y ago
To be fair, not all GitHub data is accessible via the API. Messages, pull requests, comments, wiki pages, and some gist functionality all lack API access. Edit: I originally said there wasn't API support for issues, but in fact there is.
36.
by nex3 16y ago
This is exciting news. masklinn is right that it probably won't entirely address Zed's points, but for people like me who don't care as much that it's baked in, this is very cool.
37.
by nex3 16y ago
I think the distribution issue is more about metadata than the code itself: issues, wiki pages, and comments are still centralized on GitHub. With Fossil, I gather, they're distributed among each clone.
38.
by nex3 16y ago
We'll be looking into compiling certain Sass calculations that can't be done at compile time, such as "3px + 3%", into uses of calc().
39.
by nex3 16y ago
The moderators probably fixed the link to circumvent the blogspam.
40.
by nex3 16y ago
The Y axis on this graph isn't labeled. Moreover, it's scaled so that the rise for Bill Gates looks huge compared to everything else.
41.
by nex3 16y ago
From a user's perspective, at least, I would think that language coverage would trump most other things when considering different highlighters.
42.
by nex3 16y ago
Yeah. Syntax highlighting plugins take effort to write for any highlighting library, so usually a major decision factor is the plugins already available.
43.
by nex3 16y ago
I'm surprised they went with CodeRay rather than a more fleshed-out highlighting library. They only list 20 or so supported languages, whereas something like Pygments (which Github uses) supports closer to 100.
44.
by nex3 16y ago
The main reason for the speed increase is that Froyo introduces a JIT compiler. This means that the compiler will be able to examine the running code and make optimizations based on its behavior that can outperform statically-compiled nativ
45.
by nex3 16y ago
This is a great summary of why you get encoding errors in Ruby 1.9, and why #force_encoding is not the catch-all solution. I've lost count of how many times I've had people request that I run #force_encoding on all strings passed to Haml te
46.
Debunking the Google Interview Myth(technologywoman.com)
2 points by nex3 16y ago|1 comments
47.
by nex3 16y ago
Did you find such a Lisp-to-Ant compiler?
48.
Four-Minute Video Introduction to Sass and Compass(vimeo.com)
16 points by nex3 16y ago|0 comments
49.
by nex3 16y ago
I'm curious... why is it that so much antivenin was required? If that much is needed, why do hospitals only stock six vials apiece?
50.
by nex3 16y ago
It's pretty clear in the video that the water is deeper than that. Watch when they fall: they definitely go in pretty deep.
51.
by nex3 16y ago
Poke them to release their formatting code as a library. All you'd really need is a format(text, filename) => HTML function, right?
52.
by nex3 16y ago
border-radius isn't in the spec. The CSS3 Backgrounds and Borders model isn't final yet: it's just a candidate recommendation. See http://www.w3.org/Style/CSS/current-work
53.
by nex3 16y ago
You would also have to avoid juicy foods. You could probably avoid drinking water indefinitely if you ate enough apples.
54.
by nex3 16y ago
Interestingly, Chris Eppstein, my co-developer on Sass, agrees with you that CSS needs abstraction. However, he concludes that Sass is a good language for expressing that abstraction: http://chriseppstein.github.com/blog/2009/09/20/why-sty
55.
by nex3 16y ago
I disagree. One of the main benefits of CSS compilers like Sass and Less is that they can innovate at their own pace, without worrying about any browser compatibility headaches.
56.
by nex3 16y ago
May I self-promote and suggest Sass ( http://sass-lang.org )? It's much older and less buggy than Less, and the currently-in-beta Sass 3 supports a CSS-style syntax ( http://nex-3.com/posts/96-scss-sass-is-a-css-extension ).
57.
by nex3 16y ago
Sass 3 will support a desugared syntax: http://nex-3.com/posts/96-scss-sass-is-a-css-extension
58.
SCSS: Sass is a CSS Extension (nex-3.com)
1 points by nex3 17y ago|0 comments
59.
by nex3 17y ago
Windows XP comes with at least VBScript and JScript ready-to-use for scripting.
60.
by nex3 17y ago
It's actually on GitHub, obfuscation-free (and linked from the site): http://github.com/chromakode/xkcdfools

More ›