Comments on: MythBusting — Merb Style

By: Nicolás Sanguinetti

Nicolás Sanguinetti — Fri, 21 Nov 2008 17:38:41 +0000

Er, sorry, 798 — 553 is in the branch were the framework is being rewritten, but since it’s not stable yet let’s not count it, it wouldn’t be fair, would it? ;)

By: Nicolás Sanguinetti

Nicolás Sanguinetti — Fri, 21 Nov 2008 17:36:57 +0000

Wait, you want …. what, something that handles the request/response cycle and is able of rendering a view in one of many formats, using one of various adapters, like ERB, haml, or whateverthefuckyouwant?

http://sinatrarb.rubyforge.org

$ cat lib/sinatra.rb |grep -v "^[[:space:]]*$" |grep -v "^[[:space:]]*\#" |wc -l 553

Hah, it seems it isn’t a tie after all.

Oh wait, right, this is to see who has the biggest penis, not what framework you are most comfortable working with. Not to see which framework people relates better to. Or which framework gets the job done. Get back to work and stop wasting time with this shit, please :)

By: Nathaniel Bibler

Nathaniel Bibler — Wed, 19 Nov 2008 02:30:01 +0000

You’ll be happy to see one of the latest Rails core commits, by none other than DHH himself, here: http://tinyurl.com/5ytm2h (GitHub).

Be sure to read all of the hilarious comments that ensue.

By: Matt Aimonetti

Matt Aimonetti — Mon, 17 Nov 2008 06:18:56 +0000

Documentation is coming up, check the latest Merb news where documentation is addressed.

By: vire7

vire7 — Mon, 17 Nov 2008 00:03:03 +0000

I meant @tomas. Sorry, Tomas.

By: vire7

vire7 — Sun, 16 Nov 2008 23:30:24 +0000

@thomas

The pot calling the kettle black? Dude, read your comments again and see if you can spot the hilarious irony as I don’t think it was intentional.

Write some documentation? Do you mean like a $50 book from Pragmatic Programmers? Or like Django? :P

By: Tomas

Tomas — Sun, 16 Nov 2008 10:53:07 +0000

Uh, so the reason why we’re having this LOC contest is supposedly because less LOC makes it easier to understand and familiarize yourself with the code, right?

Write some fucking documentation. That’ll make it much easier than just writing compact code.

Talk about the pot calling the kettle black.

By: raggi

raggi — Sat, 15 Nov 2008 21:46:50 +0000

Why’s everyone still talking about speed, when:

– most users don’t need it
– most apps are slow in THE RENDER PHASE

n.b. none the penis enlargers under discussion here do shit about that issue.

If you have a backend service that needs real speed, I wouldn’t use rails or merb. They’re both shit slow for that. In fact, I probably wouldn’t use any of the webservers you people use either, they’re also very slow. Firstly they do full http parsing (ouch), second of all, they’re synchronous (ouch).

There’s only a handful of us battling those issues, meanwhile you all enjoy yourselves bickering about stuff that doesn’t matter. Neither project will die as a result, you’ll just load up the spamtrains with more goo, and go to bed stressed one night and arrogant the next.

Summary(ish): http://ra66i.org/tmp/rails_vs_merb.html

By: james

james — Sat, 15 Nov 2008 21:28:02 +0000

Competition is great. I love and use both Rails and Merb. Thanks much to everyone who has contributed, innovated, etc.

Rails is getting faster… lately many of my actions are taking < 20ms.

Maybe there can be a mud wrestling ring at the next rubyconf where all the flamers can battle it out in real life… :)

By: wycats

wycats — Sat, 15 Nov 2008 20:19:00 +0000

@pratik checking for a higher version doesn’t work either. You actually need to use the dependency mechanism to allow gem author to state what versions of gems are acceptable.

The reason we’ve had “more” issues is that Rails defers the issues until runtime. By using bundled dependencies and plugins with no dependencies, everything *seems* to work at bootup, but weird errors crop up at runtime that are extremely hard to track down.

I’d prefer to be notified about dependency conflicts up front, even if it means we have to work to improve rubygems so it can handle more complex situations better.