News for hackers. Stuff that matters.
Re:How to write a filesystem in 50 lines of code by TallGuyShort on Thursday July 08, 2010 @12:27PM (#1497840)
Although I think they're overdone, I think "x in y lines" is avery relevant to the hacker community, while "x things about y" isn't always. Doing "x in y lines" generally implies an unusually elegant solution, that could be of great use.
Re:How to write a filesystem in 50 lines of code by silentbicycle on Thursday July 08, 2010 @01:09PM (#1497984)
It's such an easy metric to game, though ("The first line is 'import library_that_does_everything'") - It's a proxy for succinctness, at best.

That said, "[something non-trivial] in only 250-500 LOC" is often more interesting than "...in only 5 LOC", because generally anything that small is just gluing together libraries. There are exceptions, of course - I've seen impressive stuff in just a few lines of J/K/APL.

Re:How to write a filesystem in 50 lines of code by storborg on Thursday July 08, 2010 @01:26PM (#1498038)
In this case, the tool that he built (RouteFS) is actually a really clever abstraction above two other popular libraries (Routes and FUSE).

I agree it would be neat if he talked more about RouteFS itself, but it is a neat idea, and only about 200 lines.