That's nice to have. For both GIMP and the industry's sake, priorities should be:
- good UX
- feature-wise competitiveness
- in any (sensible) format
GIMP is an alternative to Photoshop. It isn't a psd reader.
Being the format jack of all trades yet master of none isn't too great of an idea. It'll just exacerbate GIMP's main current problem: an ancient UI Photoshop enthusiasts dread. A lot might consider switching if the bad GIMP UX was better than the also-bad Photoshop UX.
If I had to say what my main design gripe with gimp is, that'd be modularity. Seperate the ui (skins) from the tools, effects and rendering (formats). The UI is especially egregious in its hard-codedness while effects are pretty well-supported.
A few more apis would go a long way. Hell, even the closed Photoshop has open(ish) apis, since even Adobe know the value of an ecosystem and not just their internal r&d department!
When you're driving a truck for months on end on cruise control, you have less work to do: look in front and steer. Time can get a bit relative.
6 minutes pass when you feel like it was only 2. Not a cardinal mistake.
Or the other guy decides to speed up.
And especially if you drive a route where you have to wait for hours on customs. The waits get really long so of course 15 minutes feel like 5 sometimes.