i now know of closures, and have actually used them intentionally, and rarely, and def not enthusiastically. i lived mostly in the java world, and discovered c

i now know of closures, and have actually used them intentionally, and rarely, and def not enthusiastically. i lived mostly in the java world, and discovered closures when i was getting wacky results while playing around with a Clojure looping example. then ran into similar situations about once a year when doing something in javascript -- usually passing some function for a callback, and needing access to 'this' in the original/calling scope - which only confused things when i needed access to 'this' in the (local?) function scope, too. guess i'm not against closures -- they just seem mysterious to me. ditto lambdas. they seem like a good way to write esoteric code, and write more error-prone/less-defensive code -- that, for instance, might be more likely to produce NPEs, and generally be less maintainable b/c of the focus on brevity instead of clarity, and be geared more towards expert users/coders instead of the generalists (like me) who are often brought in to maintain older code.