mhashemi

11 ms·

121.
by mhashemi 12y ago
they're so close to alphabetical; this is killing me
122.
by mhashemi 12y ago
I realize this is a day late and thus ancient history in HN time, but I figure a reply couldn't hurt. You're absolutely right that it would be unwise for the typical Python team to fully adopt the stack, especially this early in t
123.
by mhashemi 12y ago
That's a pretty coarse description of the Python concurrency landscape. "things are moving away"? For one, there was never really official Python backing for gevent and other coroutine-oriented programming models. Remember as
124.
SuPPort: Evented Python servers(paypal-engineering.com)
51 points by mhashemi 12y ago|12 comments
125.
by mhashemi 12y ago
I figured 2500 words was quite enough for an introductory post. It definitely has happened, multiple times, but the rather mundane specifics will have to wait til a future post :)
126.
by mhashemi 12y ago
Unfortunately, unequivocally, yes, there is so much misinformation. I definitely would not have spent so much time on citations, otherwise ;)
127.
Smart Pipe: No pipe is smarter(youtube.com)
4 points by mhashemi 12y ago|2 comments
128.
by mhashemi 13y ago
(N.B. for returning visitors: The sooner you force-refresh, the sooner freegeoip.net rises again.)
129.
by mhashemi 13y ago
Backstory here: freegeoip.net has an hourly per-IP limit, so we distributed the load by doing the geolocation from client browsers. This borked freegeoip after many hours of Twitter/Ars Technica'ing. It was a good thing Github got its stora