The new JAPH signature? I don't know really. I just write, and sometimes weird stuff ends up on the screen. Sorry!
Let me remind you that it was just six (unimpressive) reasons Camping is better than you would imagine, not six reasons Camping is a better fit for your project. All I'm saying is that Camping gets so many things right. Not necessarily in very few lines of code or very fast, but nonetheless: I look at Camping code and nod to myself: "Yeah, this is probably the correct way to do it".
Of course, this doesn't matter at all! If we cared about correctness, we would program in Haskell, not some language where monkey patching is acceptable in production code. As long as you're comfortable in Sinatra, you should continue doing that. It's that simply.
Oh well, let me finish with a little quote from _why:
On Sun, May 25, 2008 at 02:47:39PM +0200, zimbatm wrote:
> This is not that hard to do. Maybe I should add some shortening tricks
> document. I propose platterizing to be done only before release.
No, let's not have rules. I don't feel comfortable with having
coding standards or any protocol on Camping. The point of Camping
is to have very ugly, tricky code that goes against all the rules that
people make for "beautiful" code these days. To show that ugly code
can do beautiful things, maybe.
I don't want to demonize anyone here, I just want to express the
ideas that make Camping different. Camping's personality is 80x50.
It is like the little gears of a watch that are all meshed together
into a tight little mind-bending machine. The challenge of Camping
isn't to figure out how to automate obfuscation. The challenge is
to bring new tricks into the code that push Ruby's parser and make
everyone look twice.
Not all code needs to be a factory, some of it can just be origami.
_why
I saw a very interesting comparison between Ruby and Python that sounds like this. Basically, it went like this: "Python's core language is very simple and pretty, and Ruby's is very complex and ugly. Yet, the very ugliness that Ruby allows and Python disallows means that the libraries that are created with the languages that are the exact opposite: RSpec is a thing of beauty, and something similar in Python isn't even really possible at the same level. So I actually like _using_ Ruby, even if I like the Python language more."
Like you said in both your email and here, it's all about what's best for _you_, not what's best 'in absolute.'
Let me remind you that it was just six (unimpressive) reasons Camping is better than you would imagine, not six reasons Camping is a better fit for your project. All I'm saying is that Camping gets so many things right. Not necessarily in very few lines of code or very fast, but nonetheless: I look at Camping code and nod to myself: "Yeah, this is probably the correct way to do it".
Of course, this doesn't matter at all! If we cared about correctness, we would program in Haskell, not some language where monkey patching is acceptable in production code. As long as you're comfortable in Sinatra, you should continue doing that. It's that simply.
Interestingly, camping.rb on the other hand is not very pretty or correct: http://github.com/camping/camping/blob/master/lib/camping.rb, and that's also what makes it so beautiful in my opinion.
Oh well, let me finish with a little quote from _why: