jamwt

32 ms·

241.
by jamwt 16y ago
Sorry for the length. I'd write a tl;dr but I can't stomach the idea of people reading random shit online being picky about their time. I try not to generally opine too much. I think maybe I'm too cynical, too weary of ideologues when I
242.
by jamwt 16y ago
I agree; I don't get all the fuss about "single server durability." Single servers fail all the time. After many hard lessons learned, I just assume that if it's only on a single server it's as good as gone. Bad RAID controllers, etc. If
243.
by jamwt 16y ago
My answer, as someone who recently switched an AMQP backend to using redis for queues and pub/sub broadcast: AMQP is wrong the same way RDBMSes or Java are "wrong." It's too heavy, too slow, or too complex for a great-many use cases. There
244.
by jamwt 16y ago
Yeah, PEP 380 definitely adds some more heft to generators-as-threads, removing a fair number of the problems I cited in that post.
245.
by jamwt 16y ago
Yep, this was a big part of why I eventually abandoned generators in diesel in favor of a greenlet-based approach. http://github.com/jamwt/diesel/commit/2fc64f9d50bc6f9a5cfff0... I'd worked my way through all the problems having to do wit
246.
by jamwt 16y ago
Unless I'm misunderstanding you, you seem to be conflating purity with callback vs. coroutine--I'm don't know why the second would have any bearing one way or the other on the approach to the first. If you don't want global variables, don't
247.
by jamwt 16y ago
I don't know how to completely address your post b/c it responds to assertions I didn't make. I said nothing about "Serious Business"--and bundling threads and coroutines together is like bundling horseshoes and bicycles. I made no defens
248.
by jamwt 16y ago
I think javascript is a fine little language. But: I don't make my server-side language decisions based on what happens to be in the browser. To think that a language required for use in such a constrained environment is just _coincidental
249.
by jamwt 16y ago
While I think it's great that more and more developers are being exposed to building network applications using async I/O (which I guess is "evented" now) via Node.js, I think it's worthwhile to point out that the state of the art has moved
250.
by jamwt 16y ago
I'm a big fan of MongoDB, and I think its replicated durability characteristics are good enough for many classes of applications. If you could lose a minute of data and have it just be "bad" instead of "customer enraging and business thr
251.
by jamwt 16y ago
MongoDB + Redis at http://bu.mp/ . Some PostgreSQL for offline analytics later on.
252.
by jamwt 17y ago
Thanks for the heads-up. We're just re-deploying (today) some of our website on a new platform, and still working out the kinks.
253.
by jamwt 17y ago
Related: http://sqlonrails.org Full disclosure: I was part of the team (with mrshoe, chmullig) that put it together for 4/1/06.
254.
by jamwt 17y ago
If you're doing SSL work, something that does SSL decryption needs to be in front. So I can't do my fancy HAProxy routing rules on HTTP requests HAProxy can't read--it would be reduced to a simple TCP-level balancer then. Basically, nginx i
255.
by jamwt 17y ago
HAProxy supports sophisticated balancing schemes, rule-based backend selection, etc. I.e., if Host header is X, and Ip is Y, but no cookie was provided, then use pool... with this balancing scheme. nginx's proxy setup out of the box is usef
256.
by jamwt 17y ago
Oh yes, lots--works fantastically well. http://shoptalkapp.com is nginx -> haproxy -> (cherrypy/diesel)
257.
by jamwt 17y ago
Oh yeah, the BASIC on those TI calcs! I spent every calculus class working on various things. My proudest accomplishment was a blackjack game. I implemented drawing routines for every card type, which was really painful given the graphics
258.
by jamwt 17y ago
factorial(30..50) -- for factoradics ( http://en.wikipedia.org/wiki/Factoradic ). Representing the reproducable state of a list of randomly ordered items.
259.
by jamwt 17y ago
Yeah, diesel ( http://dieselweb.org ) takes this approach.
260.
Convince me to ride roller coasters(shoptalkapp.com)
6 points by jamwt 17y ago|5 comments
261.
by jamwt 17y ago
Okay, the "comet" bit, I can see that--why conflate those? To clarify--we're going to build a comet framework _on_ diesel, but diesel itself is more of a general async I/O system with cluster messaging features. We intend it to be applicab
262.
by jamwt 17y ago
So, maybe we agree? Because I'm not disputing (and never have) that the message broker is the place to do that. But you seem to be conceptualizing the message broker as a separate _service_ or application, and I'm saying it's just a funct
263.
by jamwt 17y ago
I'm not sure what main application you're referring to. Every diesel node is an instance of an application that is willing to be provide a service that acts as the master/router for a certain class of messages. Paxos ensures there is only
264.
by jamwt 17y ago
Right, but those message queues themselves implement Paxos or have some master election scheme, etc (if they promise replication/failover). You have to get that durability somewhere. So, we're internalizing that queueing behavior into dies
265.
by jamwt 17y ago
Yeah, we didn't get a chance to change that headline before the project leaked out there. The next two phases of the project will get higher-level and build out our "real" goal: a bitchin' comet framework. But you're right, it doesn't have
266.
by jamwt 17y ago
It's a styles thing. Twisted is a very capable system, very well written, with all kinds of capabilities that diesel doesn't have and never will. So it's not a capabilities thing. It's written by a team of guys who are crazy smart, and who
267.
by jamwt 17y ago
Hi, author of diesel here. I can only assume you're probably referring to some of these things: 1. Response latency, esp at 99%-ish mark, under load 2. Memory usage per connection under many idle connections 3. Scalability wrt. data shari
268.
by jamwt 17y ago
Cho's is still there, and it's still serving out delicious pot-stickers and dumplings for cheap.
269.
by jamwt 17y ago
Cofounder of http://shoptalkapp.com . At this point, we all three (co-founders) participate pretty evenly in the hacking, strategy, marketing, etc.
270.
by jamwt 17y ago
We also intend on offering downloadable archives, along the "your data belongs to you" lines. We're just a service.

More ›