Close the GHCJS support window?

[philderbeast]

Related to #11608.

We have two very similar modules.

• Cabal/src/Distribution/Simple/GHC.hs
• Cabal/src/Distribution/Simple/GHCJS.hs

If the GHCJS module is unmaintained can we remove it?

@philderbeast Do you think it's worth it to update this codepath? The GHCJS codepath is untested and unmaintained, I think the last GHCJS release was corresponding to 8.10 and the modern way is to use the javascript backend. I couldn't be confident that anyway I did change it was correct.

Originally posted by @mpickering in #11450 (comment)

ghcjs is going away I think, so may be this should be closed?..

Originally posted by @ulysses4ever in #5844

The default branch, the ghc-8.10 branch, of the GHCJS fork was last updated Sep 25, 2022.

Originally posted by @philderbeast in #11530 (comment)

[Bodigrim]

If you don't test GHCJS (which is the case), you can be rest assured that it's broken already and there is no point in deluding ourselves that it's not. Old Cabals are not going anywhere, any users of GHCJS can keep using them. Burn it.

[mpickering]

I completely agree with @Bodigrim, if a large code path isn't tested then it is almost certainly broken already.

[ulysses4ever]

I agree as well. Should we treat this ticket as proposing a new candidate for deprecating? NB: we have a 4-release deprecation process https://github.com/haskell/cabal/wiki/Deprecation-Process