notb

I think that's a pretty poor practice. It's actually counter to central idea of this article; that you should think with the language features. In situations like the one above, if you dont want to lose the context of "this" you can explicitly bind an object to be this and return the new bound function. See underscore's bind(). Its a little more verbose and clunky but it saves you from tossing out modular code.

I agree with contentEditable. The textarea seems to bug out sometimes on WebKit and renders incorrectly.

I would say yes if you build the Clojure component as a separate service that the Rails app makes calls to. Or I guess you could simply build it as a Java class and use Rails to execute it.

I think your negative sample set is a little biased. Since all the phrases start with verbs like "was in the car" or "went to the park", these kinds of phrases are given lower probabilities.

For example:

    > twss.prob("was on a stiff pole");
    0.016050826334564946

Only 1.6% chance of that's what she said?!?

EDIT: Counter example:

    > twss.prob("that's one stiff pole");
    0.9767718880285885

Looks like real-time Pokemon. I'll buy it.

For some reason, in Chrome 13 on OS X, some of the UI animations cause the browser view to go black for a second and redraw. Not sure if this is just a Chrome bug but it's really obnoxious and means I won't use it until it's smoother.

What about WePay!? 3.5% flat fee. Supports international payments. Dead simple API. No merchant account required! Plus, it's only 50¢ for e-checks vs Noca's 1.49%. https://www.wepay.com

A raid in this sense is a start-up venture or any development job I guess. And the advice is to not try and develop the next Google because most attempts are unsuccessful. And that if you're capable of developing the next Google you should just spend your time doing something else because you wouldn't have to work very hard.