2005/09/30 by David Roundy · 1 citation
Engineering · Computer Science · #Intravenous Infusion Technology and Safety #Computational Physics and Python Applications #Haskell #Computer science #Programming language #Process (computing) #Functional programming #Control (management) #Artificial intelligence
paper · doi:10.1145/1088348.1088349
openalex publication_date 2005/09/30 · openalex created_date 2016/06/24 · openalex updated_date 2026/07/29
A common reaction from people who hear about darcs, the source control system I created, is that it sounds like a great tool, but it is a shame that it is written in Haskell. People think that because darcs is written in Haskell it will be a slow memory hog with very few contributors to the project. I will give a somewhat historical overview of my experiences with the Haskell language, libraries and tools.I will begin with a brief overview of the darcs advanced revision control system, how it works and how it differs from other version control systems. Then I will go through various problems and successes I have had in using the Haskell language and libraries in darcs, roughly in the order I encountered them. In the process I will give a bit of a tour through the darcs source code. In each case, I will tell about the problem I wanted to solve, what I tried, how it worked, and how it might have worked better (if that is possible).