(Not a dozen components, though; just four. A main/watchdog service, a web service, a volume watchdog and directory scanner service, and a cluster of sync-file jobs).
Related: it was a total pita to handle real-time debugging until I made my own `tail -f` that sorted by timestamp and automatically updated as new processes added new log files).
- Maybe you are constantly trying it on the same distro that constantly has problems with its build for some reason or other. Consistent bad experience for the smaller number of users who conclude incorrectly that digikam is broken. For example suppose it uses out of date libraries that the software depends on.
- Maybe your configuration is unusual in some fashion and because of this consistently hits the same bug. If nobody reports it then it never gets fixed if it doesn't also effect a developers machine.
Neither of these is an indication that the projects low level architectural direction is problematic.
What we actually have is a tiny number of users who use Linux as a desktop that have pretty much identical use case with a small number of images succeed. All other workflows flop.
> Neither of these is an indication that the projects low level architectural direction is problematic.
In 2020 having a project where processing a corrupted file under any conditions causes the app to crash means the projects has a bad architecture.
lol, I've actually use Digikam on windows and mac because of how well it works for me
Pixar is an interesting case because as pioneers in their field they made a lot of their own tools and run them on Linux. Presumably unlike single user incentivized to select whatever they are used to they are instead liable to pick the best platform.
Pixar uses Linux
https://www.gamingonlinux.com/articles/pixar-film-production...
Aftershot Pro, Lightworks, Maya, Bloom all seem to be pretty good.
They have in common that they charge money and thus have a budget. Pixars choice seems to suggest linux us a perfectly viable platform and these able tools seem to suggest we can have good tools if we are willing to invest our money in such. This isn't to say that such tools must be commercial. They could well be foss if we change the way we choose to support FOSS. Instead of heaping praise upon them we need to open our wallets and regularly.
So the same for all other complicated tasks.
It is not that handling run time errors has demonstrated to be a trivial tasks for a main app.
It was specifically designed to handles hundreds of thousands of images and is in the final stages of release.
We have a little bit more information and screenshots on the website: https://www.pixolage.com and would be grateful for any community feedback (or beta testers!).
Disclaimer: I work at Pixolage
In terms of development, we prefer developing on lesser hardware so that we can be sure that Pixolage will run super smooth for most setups (although long compile waits can be frustrating).
For scalability, nothing beats multi-process. (Due to the way the OS manages communications between GPU driver<->process using the GPU).
Completely agree - Picasa is/was a great application!
But huge albums are a problem for many programs, unfortunateley.
It is just sad to see that the imaging/image processing/image organizing world is still stuck in 1990s paradigm rather than embrace that the computers have gobs of memory, a single application can be composed of dozen of individual components talking to each other over 127.0.0.1 and background jobs is a thing.