4 ms·
It seems inconsistent to claim both a) this proposal/implementation has bad ergonomics and doesn't solve real problems, and b) the library ecosystem will becom
by nimih 6y ago
It seems inconsistent to claim both
a) this proposal/implementation has bad ergonomics and doesn't solve real problems, and
b) the library ecosystem will become irreparably fragmented as library authors rush to incorporate it or provide linear forks.
Surely if enough people are expending the effort to bring -XLinearTypes to a non-trivial portion of the extant Haskell universe, it is by definition both useful and at least somewhat ergonomic?
- whateveracct 6y agoIt is inconsistent. -XLinearTypes detractors have been making this paradoxical argument for months now. If it's useful, people will use it to build libraries. If it's not, it's all fine. The FUD from Haskellers depresses me. My consolation is I'll get to build useful shit with -XLinearTypes on GHC mainline now - things detractors told me weren't possible because they were too busy complaining about its imperfection.
- kreetx 6y agoThe detractors are just a minority, right? Where do they criticize(?), reddit and the mailinglists have seemed pretty clean.
- whateveracct 6y agoThere have been multiple reddit posts full of long essay comments against the extension. Including a text post itself about it. They are clearly a minority though. But very vocal.
- dllthomas 6y agoIt may be inaccurate but it's not inconsistent. Things can sound like a good idea, be embraced enthusiastically by people who haven't had a chance to work with them, and only later reveal serious ergonomic issues once people have a chance to use them in anger.