We are the chosen ones. :D

Did you notice anything that would be worthwhile switching from EndeavourOS to CachyOS? Not having any problems is nice, but is there an actual reason and do you even notice it in real world usage (I don’t count benchmarks)?

They had way too much ambition, which was beyond name and brand change. They had or planned changes in functionality and features as well. What I suggest is, a simple name and brand change. They just need to create a patch that is always patching after a new version of GIMP, without further ambition.

I argue that GIMP is for image creation too. It does even better job at this, depending on what type of work you are doing. I don’t like to create pixel (as in retro gaming) graphics in Krita. I am not talented at all, but I can judge the workflow I think. That was just an example off course. We all know Krita excells at creating painted like arts with a pen and brushes simulation.

If the llm now creates code based on that it should be under an open license as well. In this case, it is.

There are different Open Source licenses. And the result is only one license. In example there are stricter licenses and you are not allowed to re-license it under MIT License. Therefore your quoted argument is not valid.

Can you point to the point what it has been stolen and plagiarized?

Wow. The OP wrote a tool, because there was nothing that satisfied him. And he gave it away for free and even Open Sourced it. You have no rights to be angry. You have rights to criticize the project, but no one is forcing you to use.

I tried Krita. It’s not not as good as GIMP is. What I will say is, it is pretty good for what it is and offers stuff that GIMP does not have. In fact I wanted to switch multiple times because of the support for Vector layers and non destructive workflows. But I never liked editing or creating images with it. Their text tool is also terrible (or was, I don’t know the current state). Just not a good GIMP replacement for me.

I’m sure the mainstream doesn’t care or even know what problems a subset of people have. I am not saying it is not a problem for those who have, but don’t pretend as if the name is an issue in widespread adoption. In fact, changing the name would only lead to a little adoption, but split the user base and make it even more confusing. Lot of people wouldn’t want to use the old name or the new fork, because everywhere and every article talks about how bad the name was. Therefore many people would just distance themselves from the project, without really understanding the issue or even caring.

Let alone all the references in history, web and tutorials on YouTube which is only written for name “GIMP”. Changing the name of the main project would be a terrible idea. However I propose anyone who have a problem with it to simply fork it, and do a name and brand change. Without much other work, so it is not far behind to original project. This way people having a problem could just use that instead and everyone is happy.

Such a huge usability improvement! I always tried to mimic this kind of workflow with what was available before, but it never worked seemless and I always forgot how I did it last time (lol, but also sad). This release is such a big deal.

I find Photoshop not intuitive too, because its different from GIMP.

The long awaited shape tool is coming up next. So the next GIMP version is shaping up to be a great release. This reply is in no shape or form a word play. :>

Acknowledging the issues is a first good sign of trust. Executing is the other, so we’ll see how this will going. I personally lost trust and interest into Manjaro and switched away. From personal experience, there were technical issues (caused by Manjaro), and social issues (didn’t like the administration and project leader). But I hope they “recover” and be better, and survive.

I agree here. I also want to add, it depends on who maintains the Flatpak too. It’s not always the official developers.

I say as long as Ai exist, real programmers will always have a job and are not replaceable. YOLO Vibelords are replaceable, but only real programmers have the skill to go through the shit. That’s the most secure job ever if you ask me.

I feel sorry for anyone relying on Copilot.

I don’t understand the logic. Why would Proton make Linux dependent on Windows binaries? It does not make Linux dependent, but enables to use them. I don’t see any reason why Valve should demand devs to build Linux builds (plus Valve should not demand it, it should be a decision of the developers, Valve should not have that much power in my opinion).

if microsoft changed their apis wouldnt new games just not work on proton?

The same would happen with changes in Linux. And arguably it is worse on Linux. Windows binaries have a higher chance of working through WINE or Proton, than Linux binaries in the future. Plus developers only need one binary build, instead developing for Linux and Windows. Also if Microsoft changes their API, then only games affected using the new API would be affected. And changes and additions happen all the time and the Proton / WINE devs are working all the time too.

AutoHotkey

Yes, and I ask why he does not like and use it. What’s the issue with it? Would be good to know for myself. Plus, if we know whats the issue with the official software, we can make better recommendations.

Nobody can safe us from C++.