icky

inordinate

> print word

> where does "word" come from?

    >>  def Monkey(word):
    >>        class _Monkey(object):
    >>            def shout(self):
    >>                print word
    >>        return _Monkey

> Anyway, this setup is in no way different to ruby's super

> super("foo") super("bar")

No.

    >>    class Chimp(Monkey("foo")):
    >>        pass
    
    >>    class Gorilla(Monkey("bar")):
    >>        pass

That is what the parent poster has challenged anyone to reproduce in Ruby.

> Grow up. Use what you prefer, and end this stupid war.

Programming language wars are at least as old as the Internet, so the admonition to "Grow up" hold no water in this case.

I could quite reasonably parody your closing statement as: "Grow up. So who cares whether a hammer or celery makes a better tool? Just leave us alone, hammer-users."

I graduated high school in 2000, and it was a rude awakening.

Add git rebase -i into the mix, and I can wrap up all my externally-uncommitted changes into one perfect changeset.

Exactly how do they plan to let employees sell stock without accidentally becoming a public company?

Is this stock being sold back to the company itself?

A better metric of fairness would be, how equal were the opportunities to become profession X?

If being a banker is so great, and being a teacher is so (comparatively) awful, then wouldn't it be fairer to simply equalize the opportunities, and let a glut of bankers and a shortage of teachers balance out the wage difference?

> It's not about how hard you work, it's about how much free time you have left AFTER work.

Your suggestion-- that income should be justified based on how much of someone's life is eaten by their job-- smacks of the same kind of moralistic posturing for which you criticize the author of the original piece.

Rather than try to morally justify or attack these inequalities (which I regard as silly as trying to morally justify or attack a rainstorm), I'd like to explore ways that the aforementioned teacher might slice himself a bigger piece of the pie.

Imagine that teachers were all free agents. Self-employed contractors free to negotiate their own rates for their services, and free to choose their students from the applicants they consider most promising.

The better teachers would probably make more money than they do under the current system, but still probably nowhere near as much as the successful banker or lawyer.

The exception might be the exceptional teacher who already has a track record of producing Nobel laureates, world leaders, curers of disease, self-made billionaire inventors, etc.

By the time this teacher could command the truly huge rates, he would be pretty old, and might well consider this new windfall to be merely the capstone of an already satisfying and distinguished life.

But the banker and the lawyer sink or swim based on goals that are directly measurable in the short term, so the same cycle that I've postulated for the old teacher (perhaps several lifetimes old!) can happen on a scale of months or years.

So, to achieve parity with the world-class banker or lawyer, the world-class teacher needs not just free-agency, but fine-grained, objective, fast turnaround metrics of performance that directly correlate with economic return.

Do you still not know who Mitch Kapor is?

Is this legal advice?

The portion of Hobbes that is real is just an inanimate stuffed toy tiger. Hobbes as a motile, living, thinking being exists entirely as a figment in Calvin's mind, projected into the object of the toy tiger. So Hobbes the toy is real, while Hobbes the being is imaginary.

That's when you chip in with your friends/coworkers, get one wireless account (assuming you all go to the same store on a reasonably fixed schedule), and bring in some dd-wrt/openwrt/tomato routers (with all but one of them in bridge-mode), and have the master router set up with WPA2 on your side and either OpenVPN at the router level, or just use whatever external SSH boxes you've got as SOCKS proxies. (If you care, remember that Firefox doesn't proxy DNS requests over SOCKS unless you set the about:config item network.proxy.socks_remote_dns to true).

Also don't forget to bring power strips, since you're bringing in more hardware.

You wouldn't be working in the porn industry, perchance?

(Hell, Hobbes minus Calvin would be trippy enough, since Hobbes is the imaginary friend...)

I always assumed that the Joker had secretly swapped the detonators (i.e., you push the button, and the ship you're on is the one that goes).

Instead of using an ORM, I've discovered an amazingly flexible, efficient DSL for dealing with Postgres. It's called SQL. ;-)

I wrap my model objects around sql queries, so, externally, the objects have a nice ORMey OO interface, but internally I can do all sorts of wonderful Postgresql magic).

After the first time you do it, making a new microframework usually takes less than a day, depending on what else I have to get done. (The reason I reimplement is to prevent myself from adding useless features that I "might" need someday on some future project).

One of these days, I might release one, but strictly as a code-dump example, not as an ongoing project.

(Back on topic, my recommendation to the OP is to start with Django. It's beautifully designed, and has served me well even after I stopped needing its code).

We're actually just flattering you so you won't come pillage our coasts anymore. ;-)