News for hackers. Stuff that matters.

steveivy

Re:Python StatsD Server on Sunday February 27, 2011 @01:40PM (#2268480)
Getting a server implementation from Joshua Frederick was a nice surprise this weekend (esp. with me feeling sick). Thanks Joshua!
Re:Python client for Etsy's statsd (node proxy for Graphite) on Wednesday February 16, 2011 @10:58PM (#2229674)
Re:Python client for Etsy's statsd (node proxy for Graphite) on Wednesday February 16, 2011 @01:57PM (#2227711)
Thanks; the link is in my post, but when submitting here you only get title and link.
Re:Python client for Etsy's statsd (node proxy for Graphite) on Wednesday February 16, 2011 @12:53PM (#2227384)
I know web developers now who would say "UD-what?"
Re:Python client for Etsy's statsd (node proxy for Graphite) on Wednesday February 16, 2011 @12:52PM (#2227381)
Only as compared to UDP :-)
Re:Python client for Etsy's statsd (node proxy for Graphite) on Wednesday February 16, 2011 @11:35AM (#2227043)
Cool, let me know if you have suggestions, additions.
Re:Python client for Etsy's statsd (node proxy for Graphite) on Wednesday February 16, 2011 @11:18AM (#2226962)
A first pass at a standalone client is now at:

https://github.com/sivy/py-statsd

Re:How did WordPress win? on Thursday February 10, 2011 @09:40AM (#2202045)
(Disclaimer: I worked for Six Apart Services for 2 years)

I don't think MT has "weird perlisms", it's just... written in perl. WordPress took off around the time folks were realizing that you could build big sites in PHP, and so PHP in general was taking off (as Byrne mentions in his piece, more enterprise sites were adopting PHP as well). Perl started a slide back into "sysadmin" land as far as many developers and managers were concerned.

Static publishing is not a "quirk": it's a feature that sold MT to most of the large publishers using it. Yes, you have to make some design decisions with static publishing in mind, but I've never heard of an MT site being Fireballed, either.

Ask HN: Hacker-friendly setup/install tools on the Mac?

After my post about wiring up the Mac app Notational Velocity to a Github wiki got some interest (http://news.ycombinator.com/item?id=2194998), I started working on a more generic solution that any Mac hacker could fork and go with.I've realized that I don't have a good idea of what command-line install/setup tools to use. The solution involves a simple perl script, a .plist file, and some...

( Read More... | no comments | on HN )
Re:Wiring Notational Velocity to a Github Wiki on Tuesday February 08, 2011 @07:00PM (#2195504)
I just realized that NV allows you to specify where to find/save text files (in that little drop-down I'd been ignoring!) I've since cloned my wiki repo to a location in my ~/Documents folder and pointed NV there. Looks like it's going to work.
Re:Wiring Notational Velocity to a Github Wiki on Tuesday February 08, 2011 @06:22PM (#2195369)
Hey, scrod, no prob. Can't believe I forgot it! One other feature I DO love is that the official NV does wiki-style [[links]] that are compatible with github's wiki markup.

Update added.

Re:Wiring Notational Velocity to a Github Wiki on Tuesday February 08, 2011 @05:21PM (#2195187)
Also, I'm told that the "modern" perl way to do this is AnyEvent:

http://search.cpan.org/~mgrimes/AnyEvent-Filesys-Notify-0.05...

Still backed by OS X's FSEvents, so you're not reinventing the wheel.

Re:Wiring Notational Velocity to a Github Wiki on Tuesday February 08, 2011 @05:18PM (#2195175)
I personally use the markdown preview a lot, so it's worth it to me to use nvalt, but I tend to switch back and forth between the two. Does NV offer markdown preview yet? If you're new to NV and don't care about the preview (I may be the only one who does :-) ) then consider the official build by all means.
Re:Wiring Notational Velocity to a Github Wiki on Tuesday February 08, 2011 @04:57PM (#2195102)
Oh, interesting; I was looking for something like this but hadn't worked out what to search for. Will read up on it for sure.
Re:Wiring Notational Velocity to a Github Wiki on Tuesday February 08, 2011 @04:45PM (#2195057)
I haven't wired this up to pull from GH yet, but it's on my todo list.
Re:Tantek Celik on DiSo 2.0 (part 3) on Wednesday May 26, 2010 @03:08PM (#1381293)
I've been after Tantek to explain Whistle (his url shortener) to me for a while now, and I was glad that it fit in with this series of questions. I particularly liked his point about the url being expandable by any third-party because the algorithm is published.

Obviously this prevents some "monetization" of the shortener, but that's the whole point - to prevent your links from being beholden to a single provider.

I'll be continuing the series of interviews as we work through the 10 basic components of Tantek's personal DiSo 2.0 vision.