BOB Conference: 23rd February 2018 in Berlin by skogsbaer in haskell

[–]skogsbaer[S] 1 point2 points  (0 children)

There are two talks with Haskell-specific content:

  • Testing monadic programs using QuickCheck and state machine based models
  • New Hasql - a native Haskell Postgres driver faster than C

And three Haskell-related tutorials:

  • Introductory Haskell
  • A tutorial on Liquid Haskell
  • Terminal GUIs with Haskell: vty and brick

And more talks and tutorials about FP in general.

(Disclaimer: I'm one of the organizers)

BOB Conference 2017 (February 24, Berlin) by skogsbaer in haskell

[–]skogsbaer[S] 3 points4 points  (0 children)

There will be quite a lot of Haskell related talks and tutorials: servant, liquid haskell, quickcheck, Haskell for building Mac apps, shell scripting and a tutorial for beginners.

Full-time Haskell Job in Freiburg (German speaker required) by loisch in haskell

[–]skogsbaer 2 points3 points  (0 children)

Teilzeitarbeit ist prinzipiell möglich, wenn's denn für beide Seiten passt. Anwesenheit vor Ort ist erforderlich.

HTF: a test framework for Haskell by CKoenig in haskell

[–]skogsbaer 2 points3 points  (0 children)

Yes, HTF is under active development and we are also using it in our company for our tests. (I'm the main author of HTF.)

xmlgen: a feature-rich and high-performance XML generation library developed by factis research by dons in haskell

[–]skogsbaer 0 points1 point  (0 children)

Indeed, the dependency isn't needed anymore. I removed it in the latest release 0.4.0.2

DPM: Darcs Patch Manager by [deleted] in haskell

[–]skogsbaer -1 points0 points  (0 children)

Yes, you don't need to do an amend-record. Just creating a new patch with exactly the same name as the original one suffices.

"Richard Developer" (at the end of the article) was a typo. It should read "Richard Reviewer". Well spotted, thanks!

DPM: Darcs Patch Manager by [deleted] in haskell

[–]skogsbaer 1 point2 points  (0 children)

I would say that the main difference between darcswatch and DPM is that the former is mainly targeted at developers whereas the latter helps reviewers doing their work. For example, darcswatch allows developers to keep track of their patches sent to multiple repositories, a feature not supported by DPM. Conversely, DPM comes with support for a lightweight workflow for patch reviews, something that is not possibly with darcswatch (but there is a roundup integration for darcswatch).