…more “terrible” than:
…?
In the absence of GHC getting a great deal faster, users who can’t afford workstations (let alone “battlestations”!) will more and more turn to their only other convenient option and (try to) run more jobs simultaneously. So if even that is failing to work “regularly with GHC on large projects”…then this must surely now be the only hope left for GHC, at least in its current form:
@hasufell, if what you are saying is correct - that not even -j2 can be relied upon to work properly in this era of multi-core/thread machines - it would most definitely help to explain why Haskell is still a “minority-user” language: because everyone else got tired of waiting…and waiting…and waiting…and waiting…and waiting…and went elsewhere, to find a language they could actually use (in much the same way GHC devs eventually got tired of waiting for darcs and decided to switch a more popular (but stupid) content manager which was faster to use).
So @hasufell…is GHC really that horrendous to use, even for someone as experienced as yourself?