I normally avoid writing lenghty posts here but as a dev with lots of commits in darktable (dt)let me describe my standpoint on this topic.
YES: i have read through all that lengthy post of AP and i could appreciate some of his humour and his criticism of dt code.
YES: i absolutely adore his work on color maths in dt, his driving force towards what he calls “scene referred” and the contributed code that made dt the sophisticated piece of software it is today.
YES: lengthy parts in the mentioned post are imho just personal assaults - in no way acceptable. The reasons for that i can’t understand at all.
In a number of posts here in this thread the rationale behind AP’s criticism of dt code was mentioned, so let’s go into this.
The UI of dt is a design decision and so can always be debated. (BTW you can read in github how that is done)
We have too many options in preferences. Everyone here can come up with suggestions via a github issue or even a pr and i can assure you, it will be discussed. I have done such several times.
Dt is full of “bloat” making the code un-maintainable?
In the post there are lengthy statistics, but those data don’t prove a single point. Some parts of that code indeed look weird and it might be very good to refactor but proving bloat? Absolutely no.
Some details (removed code in ansel as being bloat)
- The MIDI interface. Have you used that? I got myself a loupedeck+ a year ago and concider that the best investment i ever did for raw photo work. Much more important than a new piece of glass. It speeds up the work and allows to focus on visual output while developing enormously. A no-go to be removed.
- The new selection filters. How much hate-speech was put on that. I just like to use it every day.
- The various lightroom modes. Absolutely a must is the culling mode.
- Support for slow machines (“performance over quality”, “resolution of preview images”). I don’t care personally (due to my system’s power) but i certainly want user experience to be good even on slower machines than mine.
Question here: You still concider above code as “bloat”?
It was said, because of the “bloat” dt is slow and eats up the CPU/GPU.
Have you tried recent dt master and checked performance vs ansel? You are strongly advised to do so I installed ansel from github code yesterday while investigating an issue on common code and the performance difference was to be noticed immediately and the perf gain was not pro ansel. And the better dt performance was not only for exporting but in darkroom.
Did you follow the vast number of commits removing endless lines of sse2 specific code? That’s what i would call removing bloat and reducing complexity for performance.
Last points for now. Would you want to miss the new screenshots? A performant slidesow? The new presets? Style previews? Bugfixed ISO mode? Some new algos? Lens correction based on manufacturer data? EDIT: The list is much longer, just have a look into 4.2/4.4 release notes.
Use the software you want!
If interested to do so make constructive criticism on dt using arguments on github! We love to get that sort of feedback!
Have fun with your photos and keep going!