
GHC will start maintaining an LTS release – https://blog.haskell.org/ghc-lts-releases/ by Andreas Klebinger
GHC will start maintaining an LTS release – https://blog.haskell.org/ghc-lts-releases/ by Andreas Klebinger
I installed #tidalhttps://tidalcycles.org/ , after watching @ahihi livestream on #RadioFreeFedi with my jaw open - I was like why am i seeing #haskell on screen and music is coming out, how is this happening
Correctness Doesn’t Matter
It's an intentionally catchy title, but the point is still there. I think it's an important lesson many #haskell and FP enthusiasts failed to learn.
https://www.galois.com/articles/what-works-and-doesnt-selling-formal-methods
We have a relatively big code base in #haskell and the rate of bugs per release is quite low. I consider it as my failure as a team lead.
At some point we hadn't reverted releases for more then a year! Apparently managements though we don't have the technical ability to revert releases at all :)
For me it means that we were focusing on correctness too much neglecting issues that are more important for the company.
Yes I'm spoiled, but it's not #rust 's fault, it's #haskell .
It's just that when came the moment to make a choice between learning Go or Rust, the choice was quite easy.
MicroHs, a tiny Haskell Compiler https://lobste.rs/s/ak9mmk #video #compilers #haskell
https://www.youtube.com/watch?v=SJwvPEq4Mok
To those who could not attend #ZuriHac 2025, we salute you!
The videos of this year's talks are now available https://discourse.haskell.org/t/zurihac-2025-videos-online/12430
Better infrastructure, fewer surprises. We’re raising $6K for a dedicated ARM server to support #Haskell’s infrastructure - CI, backups, and more. Let’s build infra you can reliably pattern match on. Every contribution helps!
Donate: https://donorbox.org/infrastructure-independence
Read more: https://discourse.haskell.org/t/infrastructure-independence/12419
This is a great, fair look at #haskell and #rust. I often wonder if Haskell/GHC seeming to slow down was due to conservative members of the community, or if Rust's familiar Algol-like aspects led to much faster ecosystem growth. Some of the things called out here like enum name spacing, visibility control, error handling, and testing all seems like addressable issues were it not for the allure of the bike shed. https://academy.fpblock.com/blog/rust-haskell-reflections/
I want to be your next #FediHire ! I've been a programmer since 1985 (as a child), I've been an IT professional since 1995 (pulling wires and swapping cards and configuring MS Windows). I graduated from University of Arkansas Fayetteville with a BS in CS in December of 2003. A full resume is available.
I currently require a 100% remote position. I cannot relocate from Cove, #Arkansas. I would prefer W-2 employment with a base salary of at least 130k USD/yr, plus some sort of retirement offering (401k or similar) and healthcare benefits (HDCP + HSA or similar).
I prefer something where I can be a high-performing individual contributor: reading, writing and improving source text the majority of my day, with some time spent knowledge-sharing with other developers -- learning and teaching. I'd like to work with #Haskell, #Purescript, or #Idris as the primary source language. I've previously delivered value in Haskell, #Javascript, #SQL, #Python, #Scala, #Java, #C, and #C++ among others. I can be productive in almost any language (no PHP, please; I promised myself never again).
tori will be rewritten in another programming language. But which one? The contenders are OCaml, Haskell and Rust and the decision will be made by implementing a simplistic subset of its functionality in an experimental project called iganaq.
For more details, the reasons behind the rewrite and the candidate languages, see the announcement here:
https://tori.jutty.dev/updates/iganaq
Or go straight to the code, where the OCaml implementation is almost done already:
A space for Bonfire maintainers and contributors to communicate