![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
Mmmmmmmm… Lexicographical Endianness.
Mmmmmmmm… Lexicographical Endianness.
That’s fair, but it doesn’t answer any of the questions about what should be improved. “Industry standards” is a vacuous term when the standard is defined by a singular piece of software made by one company.
Sure, GIMP isn’t Photoshop, and those familiar with Photoshop will have to re-learn things to use it. But what exactly needs to be changed? The developers have no chance of improving the program if the feedback is this generic.
I feel like the issue is that people expect a “Photoshop killer” to be Photoshop verbatim. Instead of focusing on making a good tool, people just constantly compare it to the commercial pack leader.
Most of the complaints I hear about GIMP are just “x isn’t like Photoshop”. I would take the complaints more seriously if any of the people voicing them could actually articulate what should be improved.
People who still have an i686 CPU, apparently.
Look, we already got rid of “Master/Slave” in favor of things like “Parent/Child”, “Active/Standby”, or “Primary/Secondary”. We’re not making more changes because right-wingers are afraid of everything.
The Musk followers? Good.