@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 ?
@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?
@xkummerer @rml praxis
@rml how do you know it isn't the other way around?
@rml nah, theories compose quite badly
I should write a huge text about how #Haskell is a great language and is getting better all the time.
Just to dilute the stream of negativity constantly appearing on feeds.
Maybe *you* should too.
Gosh, I sometimes hate that the LSPs are a thing now. People really like to dunk on #Haskell and its "toolchain" for LSP deficiencies.
Come on, people, this stuff is barely mature by itself.
And you really can do without it.
@sanityinc I don't get the point in the post. If you don't like the tempo, you just stay on whatever the LTS suits you. If a library is too fancy for you, don't touch it. Hate YAMLy hpack? Sure, use cabal. Love it? Do the other way around.
@wiredfire @dansup @GuyDudeman @wedistribute E2E in a closed source system under USA compliance, yeah, sure. Totally not lame.
I have no illusions with Telegram here, it's a public comms platform to share cat pics. You don't use that if you need E2E.
Trading away comfort of multi-device account and non-bloated open source clients for a clown mask of "security" doesn't cut it for me.
@dpiponi From where he would fall out?
A> Out of favor
B> Out of window
C> Out of plane
D> Out of service
* 50:50
* Phone a friend
* Ask the audience
Toots as he pleases.