Why? Because of the UX. It completely breaks the creative workflow if you have to save two [or several] versions of an image and switch to another app to compose them together to see an effect applied locally. And then go back and repeat, if the strength is not to your liking.
Besides, Gimp doesn't support floating point image editing, so there is a also data loss involved if you use this app for compositing your RAW samples.
Krita & Natron seem the only alternatives on Linux unless I miss something.
On OSX, you could use Krita, DaVinci Resolve, Fusion, or Natron. Or pay for Photoshop.
In any case, switching apps sucks. :]
DT's authors understood this and added support for masks and module instancing. Plus a ton of blend modes.
That's what sets DT apart from the competition when it comes to 'how' you work.
As for the 'what': there is very little that the toolset of DT leaves to be desired. Even for professionals. :)
Why? Because of the UX. It completely breaks the creative workflow if you have to save two [or several] versions of an image and switch to another app to compose them together to see an effect applied locally. And then go back and repeat, if the strength is not to your liking.
Besides, Gimp doesn't support floating point image editing, so there is a also data loss involved if you use this app for compositing your RAW samples. Krita & Natron seem the only alternatives on Linux unless I miss something. On OSX, you could use Krita, DaVinci Resolve, Fusion, or Natron. Or pay for Photoshop. In any case, switching apps sucks. :]
DT's authors understood this and added support for masks and module instancing. Plus a ton of blend modes. That's what sets DT apart from the competition when it comes to 'how' you work. As for the 'what': there is very little that the toolset of DT leaves to be desired. Even for professionals. :)