camping

and sometimes animations: https://viewsourcecode.org/why/redhanded/ But my own experience of learning from him how to experience code as poetry mostly involved around using Camping in production for some small side projects and needing to explore some bits of its code because of practical reasons: https://github.com/camping/camping

URIComponent,encodeURIComponent] is quite obvious. So is the second line except perhaps for the use of the w function. It splits the input string on spaces in an array and maps the callback passed as second argument (in this case, require, if you didn't scroll til the end of the line). We'll come to its meaning later. n = (p)->p.replace(/\/*$/,'').replace /^\/?/,'/' # normalize?(path??) not sure about his one. # p is also used elsewhere as a generic name. e = (d,s)->d[k]=(if d[k]instanceof Array then d[k].concat v else v)for k,v of s;d) # extend(destination, source) # k and v are obviously key and value. w = (s,c)->s.split(/\s+/).map c] # w(string, callback) In Ruby, w%foo bar baz% is a shortcut for creating an array of strings ["foo","bar","baz"]. The w method here is enhanced version of this, and a nod to _why, who often used it to require a bunch of libraries at the top of his scripts. See for example https://github.com/camping/camping/blob/ddea5760289a4de3c270... For those who don't know about him, _why is the author of Camping, the grand-father of golf Web microframeworks. The current version doesn't use the w trick anymore because the reduction of dependencies made the normal method shorter. Here's the code (possibly NSFL for some...): https://github.com/camping/camping/blob/master/lib/camping.r... and its heavily commented (but as terse, codewise) version: https://github.com/camping/camping/blob/master/lib/camping-u... Camping used to be the go to ruby microframework until _why's disappearance. Then dev stalled for a while and Sinatra took its place. It has since been revamped and is actively maintained. Neither Camping nor Berliner are meant for professional use, obviously.

thub.com/camping/camping/blob/master/lib/camping.rb, and that's also what makes it so beautiful in my opinion. Oh well, let me finish with a little quote from _why: On Sun, May 25, 2008 at 02:47:39PM +0200, zimbatm wrote: > This is not that hard to do. Maybe I should add some shortening tricks > document. I propose platterizing to be done only before release. No, let's not have rules. I don't feel comfortable with having coding standards or any protocol on Camping. The point of Camping is to have very ugly, tricky code that goes against all the rules that people make for "beautiful" code these days. To show that ugly code can do beautiful things, maybe. I don't want to demonize anyone here, I just want to express the ideas that make Camping different. Camping's personality is 80x50. It is like the little gears of a watch that are all meshed together into a tight little mind-bending machine. The challenge of Camping isn't to figure out how to automate obfuscation. The challenge is to bring new tricks into the code that push Ruby's parser and make everyone look twice. Not all code needs to be a factory, some of it can just be origami. _why