[Haskell-cafe] [ANNOUNCE] GHC 8.2.2 release candidate 2
Sven Panne
svenpanne at gmail.com
Sun Nov 5 20:52:11 UTC 2017
2017-11-05 15:37 GMT+01:00 <jpaugh at gmx.com>:
> A better approach might be to develop a "machine-readable" output format
> which then is kept stable, and can be enabled with a flag. Git has a
> similar solution.
>
Without doubt, this is definitely the better approach, but this is hardly
what can be achieved for 8.2.2. Adding some flag to get the old behavior
back when wanted *is* achievable.
> It would be a shame to avoid changes which make the user experience better
> simply because other projects cannot sync their development cycle,
>
Don't get me wrong: I'm all for improving user experience, but making ad
hoc changes without enough thought or even a chance to get the old behavior
back is probably not the right way to proceed. All SW lives in some kind of
ecosystem, so it should behave well in that. And for Emacs users, the user
experience has been made much worse.
> especially if those projects are not universally used or required.
>
This is highly a matter of personal taste: No project is "universally
used", so this is tautological statement. The question is: Is a minor
cosmetic change really worth breaking things in one of the major IDEs?
Cheers,
S.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20171105/64d7625f/attachment.html>
More information about the ghc-devs
mailing list