Permalink
Browse files

I hate this markdown formatting

  • Loading branch information...
1 parent 1fee6cc commit 5d19f8a1c4c943563a4c33382aa79e2826100939 Nathan Duran committed Apr 9, 2011
Showing with 1 addition and 3 deletions.
  1. +1 −3 README.md
View
@@ -6,9 +6,7 @@ The rack-mongrel2 gem was supposed to be "the only Mongrel2 Rack handler you'll
1. I don't care about any of that Ruby hippie FFI shit. I use the standard-issue hand-compiled zmq gem and I like it.
-2. I don't ever supply any default ØMQ connection specs since there is virtually NO chance that you will ever setup your Mongrel2 instance the same way I setup mine. Especially not if you're running more than one of them and can't keep recycling the same ports for every app you intend to boot.
-
-This does make the setup code look more like actual code than magic unicorn farts, so some angry Rails teen will probably lock himself in a Peet's bathroom for a week to sob uncontrollably while chanting "D.R.Y." and jerking off to the Kid Robot catalog he carries around in the $300 hardshell backpack his mom bought him to protect his MacBook Pro and Hario ceramic burr grinder after seeing it. I consider this a plus.
+2. I don't ever supply any default ØMQ connection specs since there is virtually NO chance that you will ever setup your Mongrel2 instance the same way I setup mine. Especially not if you're running more than one of them and can't keep recycling the same ports for every app you intend to boot. This does make the setup code look more like actual code than magic unicorn farts, so some angry Rails teen will probably lock himself in a Peet's bathroom for a week to sob uncontrollably while chanting "D.R.Y." and jerking off to the Kid Robot catalog he carries around in the $300 hardshell backpack his mom bought him to protect his MacBook Pro and Hario ceramic burr grinder after seeing it. I consider this a plus.
3. I fixed a longstanding crasher that's been unaddressed for months which was hindering my team's progress.

0 comments on commit 5d19f8a

Please sign in to comment.