When Linus says no, he rejects features and pull requests. That's fine. That's responsibly shepherding your implementation. That's not what Elm does. They lock

When Linus says no, he rejects features and pull requests. That's fine. That's responsibly shepherding your implementation. That's not what Elm does. They lock down the compiler so only Elm devs can modify internals, which would be equivalent to Linus trying to prevent people from modifying the kernel. They really don't like people forking their repo, which would be equivalent to Linus getting mad at people making derivative kernels (because it would "split the community.") It's not just a matter of saying "no," it's trying to control what devs do to an UNREASONABLE degree.