
The talks of the 2025 Haskell Implementor's Workshop, also co-located with @zurihac are available on YouTube: https://www.youtube.com/playlist?list=PLQpeDZt0_xQfpBPdVV3hUZ3_pDxmYhsbr
The talks of the 2025 Haskell Implementor's Workshop, also co-located with @zurihac are available on YouTube: https://www.youtube.com/playlist?list=PLQpeDZt0_xQfpBPdVV3hUZ3_pDxmYhsbr
The talks of the 2025 Haskell Ecosystem Workshop, co-located with @zurihac, are now available on YouTube: https://www.youtube.com/playlist?list=PLQpeDZt0_xQe319u9EdkpxjibYFtGsugc
The talks of the 2025 Haskell Implementor's Workshop, also co-located with @zurihac are available on YouTube: https://www.youtube.com/playlist?list=PLQpeDZt0_xQfpBPdVV3hUZ3_pDxmYhsbr
The talks of the 2025 Haskell Ecosystem Workshop, co-located with @zurihac, are now available on YouTube: https://www.youtube.com/playlist?list=PLQpeDZt0_xQe319u9EdkpxjibYFtGsugc
The talks of the 2025 Haskell Ecosystem Workshop, co-located with @zurihac, are now available on YouTube: https://www.youtube.com/playlist?list=PLQpeDZt0_xQe319u9EdkpxjibYFtGsugc
So I made a tool for managing little changes in code&text and it seems to run well enough now, so sharing.
The diff is like from git diff --word-diff
, but you can automerge same-line edits, retain spacing&indentation from a selected version, and send the small edits around as patches. Also works great for #LaTeX and #markdown (merging these with plain git is pure pain).
So I made a tool for managing little changes in code&text and it seems to run well enough now, so sharing.
The diff is like from git diff --word-diff
, but you can automerge same-line edits, retain spacing&indentation from a selected version, and send the small edits around as patches. Also works great for #LaTeX and #markdown (merging these with plain git is pure pain).
Interesting comments on the GHC #Haskell proposal process. I don't think language proposals are like academic papers as the sense of authorship is very different. A paper is not going to be just the way I’d write it, and that’s totally fine! The author chose to emphasize different things. But a language change ends up being owned (maintained) by a larger group.
Interesting comments on the GHC #Haskell proposal process. I don't think language proposals are like academic papers as the sense of authorship is very different. A paper is not going to be just the way I’d write it, and that’s totally fine! The author chose to emphasize different things. But a language change ends up being owned (maintained) by a larger group.
"C is a simple language. This is fact I agree with and appreciate. It is the reason for C's endurance. If someone posts a patch or submits a PR to a codebase written in C, it is easier to review than any other mainstream language. There is no spooky at a distance."
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.
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
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
A space for Bonfire maintainers and contributors to communicate