oh snap! really appreciate the bug report. we'll fix it.

1. oops. thanks for the report, we'll look into it

2. that's kind of our thing, we're gonna stick with it for a while longer :)

Thanks! Congrats on cultivating such a promising project!

For $150, this conference is unbelievable.

Guy Steele giving the keynote on day one, Douglas Crockford talking day two.

Bradford Cross from Flightcaster, Chris Houser (Clojure), Jeff Brown (Grails), Kevin Well (analytics lead at Twitter) it's story-time with some of the world's greatest programmers and problem-solvers.

I was wholly expecting his argument to address this quote:

If developers grow dependent on third party development libraries and tools, they can only take advantage of platform enhancements if and when the third party chooses to adopt the new features. We cannot be at the mercy of a third party deciding if and when they will make our enhancements available to our developers.

with respect to "private api" arguments made here: http://www.marco.org/500743718

I actually did a === check for just that reason, since if you define _ = {}, then passing in a real object that is {} will also return true for _ == {}

Nope:

    js> a = {}
    [object Object]
    js> b = {}
    [object Object]
    js> a == b
    false

== only casts between certain primitive types, it doesn't do a deep comparison:

    js> x = null
    null
    js> y = undefined
    js> x == y
    true
    js> x === y
    false

Also undefined comparisons are still true with ===:

    js> var _
    js> _ === undefined
    true

But you're right, === should be the default choice, and only use == if you have a good reason.

feel free to correct me if I'm wrong, but I thought that GreaseMonkey scripts run on the same page, but in no way _replace_ the scripts a site serves.

what, I think, Stallman envisions is being able to use your local copy of Gmail instead of the one Google's serving you without any loss of functionality.

GreaseMonkey scripts can modify the page contents, and if only GreaseMonkey scripts could run before whatever JavaScript is included with the page could start, then it could completely replace the site's script rather than just modifying its behavior shortly after the site's script begins to run. I think so anyway, I haven't actually implemented this so I won't claim to know for sure that it can be done.

Chromium has this "early injection" feature for GreaseMonkey scripts, so that's one free browser for which it would be very easy to build Stallman's replacement feature. See the link I gave earlier in this thread and also http://www.mail-archive.com/chromium-discuss@googlegroups.co... for some background.

I'd like to see this applied as an embeddable feature in hacker news. see who writes comments, which comments get commented on and what people really have to say before they hit that 'add comment' button

See http://www.sothebyshomes.com/ I know a little about the Sothebys site, as the company I work for created it, and I wrote a fair bit of the Javascript myself.

The original site makes extensive use of js to load content, and anywhere data is missing on the pirated site, that's why.

What we can't figure out here in the office, is why they did it? How much of this is going on?

looking at the two side-by-side, you can see the few places they had to substitute their own text, which almost always sucks.

phew, what would you do about such a thing?

the trans-equatorial railway express, of course, ol chap!

but, uh, (slightly) more seriously, if one big transmitter is the problem, then isn't the solution multiple small transmitters in the the same orbit, repeated at increasingly closer-to-earth orbits? then you could just run a wire up to a transmitter in geostationary orbit.

A compiler that takes Sed programs and produces Parrot interpreter code. It was a project in a college Compilers class that I didn't take seriously enough, so I'm revisiting it to see if I've actually grown better at this programming thing since I've graduated.