jlouis
27. november 2012 - 16:55

A very common thing that crops up now and then is the question in the title. What is fastest for editing text, the keyboard or the mouse? The answer which is an often quoted answer is an older "Ask Tog" article[1a, 1b, 1c]. They come up again and again in these discussions and then the keyboardists battle it out against the mouse-zealots.

Sebbe
31. oktober 2012 - 16:22

Next time you typeset a LaTeX document, where you discuss some Haskell code, consider using the following command to typeset the name:

% To be added to your preamble:

\usepackage{hyperref}
% Format function name and link to it on Hoogle
\newcommand{\hoogle}[1]{\href{http://www.haskell.org/hoogle/?hoogle=#1}{\texttt{#1}}}

That is, instead of I use the function \texttt{liftM2} to lift ..., use I use the function \hoogle{liftM2} to lift ....

jlouis
29. oktober 2012 - 20:26

The following were the initial research requirements for Erlang when they sat out to investigate a new language for telecom[0] (link at the bottom). It is in the thesis written by Bjarne Däcker, and I think it would be fun to scribble down my thoughts on the different requirements. My view may very well differ from the original views, since I came into the world of Erlang pretty late.

jlouis
13. august 2012 - 21:39

To most programmers, the computer is a universal machine in a specific sense. We know, that if we can figure out a program for a problem, we can get any computer to solve that specific problem. We also know, by the rules of computability, that any (common) computer in our usual sense of the term is equivalent. They can solve the same problems and mostly differ in how fast they can solve it or how large a problem they can feasibly work on.

jlouis
10. august 2012 - 18:38

On Curiosity and its software

I cannot help but speculate on how the software on the Curiosity rover has been constructed. We know that most of the code is written in C and that it comprises 2.5 Megalines of code, roughly[1]. One may wonder why it is possible to write such a complex system and have it work. This is the Erlang programmers view.

Rasmus
11. juni 2012 - 12:03

Hej Dikutal

Jeg er medlem af arbejdsmiljøudvalget på diku og er således med til at granske planerne for det nye NBSP. Vi har her til morgen fået udleveret dispositionsforslaget (hvilket er første fase i det egentlige byggeprojekt) og skal derfor til at se de konkrete planer igennem og vurdere om alt er som det skal være.

jlouis
9. juni 2012 - 14:14

One interesting view on Erlang is that it is not really about functional programming that much. With the right kind of glasses on, the functional programs are just what is going on inside the processes of the Erlang program. This may be interesting, but to the outside user of the process, you can't discriminate what the inside looks like.

jlouis
10. maj 2012 - 22:04

One important key aspect of Erlang programs is to identify where your Stable state is in the program.  Stable state is what you can trust. What you can trust is what you can build on. Joe Armstrong defines one of the key aspects of an Erlang system as Stable Storage. A place where we can push data and be sure it won't change. If we verify data before pushing, we can trust those data a great deal.

Sebbe
20. april 2012 - 14:25

skema.ku.dk

So you’re a student at the University of Copenhagen, and you’re starting on a new course. Wouldn’t it be lovely if you could add your schedule to your calendar, so that you could keep track of when to be where?

oleks
23. marts 2012 - 19:46

At the University of Copenhagen in general, and in my view, at the department of Datalogy in particular, there seems to be a common sense of pure and utter hatred towards the digital university administration systems (and in some ways,
administration in general). This holds for the student and employee management system, KU-Net, but by far much more so for the unified course management system, Absalon.