Arc Forumnew | comments | leaders | submitlogin
2 points by conanite 5972 days ago | link | parent

Saving client state in closures/continuations is a continuous source of contention. Here's an old discussion: http://arclanguage.org/item?id=1455 , and a more recent one: http://arclanguage.org/item?id=7338

I like the "It's hard to beat closures for elegance" argument, but I haven't really tried the arc way for web apps yet. It's also true that over time we see higher-level languages win out over their lower-level counterparts despite initial objections about performance. So it might be that closures win eventually over initial objections about scalability. But I like readable urls, http://example.com/a?fn=fkg34lk doesn't really tell me anything.



4 points by almkglor 5972 days ago | link

maybe something related to http://decenturl.com/ might help: http://www.reddit.com/r/programming/info/5zcbl/comments/

Edit: It might be useful to add an optional parameter in some of the link-creating stuff where the programmer can add some sort of "hint" which the base system will use, so instead of http://example.com/a?fn=fkg34lk you get http://example.com/a?fn=voteup_fkg34lk

Or possibly just "make it long" and just have the base system add a number if the id clashes: http://example.com/a?fn=voteup-maybe-something-related-to-3

So yes: closure links per se don't prevent decent url's, naive implementations of closure links do.

-----