nothingmuch

A vibrator has a pretty good form factor for insertion into a loaf of bread =)

.oO( a breadbox with speakers inside it to keep bread fresh )

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.

http://skitch.com/nothingmuch/bhdwp/hacker-news-new-links

plz delete

I MEAN ERLANG HAHA LOL:

my website: http://www.erlang.ewebsite.com/page/erlang

ERLAGN!

http://www.cs.rutgers.edu/~ccshan/recur/recur.pdf

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...

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 certain block of code does nothing but link in such deterministic units, removing the nondeterminism of function prototypes.

Most of the source code out there can be parsed statically without resorting to anything drastic. The semantics of this hypothetical Perl 5 variant do differ, but as a strict subset it will still properly most of the useful code out there.

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 continuation you need to apply the reified continuation using call-cc, and it needs to know what to do with this continuation.

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.

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 slow so the 'return' escape continuation is also unusable there is a reason to use goto for this.

DIE IN A FIRE RTARD

Clearly you've neverheard of Common Lisp

LtU

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 operations with no restrictions at all. If there were db level restrictions they could only destroy their own data).

This ALWAYS NEVER EVER type of mentality demonstrates exactly why CouchDB is simultaneously overhyped and condemned.

In fact: http://skitch.com/nothingmuch/bxtct/yuval-kogman-nothingmuch...

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.

dude you totally made my day =D

"... but it does show plenty of promise."

"Personally I would much rather see feature completeness first"