nothingmuch

7 ms·

1.
Where are the open edges?(blog.woobling.org)
3 points by nothingmuch 16y ago|0 comments
2.
by nothingmuch 17y ago
A vibrator has a pretty good form factor for insertion into a loaf of bread =)
3.
by nothingmuch 17y ago
.oO( a breadbox with speakers inside it to keep bread fresh )
4.
by nothingmuch 17y ago
Exactly. It's funny how commenters keep clinging to Erlang as if I said it was purely functional, when I'm actually talking about writing purely functional Perl (and to the extent that it's possible, C). Oh well.
5.
by nothingmuch 17y ago
http://skitch.com/nothingmuch/bhdwp/hacker-news-new-links
6.
by nothingmuch 17y ago
plz delete
7.
by nothingmuch 17y ago
I MEAN ERLANG HAHA LOL: my website: http://www.erlang.ewebsite.com/page/erlang
8.
by nothingmuch 17y ago
ERLAGN!
9.
Gospel of Consistency(blog.woobling.org)
15 points by nothingmuch 17y ago|1 comments
10.
by nothingmuch 17y ago
http://www.cs.rutgers.edu/~ccshan/recur/recur.pdf
11.
by nothingmuch 17y ago
Interestingly, C suffers from a somewhat similar ambiguity, where not the results of runtime-at-compile-time but rather type definitions affect the parsing. http://calculist.blogspot.com/2009/02/c-typedef-parsing-prob...
12.
by nothingmuch 17y ago
There's nothing preventing symbol table modifications done by Perl modules at compile time to be reified into some sort of linkage unit, with which a parser could then statically parse the code. Similarly it's possible to prove that a certa
13.
by nothingmuch 17y ago
the delimitation is not for data (that is closed over like any normal closure), it's for control. when you apply a reified delimited continuation as a function it returns a value to that call site, to do the same with a traditional continua
14.
by nothingmuch 17y ago
can you please point to a real example of code like this? just because a pathological case is possible, doesn't mean that it's actually common, or even existent.
15.
Delimited Continuations for Perl(blog.woobling.org)
24 points by nothingmuch 17y ago|3 comments
16.
by nothingmuch 17y ago
this is solved ore cleanly with escape continuation/exceptions. Perl also provides 'last LABEL', which is handy (lets you break out of any level of nesting). I guess in a language like C where you can have neither and function calls are slo
17.
by nothingmuch 17y ago
DIE IN A FIRE RTARD
18.
by nothingmuch 17y ago
Clearly you've neverheard of Common Lisp
19.
Users, Accounts, Identities and Roles(blog.woobling.org)
5 points by nothingmuch 17y ago|0 comments
20.
by nothingmuch 17y ago
LtU
21.
by nothingmuch 17y ago
If the business logic is implemented in couchdb or implemented in serverside code, it's still business logic protecting the data. It could be just as flawed, or even worse (e.g. sql injection allows malicious users to run database operation
22.
by nothingmuch 17y ago
In fact: http://skitch.com/nothingmuch/bxtct/yuval-kogman-nothingmuch...
23.
by nothingmuch 17y ago
If you had actually read my criticism you'd see that I do get what it does. I'm not faulting the design, I like it a lot, it's just that the implementation has issues that caused me to favour other schema free backends.
24.
by nothingmuch 17y ago
dude you totally made my day =D
25.
by nothingmuch 17y ago
"... but it does show plenty of promise." "Personally I would much rather see feature completeness first"