Which is both a blessing and a curse - on the one hand, consistency, on the other hand, not welcoming to people who want to try something different.
Which is both a blessing and a curse - on the one hand, consistency, on the other hand, not welcoming to people who want to try something different.
If you knew a way to develop software like that where everyone could get their way all the time, please let me know, we could turn that into a product and get really rich selling it to every software company.
In Japanese, there is a term for this, and it's actually borrowed from the English "my pace" (マイペース). If somebody has this attitude, you can call them a my-pace. From what I've seen, that term is always an insult: nobody ever calls someone else a my-pace as a compliment.
Studios need features implemented immediately. That usually generates functional but unmaintainable solutions. Note that filmgimp/cinepaint was abandoned by studios as well as gimp developers.
What studios should have done: fund main gimp developers and hire other developers to help accelerate the development of GEGL or other multi bpp lib. What gimp developers should have done: try to merge enough of the studios changes to keep them interested.
I agree with your sentiment that some forking is preventable, but other times it isn't. Changing the fundamental design of the program tends to be one of those things that can't really be merged without causing a lot of other problems.