@shingworks This is because you were stating a commonly-spread misconception about the Linux/Krita/etc. workflow, regarding incompatibilities with working with publishers. If no one pointed out the misconception, you and many others would simply continue to repeat this.
As someone who has worked as a publisher and was commissioned to create a lot of content myself, this is completely false. There's no incompatibility issues, nor any investments (it's all free+open software).
@hornyboner Why would they need an IP address for a printer to begin with? They don't have any sort of automatic network printer discovery? Sounds archaic.
Over in the Linux camp, if you have a printer connected to the network, CUPS automatically adds that printer upon connecting to the network.
Basically, CUPS does a broadcast and each printer on the network will respond with their information, to which CUPS uses to automatically add and configure the printer on the system. Stupid simple.
@shingworks This is a myth that has been debunked multiple times in the past. Krita can open and export Photoshop PSDs. Although to be perfectly honest, the international standard is ORA (OpenRaster), which has no relation to Adobe's file formats.
PS: I have worked in publishing before, and we used Linux / Krita / GIMP / Scribus; and not Adobe software. Didn't matter what format you gave us, because we could open everything, even the more obscure formats.
@shingworks Driver incompatibility is a non-issue on Linux, due to Linux being a macrokernel. It has exceptional support for Wacom tablets (and privacy / security).
GNOME Control Center provides a dedicated Wacom Tablet section in the Devices section, for configuring your tablet/stylus..
Everything you can do with Photoshop can easily be done using Krita, so there shouldn't be much/any re-learning on that front. Most Unis have even switched to Krita instead of Photoshop nowadays.
@shingworks Why not try out Solus[1] and use Krita[2] instead? You'll get much better mileage from your system, even older systems.
@Jbastardov Because proprietary software companies rarely ever set up continuous integration to ensure the overall quality of their codebase, as does modern open source software. That costs time and money.
I'm from the Redox OS camp, and you can bet that we have a vast array of unit and integration tests littered everywhere (in addition to writing all our stuff in Rust for those memory safety guarantees), so things like this aren't going to happen on our platform.