l'empathie mécanique @dpwiz@qoto.org

@underlap @acowley ah, that's cabal the file format

What would you like instead of that? Use toml and skip the custom format entirely?

@underlap @acowley it uses cabal the library, but not the cabal the binary. The naming is unfortunate...

@underlap @acowley Anyway, how adding one more build tool would help?..

We've had `stack` already, with this specific mission of improving user experience. And improve it did. Now we have two concurrent build systems. Meanwhile, users continue to receive the `cabal install whatever` advice and hurt themselves with it.

@underlap @acowley Unless you happen to support Hackage and Stackage the result would be very niche, unusable in anything beyond perhaps online playgrounds. And then users would have to encounter "poor" experience of the real world anyway.

If only we had a library for Common Architecture for Building Applications and Libraries or something like that...

@underlap @acowley There were alternative build systems (like mafia)... I don't know even what is the problem they intended to solve.

Why do you want to replace Cabal?

@underlap @acowley Even GHC2021 is not enough to be convenient in all the important places. Using even restricted language would be no fun.

@zeux what's that? Nvidia fan service?

@sjb3d @aras @joeldevahl have you looked at dual contouring? It's more costly, with finding tangentials, but the result is as good as it gets.

@outie @mcc Please disable ad blocker and allow JavaScript on this page. We will add your biological and technological distinctiveness to our own. Your culture will adapt to service us. Resistance is Futile.

I wish `git` had something to hexdiff files out of the box, instead of that weak excuse of "binary file differ"

@acowley So, this is -Wcompat? (=

To sum up, we have:
- Stackage LTS, pinning GHC major and a set of cross-compatible packages.
- -Wcompat for advance warnings.
- -XGHC2021 for baseline language features
- GHC proposal system to announce, plan ahead, and coordinate features.

What do we miss other than formal blessing that such-and-such GHC/LTS heralds a new "epoch"?

ghc/8.10.7 and its associated lts-18 appear to be something just like that.
And soon 9.6.x will come, that'll cement in GHC2021, text-2, etc etc

@acowley So, those are our stackage LTS snapshots?

@acowley If anything, it would be python 2/3 and scala 2/3, regularly.

Maybe I just prefer gradual fixing instead of "patch tues-years".

@acowley How it is better than 3-ghc-majors policy?

@wilfredh what about about emacs.zip ?

Screw banks and their "security" policies

@RenewedRebecca @cwebber@octodon.social let them combine the best parts in a collaborative effort

@rml This looks like nominal vs structural "styles". Haskell clearly favors the former, but has a lot to work with the latter - Dynamic, Generics, all kinds of "Value" ASTs and coercing/parsing/building to bridge it.

I'm pessimistic, honestly, on the merits of generic structures throughout and usually want to parse them away and the boundary. Thus, it's Haskell for me (:

@rml hm... Perhaps I don't get what do you mean here. What's the difference between a composable and decomposable code?