Some software like Firefox can understandably not work with multiple instances because they would interfere with each other writing to the profile folder (except if they run on two separate profiles).
But Baobab (disk usage analyzer) has no such constraint, so there is no reason why it shouldn't be able to run in multiple instances.
The funny thing is: older versions of it
actually supported multiple instances! Yes, they deliberately made it worse.
Quote:
|
Allowing only one instance is actually harder to implement, because the program needs to find and communicate with the instance already running
|
(
source)
Related bug tickets:
Who thought it was a smart idea to limit it to a single instance? It has no benefit I can think of. Or has it?
I know, there are workarounds, see
Ask Ubuntu, but I want to understand how it is a benefit to limit it to a single instance. If there actually were benefits, it should still have been made possible to override the single-instance limit using something like:
Some software already does this. For example celluloid (front-end for mpv media player) has a --new-window parameter for this purpose.
What is the benefit of limiting Baobab (Disk Usage Analyzer) to a single instance?
