Comments on: wiggum thread summary wanted

wiggum thread summary wanted

stupidsexyFlanders — Mon, 11 Jun 2007 06:49:56 -0800

I'm vaguely interested in the Ralph Wiggum thread but at 350+ comments I'm afraid to enter. Please summarize the general drift of it, including excerpts and/or links to any particularly entertaining portions. Thank you.

By: graventy

graventy — Mon, 11 Jun 2007 06:53:35 -0800

Hahahahhaha. No.

By: These Premises Are Alarmed

These Premises Are Alarmed — Mon, 11 Jun 2007 06:57:16 -0800

I ran it through Mac OS X's "summarize" service for you:

Even if the writers and everyone involved meant that Ralph was dreaming of being a Viking, doesn't it give you (the non-champion people) any satisfaction out of letting your brain hear it the other way?

Oh well, sometimes Summarize produces hilarious results.

By: flapjax at midnite

flapjax at midnite — Mon, 11 Jun 2007 06:59:06 -0800

Metafilter: I'm afraid to enter.

By: cortex

cortex — Mon, 11 Jun 2007 07:01:56 -0800

Two major positions are argued for: Ralph as literal (if poorly conceived) viking warrior in dream, and Ralph as metaphorical champion-of-dreaming achiever. Passions run high; both sides argue sternly, one from a position of Occam-driven simple-as-correct, the other claiming the need for a more inclusive and nuanced analysis in deference to the subtlety of the writing staff. Tertiary positions pop up, arguing compromises, alternate readings, and explanations of all the previous from a few different angles. Questions of the authenticity of the debate itself arise, and are neither verified nor satisfactorily dismissed. There's a fair amount of cursing, and discussions in more or less blunt terms of the possibility of high-functioning autism as the causal force behind the metaphorical-viking arguments. The next day, someone posts a bizarre summary request to Metatalk, and after offering a token summary, a site administrator suggests that interested parties should really probably just read the thread in question instead of starting a new one here, and then promptly closes this.