Copenhagen Suborbitals launched another rocket #space

The rocket launched and flew straight up for a short while, until white smoke could be seen, and the rocket dropped into the ocean.

It was quickly recovered, nose cone included.

Best part: seeing the rocket go up.

Worst part: all the armchair philosophers spouting their "advice" on Youtube.



I have had an ungodly number of open pages in my web browser for months.

After one week of vacation, I finally managed to look/read/skim through most of them. It took a week of vacation to amass the energy to do that.

Still open:

Hopefully I'll get to close those as well, soon.


Source code management history #free software #perl #vcs

In the Hacker News discussion of the open sourcing of BitKeeper (oh, the irony (or not, according to its owner)) there was a cool sub-thread about version control systems development back in the day at Sun:

"Their stuff wasn't ready so I kept working but that made them look bad, one guy with some perl scripts outpacing 8 people with a supposedly better language. So their VP came over and said "Larry, this went all the way up to Scooter, if you do one more release you're fired" and set back SCM development almost a decade" - BitKeeper discussion at Hacker News.


Lisp dialect pop quiz #perl #programming


"Hey, pop quiz! Which of these languages is the best Lisp dialect?

  1. Java
  2. Objective C
  3. Perl
  4. PHP
  5. Emacs

The answer, of course, is [show it]


Quick "host is up" #commandline #email #net

Using ping(8) to determine whether a host on the local network is up is easy, but a bit slow - especially if what you are doing is checking whether it makes sense to ask the jukebox what song is playing, so you can add an X-Now-Playing: header to the email/article you are composing.

So I went hunting for someting quicker, and came up with this little script, using nmap(1):

  nmap -PS --max-retries 1 --max-rtt-timeout 20ms --host-timeout 20ms $CHECK | grep --quiet 'Host is up'
  if [ $RET = 0 ]; then
      echo "UP"
      echo "DOWN"
  exit $RET

Works nicely.


Haskellbook, Twitter and communication - which is hard #community #haskell

This evening, a series of tweets by @haskellbook appeared in my feed in quick succession:

"We do not take feedback or questions via IRC. Please use the recommended community resources for getting help."
"If something is wrong with the book, use the email feedback info on the website."
"We do not take feedback or questions via Twitter. Please use the recommended community resources for getting help."

Which struck me as odd, why write about all they ways you don't want feedback?

So I did what all stupid Twitter-users do, I posted a sarcastic reply:

"Please, oh, please, let us know all the ways you don't want to communicate. We can't wait to hear them all enumerated. #wat"

Not a nice thing to do.

Both authors immediately responded with a couple of tweets, one of which expressed the notion that I should not join the conversation if I did not have the context, as I tried to explain to the two tired authors how their tweets had looked to me.

This is where my age shows.

I knew I didn't know the context. I just saw what my twitter feed showed me, and responded to that. And I assumed that's how it's supposed to work.

I see now that it is not.

If you read something out of context, and in a crippled medium such as Twitter, it is of course your - the reader's - responsibility to research the context. The author doesn't have to care about this!

I never "understood" Twitter (much preferred usenet), and I think this is one of the reasons - discussions are disjointed and incomprehensible, because of the way the medium works.

That's simply how it is constructed, and apparently how it is supposed to be. And I, for one, am not compatible.

So, unfollow it is.

Funnily this happened just after I transferred the newest editiion of the Haskell Book to my Kindle, and contemplated starting reading it. I guess I will wait a while, until the dust settles.


Raspberry Pi 3 #computers #hardware #jukebox

I upgraded my jukebox to a Raspberry Pi 3 yesterday, after becoming exceedingly annoyed by my Raspberry Pi B+ only managing to boot about half the time.

So far: the built in wifi works great, I can run the attached 2,5" harddisk from two of the usb ports, and it boots as it should.

So with the new Pi I have saved using an external USB-hub and an external USB wifi dongle.

Only downside is that I could not make the external usb sound dongle work - it appears in alsamixer, but whatever I do, no sound comes out. The built in sound works, and seems to work better than on the original Pi, where the sound level was unusably low.

All in all, Raspberry Pi 3, thumbs up!


Archive... Search... Keywords...
Publisher at Google+
Sommerhus 2015


GNU (33).


Prins Nikolai William Alexander Frederik (17).

Software Freedom Day (12).


Annisette (Savage Rose) (68).

0.0329 s