A long thread of discussion covering the PEP 333 and the decoding of the PATH_INFO attribute in the environ dict. Final verdict – its sucks, but it should be decoded. Reason being the CGI spec, which the PEP 333 refers to says so. I encountered this issue when I noticed that wsgi-inspect does not actually decode the PATH_INFO attribute.
A great collection of notes on how to hack TiddlyWiki. TiddlyWiki is one of those excellent examples of a completely javascript based web application, with the potential of working in a distributed, semi connected environment. With things like Gears and TiddlyWiki one can imagine web based application that work offline, and sync online seemlessly. Something to bite into soon.
"I think it’s because institutions are so good at squeezing the fun out of everything. It’s appalling for example how schools can take the most vibrant topics and mangle them into formulaic, mediocre slog. And so it is for programming. Many corporations turn an inherently rewarding experience into something people just barely stomach in exchange for a paycheck." Amen brother.
How to read a barcode from a black and white image of a barcode. Now will need to figure out code that will be able to detect a barcode in an image. Promising nonetheless
Note to self – When encoountering the "Argument list too long" because the bash expansion choked on a large list of files – use "find ./ -name '<pattern_to_match>' | xargs <cmd_to_run>"
An interesting ongoing tutorial on implementing the MVS stack within the browser (A-la JavascriptMVC.com). Looks intriguing and possiby a solution to the mess large javascript applications tend to be. However, the jury is still out (IMHO) as to the whether a MVC framework within the browser is really the best solution for this