Diesel Redis, Plus Two Announcements

[jamwt]

I've set up a redis for diesel, to share links and discuss various
diesel-y things:
http://www.reddit.com/r/dieselweb/

RSS here: http://www.reddit.com/r/dieselweb/.rss

I'm not the hugest fan of google groups, so I'm open to exploring
other forums for community communication.

Announcement 1:

diesel's repository has been moved to github (and, naturally, git):

http://github.com/jamwt/diesel

Rationale: basically, the size of the developer community in git/
github is just too beneficial for the project to ignore.

Announcement 2:

diesel is moving to a greenlet based approach.

The good:

* A few nasty gotchas coding (yield vs. no-yield, head-scratching
stack traces, `catch` and `up`) go away
* The core is greatly simpler and more robust
* The API and protocol support is almost identical.. it's pretty much
just a matter of removing "yield" everywhere, and doing one or two
more things
* It's much faster (40% for socket-heavy stuff to 200% for pure event/
coroutine work)
* Your apps will be a lot cleaner when you're done

The bad:
* It will break your apps.. I've ported a complex 10k+ liner in a few
hours, so not too bad, but still
* By abandoning the generator approach, diesel has forfeited some of
its... identity?

This new system is in the `diesel2` branch on github. It will become
master in a few weeks, so coder beware! I'll keep the old system
around as `diesel1`, but I won't be contributing any more fixes or
improvements on it.

My goal is to put together a more detailed blog post on the change,
ramifications, upgrade steps, etc, in 1 to 1.5 weeks. In the mean
time, check out the deltas on the examples/ in the git repo between
`master` and `diesel2`.

- jamwt

[jamwt]

Diesel *reddit*, rather. Too much typing of "redis" lately.