Debian Common Core

This interview with Bruce Perens is pretty interesting, and many good points were made. I know that I would love it if all of the Linux distributions did things the same way at the lowest levels. Of course, I’d also like the kernel developers to take security as seriously as the developers at OpenBSD, but first things first.

An interesting quote from the interview is this: "It used to be that there were lots of nuts with ideas in the world, but they were isolated nuts. In this day and age, there are no isolated nuts. You can always find in the world of the Internet 50 nuts just like you, and what do you call 50 nuts like you? A start-up company!"

The Support Myth

The principle differentiator between open and closed source software these days is supposedly support. The quality gap between the two camps has either closed or Open Source is widely recognized to be superior. The primary reason today for not adopting an open source solution (where there is a business case for doing so) is that there may not be any support for the software. This is certainly a big part of the FUD campaign pursued by Microsoft against Open Source and Linux. I suggest that “the support myth” is just that – mythical.

If you use Windows, are you free to contact Microsoft and ask for help? No, not really – you maintain a busy in-house staff to take care of this for you, and to reinstall the operating system or reboot the workstation or server (!) as your primary troubleshooting methods. If there is a glitch in Word, can you do anything about it? No, you can’t. You can complain and whine, but you cannot fix it or get it fixed. Once a new version of Word is out, you can take your chances and buy a new license, and then hope that your problem got fixed, and that any new features don’t break your workflow, render your old documents unreadable or require a new training course. Most closed source software “support” is not supportive, and can only help you in narrow ways when the software is broken, but never when it’s wrong.

A common complaint of those confronted with the Open Source model is the claim that while you are permitted to change the source of your software, you lack the expertise to do so, which makes it a non-advantage. The counter to this is that, if you need a feature or a bug fix, you can simply sponsor a hack-a-thon to get it implemented, supporting the community and getting your needed fix far faster and more cheaply than hiring a consultant or having fully customized software written. There are a lot of changes required in the way that people think of software development in an Open Source world, but those changes will be easier to make once you shed your belief in the outmoded “support myth”.

vimrc

" It takes a lot of doing to get vim (which is really gvim)
" to behave properly on Windoze, but I've got something that
" works a bit.  I have to turn auto-indenting off because it
" constantly screws up, but it's better than notepad.

colors darkblue
set guifont=Lucida_Console:h10:cANSI
set nocompatible
"source $VIMRUNTIME/vimrc_example.vim
"source $VIMRUNTIME/mswin.vim
"behave mswin
set backspace=indent,eol,start
set ruler
set nocompatible
set showcmd
set ts=4
set shiftwidth=4
set expandtab
set shiftround
set smarttab
set tw=72

set incsearch
filetype plugin on
syntax on

:inoremap ( ()<ESC>i
:inoremap [ []<ESC>i
:inoremap " ""<ESC>i
:inoremap { {}<ESC>i
:inoremap < <>i

iab teh the
iab hte the
iab adn and
iab nad and
iab taht that
iab htat that
iab fo of
iab ot to