Krita is a great tool and works with a lot of the graphics tablets on the market (not sure about the ones with a display but maybe?), and I was using it on Linux many years ago.
Yes. It's an industry standard in any digital art related industry. I know nothing about Krita and don't care to. It's not up to me. We need industry standards. Industry standards are a good thing.
There is a GitHub repo with a one-click (curl pipe to bash) installer for Photoshop using wine. Works great. Not going to link it because of questionable legality haha but it's easy to find
The current state of Wine Photoshop for the past 5 years is that it's unusable alongside other modern graphics software on modern hardware. The only high dpi version that you can expect to get working is CC2018 and it has a lot of bugs when running on Wine. CS6 runs perfectly and it's an excellent version of Photoshop, but it doesn't support high dpi so you'll have to lower your display resolution until you can read the menu text.
This won't help anyone who requires Wine as part of their workflow, I luckily don't, but I understand that Wine should be on target to handle Wayland by the next release early 2024.
This will give it proper HiDPI support and Vulkan rendering to help speed things up.
Does that mean CS6 on Wine will then work as if it was a hiDPI application? That would be amazing.
I should also mention CS6 runs fast as hell on Wine. It was so good that when I tried using Linux as my daily driver (before I gave up) I would change my display resolution to use it instead of CC2018.
It would be fair to say it's "quite simple" to port macOS apps to Linux if macOS apps were written against the Unix/POSIX API, but they are generally written using Apple's macOS-specific proprietary frameworks, meaning a Linux port of a GUI application would really be a re-write.
Adobe products look the same across Windows and macOS. I don't think they are using so much native stuff. They even ported their software to ARM, I think they could manage a Linux transition
Which is close to trivial if you're mainly using macOS APIs.
Of course Adobe probably has a lot of platform-agnostic stuff but which wasn't that straightforward to port but I'm pretty sure the UI and system stuff is still mainly using Cocoa.
I'm not even sure the macOS version would be necessarily that easier to port than the Windows one (then again there is probably not that much .net code in their tools)
"Quite simple" is an enormous overstatement here. The API surface of macOS is a vast superset of POSIX, including lots of libraries (AppKit, e.g.) that are not open-source.
