mirek kratochvil
@exa@mastodon.online  ·  activity timestamp last month

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).

https://github.com/exaexa/werge (is #haskell )

#versioncontrol #programming
mirek kratochvil
@exa@mastodon.online  ·  activity timestamp last month

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).

https://github.com/exaexa/werge (is #haskell )

#versioncontrol #programming
Anthony Cowley
@acowley@mastodon.social  ·  activity timestamp last month

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.

https://github.com/ghc-proposals/ghc-proposals/issues/706
Anthony Cowley
@acowley@mastodon.social  ·  activity timestamp last month

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.

https://github.com/ghc-proposals/ghc-proposals/issues/706
Yuras
@Yuras@mastodon.social  ·  activity timestamp 2 months ago

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.