Adj_and_Styles

> Gimp for a looooong time was a multi-window user interface, completely antithetical to almost any other application released in the last 20 years or so.

Same as Mac software in the late 90s. GIMP is/allows MDI, tabs or whatever it is called. A decade old at least, Wikipedia is not clear if the change was "new feature" or "new default but avaliable before". Maybe Mac native software went that way too, no idea what is the trend there now. Most things reinvent everything including window management, poorly, inside a browser, anyway.

Maybe save the log automatically? And then check and report unsolved errors, at end of the fuction or better separate one so log can be reinspected any time.

I have encountered "GnuTLS: The TLS connection was non-properly terminated. Unable to establish SSL connection." multiple times, and retry options seem to be useless when that happens. Some searches suggest it could be related to tls handshake fragmentation, but nonetheless wget could retry if related options are used. Manual retry seems to download the missing URLs, otherwise mirroring jobs are randomly incomplete.

The atool script is just a wrapper around many compression tools. Try atool -x which creates the temp folder under final destination.

https://www.nongnu.org/atool/

Edit: just noticed it was mentioned in other reply, but as aunpack, a symlink to atool. I got used to the -x|-l|-a|... style and rarely remember the alternative names.

Japanese already tested it, with googly eyes. It seems to work. Modern cars are expensive, some extra plastic and servos is not going to break the bank.

https://dl.acm.org/doi/10.1145/3543174.3546841

https://www.dailymail.co.uk/sciencetech/article-11250965/Jap...

https://videos.dailymail.co.uk/video/mol/2022/09/26/56244997...

British used a LED matrix. More "output" options (frowns and smiles, text), similar results.

https://www.nottingham.ac.uk/news/first-ever-uk-ghost-driver...

https://www.theengineer.co.uk/content/news/pedestrian-study-...

In bash you can probably use "pushd" instead of "cd" (it builds a stack and can swap top two entries, as well as rotate the stack) and abuse "dirs" (to create the variables with something like "c3=$( dirs +3 2>/dev/null )").

So when people do not understand the meaning of a word and not care about it, because they do not speak that language, the metric is useless instead of a test of "everything else but the name".

My, small but non zero, experience says the reason these speakers of other language declined to use it was because it lacked features and sometimes because "piracy is also free". They pointed the brush system was basic, PS already had effects they used a lot. No adjustment layers, styles or layer groups to be more efficient. Slow processing because it operated in full data always, while PS solved preview first and the rest in background. And many other things. The Mac ones found no issues with the windowing system (no MDI mode then, with everything wrapped by big window), because it matched more what they were used to, but Windows users found it bad because their OS is not designed for it. None cared about what Gimp or Wilber words are, it was "a poor PS clone with a croissant dog mascot".

Does GIMP have a bigger market share in non-English speaking places? Because if it does, then maybe the name is to be blamed. But if usage is similar everywhere, the name does not seem to matter much, or at all, for the (lack of) success.

Non English speakers should have no such issue with the name and adoption in that population should be higher than English speakers. But is it? If similar usage, the problem is somewhere else.

From experience, the issues raised where total lack of CMYK, limited to 8 bit per channel,lack of even basic non destructive editing, crude paint engine, no healing tool, etc. Some have been solved partially or totally over the years, but too late for some users.

Those could had been implemented loooooooong ago. In a hacky way. The dictate was to be pure and wait for GEGL. So still nothing of that. We got layer trees at least.

They could have been implemented by overloading the layer blending code, and recoded with GEGL once ready. But pure won over "we can do that too now, please do not look behind the curtain". It's really simple: adjustment is just a layer that only uses mask data and operates on the bottom layer pixels with already coded functions (levels, contrast, etc). Styles would be similar, applying plugins/scripts. If when proposed the reply is "we will not accept that kind of crude system", nobody wastes time coding a patch.

That was not the only time GIMP project went the pure road. There was also drama with themes and paintbrush system. On the end, some of the old ideas managed to get there, like grey icon theme (now hated by some, the irony) or having a working paint system (I have not tested with a tablet, so no idea if any good). Even non coders were trying to help, for example contributing brushes and testing the system [0], yet they ran out of steam after some time of hitting walls. The few people involved now seem to be the ones that have been taking over after all the previous got seriously burnt (except Kolås). [0] https://www.ramonmiranda.com/gimp-paint-studio-su-pasado-pre... (autotranslation work OKish)