Nice work! I've been noodling over an alternate backend metrics store using Redis, but probably closer to Mixpanel than Graphite in nature. I'd love to hear more about your pursuit of a redis solution, and why you abandoned it.
The README on that gist reminds me how fortunate I am to work with Ubuntu servers. Building redis from source on Linux is literally "git clone https://github.com/antirez/redis && cd redis && make". And that's the hard way to install things in DebianLand.
Maybe npm loves moe, but it hates me. I had to downgrade my version of node to 0.4.12 to even get NPM to install on my Mac. The error I was seeing was identical to one that had been seen (and reported in the Github issues list) by several other people 6 weeks earlier.
The issue was seemingly marked as "Closed" on June 27th, a full 2 days before a fix was released for testing. It subsequently broke again and stayed broke for, well, I don't know, because I still haven't upgraded my node for fear that NPM would break again.
I'm confident that it's me and not you, but I think I'll stick to pip/virtualenv as my package managers of choice, thanks.
Something very similar to this has been in my ~/project_ideas folder for the last year or so. It comes from the Department of Itch Scratching and I think there's a market out there for a holistic in-house vcs/issue/deployment management tool.
Kudos to the Springloops devs for executing on a vision. Hopefully I'll get to take it for a spin before too long.
A quick note to those python devs out there who have to wrap SOAP APIs and haven't discovered it yet, https://fedorahosted.org/suds/ is a very clean and pythonic SOAP client library.
It's developed by a man named Jeff Ortel (on behalf of Red Hat, I believe), and it kicks the pants off of SOAPpy/ZSI/wsdl2py or whatever else you're using. You're welcome.
This has been my exact experience wrapping several big SOAP APIs.
Worse still, I've (recently!) wrapped an XML api that cares about the document-order of sibling elements. It might as well be a binary format if I have to copy your request examples and can't use a bog-standard XML parser/generator.
General IT: Sales of MSFT's Kinect will surpass XBOX sales.
Web Development: Python will get a library/framework that is a paradigm shift in writing apps for real-time clients. Something that ties together Twisted's reactor with Django's approachability with socket.io.
Personal: I will finish building my house, then focus on shipping a single side-project.
I "learned C" in my CS101 classes as a first language. I liked it, and was able to get around a little in it, but I never retained any of it. I plan on studying this book. Here's my "gimme, gimme, gimme" list:
- Please make it bulletproof code, as mentioned above. I would hate to spend time relearning C the hard way AND the wrong way.
- Please get me to the point where I can make use of other libraries effectively. I'd like to understand the include/linking process at least as thoroughly as I understand python's import process.
I read the whole thing, but I was unable to visualize the vulnerability after about the second paragraph describing it.
Maybe it's more mundane than I picture in my head, but I would love to look over someone's shoulder as they went through that process.