Someone called Evgeny Morozov has produced this gem in an article at the Wall Street Journal:
the "open-source" software movement, whose activists tend to be fringe academics and ponytailed computer geeks
Have we really not progressed further than that? I guess one should not expect any sense from the WSJ, especially since its purchase by Rupert Murdoch, but it's really time that these tired, clichéd and stupid characterizations stopped. A fellow at the New America Foundation should know better. And the fact that he can write such ignorant and absurd nonsense casts doubt on his whole thesis.
As the owner of one business and part owner of another, both of which do work based pretty much exclusively on open source software, who left academia nearly twenty years ago and has never worn a pony tail, I'm feeling left out. (OK, I own up to the geek part.)
Just a few miles from here is the headquarters of RedHat. They are a poster child for just how stupid and ignorant this image of open source is. The State of North Carolina has just done a deal with them to make sure they stay here and expand. They are a growing, profitable business that contributes a lot to the local economy.
The other day I got annoyed that a number of hosts I connect to regularly via ssh don't set the window title, so with a lot of windows open it gets difficult to see which window is which. So I added a LocalCommand to my ssh config to set it. Sadly, this broke git. So when I went to update my local posgresql repo last night to fix a bug, I got a mysterious error message about a git protocol failure. OK, I thought, I'll turn it off for the git host, and I added an entry like this to my ssh config file:
No dice. Nothing I tried in the config file, other than disabling the local command globally, worked. I ended up following a tip from The Git Wiki and implemented a wrapper that sets the option shown above, and set it as my GIT_SSH setting. Now it all works. But it's a pity one has to do so much work. If git really needs not to have a local command run (and it gets upset by something as simple as /bin/true) then it should force the PermitLocalCommand option off itself.