Introduce Yourself

I'm David Feuer. I maintain containers, co-maintain unordered-containers and pqueue, and contribute to various other projects. Data structures are fun. I'm a good person to talk to about laziness subtleties, and about whether particular applications of unsafe IO are safe in context.

I'll kick this off. My name is Jaro. I have been interested in Haskell for about 8 years now. I like it because of it's connections to theory; there is always more to learn!

I'm currently working on gigaparsec which is a parser combinator library like parsec and megaparsec, but gigaparsec allows you to write your parser in a natural left-recursive way and it returns all possible parses instead of just the first parse that succeeds. My goal is to make a parser combinator library that allows you to use annotations to inform the parsing process instead of forcing you to restructure your parser.

Recently, I'm getting more and more convinced that correctness is the cornerstone of computation. To write a useful program you should first specify the idea itself and only later provide an efficient implementation. I got this idea from Conal Elliot who has talked about it on the Type Theory Forall podcast and recently at ZuriHac.

So, now I've also started reading the HoTT book to see what it really takes to express myself formally.

Looking forward to your introductions!

I'm "TomMD". To say I 'maintain' things might be an overstatement, but I've released a number of Haskell packages and minor fixes. Much of that was on my own but a significant portion were from my Galois days. I've had a few publications and am hoping to get to ICFP Seattle this year. Also years ago I made (cofounded) a company (Muse Dev) with Haskell as central part of the stack which was enjoyable.

Currently? Life is very busy so I'm just enjoying my Haskell time writing this and that rather than building much for release.

I'm Glyn Normington. I dipped into Haskell briefly in about 2011, but recently got a little deeper into it when I taught a second year functional programming module at Winchester University, UK. I'm a retired programmer with 39 years experience and try to pass on some general tips in the module. I came here after recently deleting my Reddit account. (I've been on the Fediverse for a while as fosstodon.org/@underlap.)

I'm Kleidukos, interested in production Haskell, with a focus on developer experience, web services, accessibility and building community spirit. Glad to join the party here!

I'm Edwin. I've been enamored by Haskell for several years, but never had the opportunity to work on it professionally, or for any medium-to-large sized projects.

I did write a statistics calculator for DnD 5e for my DM that used Haskell for the backend though, and that was fun. I attempted to use Haskell for the GUI, but found the experience lacking, since my DM had a requirement that it work on Windows and be a desktop app. Long story short, I spent hours trying to get gi-gtk to work on Windows after spending other hours trying various other solutions (to include threepenny-gui) before eventually giving up and writing the GUI in Python + Qt 6.

I now have a passion project named "War Womb", which aims to be a 2D app that lets you play Warcaster: Neo-Mechanika digitally. I have a prototype written as a web-app using Python + FastAPI in the backend and Typescript + React on the frontened. I've been recently tinkering with SDL to see if I can treat the app more like a game, since there are a lot of interactive components, and thus hopefully use Haskell for this project instead, since I have way more fun programming in Haskell than anything else I've use.

Do code-blocks work better than on reddit for mobile?

Fenced code block:

module Main where

main :: IO ()
main = do
    putStrLn "Hello, kbin!"

Indented 4 spaces:

module Main where

main :: IO ()
main = do
    putStrLn "Hello, kbin!"

update: Oh wow, looks like only inline code fragements work? Something like main = putStrLn "Hello, kbin!"
update 2: No syntax highlighting at all! That's probably a show-stopper.