I wish I could get over the learning curve with GIMP but tbh my current workflow involves a windows 10 virtual machine for Photoshop. It works for my needs without GPU pass through.
I don’t think a week is that long to wait for an open source project like this. I suspect as soon as they released 115 they got a deluge of bug reports that are probably keeping them occupied.
Granted, I’m not personally affected because <smug>I use Arch btw</smug>. But on a serious note, it makes sense to me that “bleeding edge” distros where users expect the latest versions quickly would package Thunderbird for their repos, whereas those on more stability-focused distros would wait the couple of weeks for the Flatpak.
I need to look into it again. I wanted to stabilize my footage of a Samsung gear 360 with the embedded gyro data but I didn’t got it to work. Maybe I have to try it again.
Of all the design decisions in GIMP that seem to make it so weird or different to someone coming from Photoshop, Adobe has put in 2X the amount of design choices into their software simply to try to thwart piracy.
The amount of stupid libraries and processes it loads and “requires” to run is just crazy.
A lot of it became apparent when Apple dropped 64-bit support a few years back.
Developers had a decade to update everything to 64-bit. All the fancy (and expensive) Adobe apps were 64-bit, but all their licensing dependencies and anti-piracy libraries were strangely still 32-bit.
People with legit copies couldn’t run anything after upgrading macOS. Only those with cracked/pirated versions (that didn’t load the 32-bit libraries) could actually use the software.
I have no doubt that the mess of libraries and copy protection that Adobe “requires” would prevent their software from working under WINE.
There is a Photoshop CC installer for Linux hosted on Github. I’ve tried it - it works. It’s just not a great experience. Saving files is a pain, because the export option does not exist. You need to use Save As, and that only works with a hacky workaround.
The UI doesn’t update until you do something that forces it to re-draw (like zooming or panning), which is a real pain when transforming or moving layers - for example. Plus, the UI doesn’t scale. You need to use Photoshop in complete fullscreen otherwise parts of the UI will be missing.
AI filters do not exist, for obvious reasons. However, most other filters work fine.
And most obviously, performance has an extreme degradation. It’s really slow.
But yeah, would probably get a “Bronze” rating on WineHQ, which is better than not working at all - I suppose. It’s progress?
Oh wow, that doesn’t sound like a nice experience at all. I wonder if older versions of PS work better with Wine since it could be an option if you don’t need the latest features.
And there’s the issue of tablet pressure! As an amateur artist I was ok with most of the peculiarities of Ps on Wine (even the weird full-screen deal that you mentioned), but even after extensive tinkering it would only register my Wacom pen strokes as single spots or full-pressure lines. Apparently this bug is pretty old, and the underlying problem is way more difficult to solve than it first seems (esp to a linux noob like me). I’ve heard photoshop cs2 can avoid this bug (and it worked fine for me) but that version of Ps looks very different than what I’m used to, having been a longtime cs6 and cc user.
I ended up mainly using SAI on that system–which ran very well on Wine–but it has fewer bells and whistles and there are certain tools like liquify that don’t offer the same degree of control in Krita or GIMP (as far as I could tell). If my laptop hadn’t been struggling so much, I think I probably would’ve shifted more towards Krita but somehow it ran much worse on the linux system than the previous windows system, regardless of which version I tried. It’s a difficult problem to troubleshoot if you don’t know tech stuff very well - . -
O use ext4 at home and in servers that are not SLES HANA DB ones.
On SLES HANA servers I use ext4 for everything but the database partitions, for which SAP and SUSE support and recommend XFS.
In a few occasions people left the non-db partitions as the default on SUSE install, btrfs, with default settings. That turned out to cause unnecessary disk and processor usage.
I would be ashamed of justifying btrfs on a server for the possibility of undoing “broken things”. Maybe in a distro hopping, system tinkering, unstable release home computer, but not in a server. You don’t play around in a server to “break things” that often. Linux (differently from Windows) servers don’t break themselves at the software level. For hardware breakages, there’s RAID, backups, and HA reduntant systems, because if it’s a hardware issue btrfs isn’t going to save you - even if you get back that corrupted file, you won’t keep running in that hardware, nor trust that “this” was the only and last file it corrupted.
EDIT: somewhat offtopic: I never use LVM. Call me paranoid and old fashioned, but I really prefer knowing where my data is, whole.
Most comments suggesting btrfs were justifying it for the possibility of rolling back to a previous state of files when something breaks (not a btrfs breakage, but mishaps on the system requiring an “undo”).
Ah, I see. While that use may be a good plan for home server, doing that for production server seems like a bandaid solution to having a test server and controlling deployed changes very carefully.
Not a multi function device, but a plain printer, but I have a Borther HL-2365DW connected via 2.4 GHz WiFi and that is detected as HL-L2360D. The printer works absolutely fine. It still has the original toner cartridge and it is used 3-5 times a year without any issues.
Before that I had a HL-2030 that died after ~14 years.
To be fair, I have a 4P that I still use. But yah, my Brothers have always lasted a long time and toner/ink isn’t crazy expensive. And they don’t pull DRM shit like HP and get their peepees slapped time after time.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.