# The evolution of: Decoupling base and GHC

**URL:** <https://discourse.haskell.org/t/the-evolution-of-decoupling-base-and-ghc/4085>\
**Category:** Uncategorized\
**Created:** [February 13, 2022, 11:23am UTC](https://discourse.haskell.org/t/the-evolution-of-decoupling-base-and-ghc/4085 "2022-02-13T11:23:54Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![sclv](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/sclv/32/71_2.png) [@sclv](https://discourse.haskell.org/u/sclv)\
**Post date:** [February 14, 2022, 12:15am UTC](https://discourse.haskell.org/t/the-evolution-of-decoupling-base-and-ghc/4085/13 "2022-02-14T00:15:51Z")

</div>

Let me suggest what the I think the decoupling issue is about (and gently remind abab and atravers that there was a long argument on haskell’s popularity at [The evolution of GHC](http://discourse.haskell.org/t/the-evolution-of-ghc/4008) and encourage them to keep any further comments there)

1. Updates to base can cause people to need to update other code.
2. People may want to update ghc to get bugfixes, new features, etc.
3. In so doing, they may not want to update base, so as to avoid needing to update other code, including a potential nest of transitive dependencies.
4. If base was decoupled so older versions could be installed on newer GHCs, this would alleviate this situation somewhat.

That’s it.

---

_[View the full topic](https://discourse.haskell.org/t/the-evolution-of-decoupling-base-and-ghc/4085)._