wylee's comments

> Free markets when supported by strong property rights can have strong protections to prevent harm or pollution.

This seems to imply that such markets aren't actually "free" since they're regulated via the enforcement of property rights.

I mostly use GitHub these days (at work), but I think Bitbucket is pretty similar in terms of features and may even be better in some ways (e.g., I like Bitbucket's design better, and they give you unlimited private repos). I don't think you could say GitHub is miles ahead of Bitbucket, except maybe in terms of users.

Regardless, I agree that more competition is good.

I'd guess the scenario is more like a social setting where you know some of the people and don't know others. And you're having a "what do you do?" kind of conversation where you respond with "computer stuff" and then the person you're talking to, or someone in earshot, says something like "Oh, maybe you could help me with mine...".

That's happened to me several times. I've also had people do a similar thing in work settings--people who weren't even direct coworkers.

I agree with you, but only for local commits that haven't been pushed to a shared repo.

Rewriting local history seems no different than rewriting code in your editor.

Rewriting shared history is (almost) always bad.

> The obsession of git users...

That seems overly broad. It seems to me that most people who use git agree that public history shouldn't be rewritten, especially on master.

> The whole point of history is to have a record of what happened.

On the other hand, a bunch of "Derp" or "Whoops" type commits aren't very useful. It's definitely beneficial to clean that sort of stuff up by rewriting local history before pushing.

Everything in Python is an object:

    >>> isinstance(type, object)
    true
    >>> T = type('T', (), {})
    >>> isinstance(T, type)
    True
    >>> isinstance(T, object)
    True
    >>> isinstance(T(), object)
    True
    >>> isinstance(int, object)
    True
    >>> issubclass(int, object)
    True
    >>> isinstance(1, object)
    True

That doesn't seem funky to me, given that `x` in your example is in fact not local to `inner`. It may seem surprising, but it's consistent with how Python handles locals in general.

Did you factor in the energy that goes into producing vehicles, building & maintaining roads, etc? Or did you just count tail pipe emissions? What all factors did you consider when assessing the impact of the fleet?

I'm not sure what your use case is, but you may want to look at serializers.RelatedField.

> I wonder how often it actually comes into play

I've wondered the same thing in the past, but just recently I converted two Django projects at work from MySQL to PostgreSQL. The transition was pretty much seamless--I didn't have to change any application code.

One of the projects was converted to add spatial capabilities via PostGIS. The other was converted due to an issue with how MySQL stores data (it ended up being easier in a time crunch to dump and reload into PostgreSQL than fix the issue with MySQL).

I think it's more accurate to say that it's because open office are cheap (*up front). It's pretty clear that they reduce efficiency in many, if not most, cases, which can be very expensive.

What about burning just those pages of the Bible that condone slavery?

> 1 When in doubt, wear a suit

As general advice, this is wrong. There are a lot of positions where wearing a suit to the interview would automatically mean you won't get hired.

Of course, it depends on the locale, the position, &c, but the idea that a suit is always safe is somewhat outdated.

I'm not a huge fan of Obama, but do you really think the surveillance state was created during his presidency? This type of thing has been going on... well, probably forever. It's gotten more sophisticated in the Internet age, but that started before Obama too.

The notion that we don't "pay atrociously high fees" to own and operate cars is a pet peeve of mine. People look at bus fare, for example, and think it's a lot, but compared to the actual cost per mile of driving (payments, insurance, fuel, maintenance, &c), it's often cheaper, even for short trips.

And this doesn't even get into the costs of pollution (including noise pollution), deaths, injuries, and poor health associated with sedentary lifestyles.

I used Eclispe/Aptana/PyDev at a previous job and it was pretty nice, but PyCharm is superior in my opinion. In addition to great completion and code navigation, it also gets Vim emulation mostly right. PyCharm is also a mostly out-of-the-box experience, whereas it took a while for me to get Eclipse set up just right.

I use this sox command:

    #!/bin/bash
    play -q -c 2 -n synth brownnoise band -n 1600 1500 tremolo .1 30

You can adjust the frequency and other parameters to suit your environment. Adding tremolo makes it sound a bit like ocean waves.

That version (and the one in the article) are somewhat confusing to parse and detract from the point of the article.

This seems more "Pythonic":

    def lookup(d, key):
        return Just(d[key]) if key in d else None

    def values_in(keys, d):
        values = []
        for k in keys:
            x = lookup(d, k)
            if x:
                values.append(x.value)
        return values

If you really want a one-liner, I think this is easier to understand:

    def values_in(keys, d):
        return [x.value for x in (lookup(d, k) for k in keys) if x]

I think it's pretty safe to go with Python 3 for new and/or personal projects. I started moving all my stuff to Python 3 a few months ago and Fabric is the only major project I use that hasn't been ported.

How does the GPL prevent this?