News for hackers. Stuff that matters.
Re:Pixelmator Pro released by thijsvandien on Wednesday November 29, 2017 @12:48PM (#15809026)
Requiring High Sierra means I won't be able to give it a go within the next half a year or so. I only just migrated to Sierra... Professionals are generally more careful with upgrades, so I'm not sure if that requirement was worth it.

Apart from that, Pixelmator was an absolute steal when it was first released but I can't help the feeling it has stagnated since then. It has become buggier and requests for very basic enhancements are ignored. As an example, it still annoys the hell out of me that a zoomed in image that is not completely visible always sticks to the edge of the window it's in—good luck selecting anything at or near the edge.

At this point I'm more motivated to get to know Affinity Photo better rather than giving the Pixelmator team another chance.

Re:Pixelmator Pro released by tbassetto on Wednesday November 29, 2017 @01:11PM (#15809246)
It’s built using Metal 2 (https://developer.apple.com/metal/) which is only available on High Sierra. I guess they carefully weighed the pros and cons before making this decision!
Re:Pixelmator Pro released by thijsvandien on Wednesday November 29, 2017 @01:19PM (#15809323)
For comparison, Affinity Photo offers all of software, OpenGL and Metal rendering. I suppose at least supporting the previous version of Metal would not have been a massive burden. It's not like it's a completely different API.
Re:Pixelmator Pro released by mortenjorck on Wednesday November 29, 2017 @01:09PM (#15809226)
This stems from use of CoreML, a High Sierra-only API used for the content-based layer naming.

It would have been nice if that had been a feature-flag that only turns on when running on High Sierra, but I'm guessing they decided that level of modularity was too much dev/testing overhead.

Re:Pixelmator Pro released by TomVDB on Wednesday November 29, 2017 @01:29PM (#15809406)
> As an example, it still annoys the hell out of me that a zoomed in image that is not completely visible always sticks to the edge of the window it's in—good luck selecting anything at or near the edge.

I've been using Pixelmator quite a bit lately, and that one just drives me nuts.

Re:Pixelmator Pro released by Zelizz on Wednesday November 29, 2017 @02:49PM (#15810222)
I think I made a thread about that on their support forums maybe 5 years ago? They're never going to fix it.
Re:Pixelmator Pro released by teilo on Wednesday November 29, 2017 @02:00PM (#15809707)
I'll give the Affinity products a chance when they fix bone-headed missing features - like a way to change the ruler origin. This is a particularly egregious omission in Affinity Designer. They have been promising this non-optional feature for almost 2 years now.
Re:Pixelmator Pro released by lostgame on Wednesday November 29, 2017 @12:50PM (#15809043)
Was very, very disappointed to notice that it required High Sierra, especially given the current state of its security.

They lost a purchase from at least a serious dedicated fan, here, for that one.

Re:Pixelmator Pro released by SomeHacker44 on Wednesday November 29, 2017 @12:56PM (#15809096)
I never want to run High Sierra or iOS 11. Clearly, I will be required to at some point when I upgrade my iPhone/Mac hardware, but... <sigh>

Why does every Apple release feel like one step forwards, two (or two dozen) steps backwards?

Re:Pixelmator Pro released by dreamcompiler on Wednesday November 29, 2017 @01:42PM (#15809536)
I'm still on Mavericks and never plan to upgrade. Every new Mac OS now seems to be a major regression in basic functionality in the name of more eye candy, more Apple lockin, and more crap I have to turn off just to get work done. I'm done. I just bought a Dell XPS 13, installed Linux on it, and I'm not looking back.
Re:Pixelmator Pro released by AdamJacobMuller on Wednesday November 29, 2017 @02:30PM (#15810038)
Apple is pushing me there for sure.

The latest MacBook Pro is not so pro anymore. 16gb ram is embarrassing in 2017.

Re:Pixelmator Pro released by whitehat2k9 on Wednesday November 29, 2017 @09:10PM (#15812879)
Maybe it wouldn't be if people stopped coding everything in node.js.
Re:Pixelmator Pro released by rovr138 on Wednesday November 29, 2017 @10:52PM (#15813340)
Try running a couple of test VMs, an IDE with code completion on top of a decent sized code base and you’ll be swapping like crazy even with 16GBs.
Re:Pixelmator Pro released by AdamJacobMuller on Friday December 01, 2017 @01:27AM (#15822331)
While I agree with you that node.js is bad, that's not even my issue. I use Vagrant extensively and I might want to spin up 2 or 3 VMs with 2-3GB of ram to test $thing.

Now, I can do that (3*3 == 9 < 16) but, really, it makes the rest of my system just run terribly.

I would personally pay a $1000 premium over the current MacBook Pro for a version with 64GB of RAM.

Re:Pixelmator Pro released by abritinthebay on Wednesday November 29, 2017 @02:50PM (#15810231)
Because you are not their target market.

For everyone else - including many developers and power users - they are selling well (very well).

Re:Pixelmator Pro released by coldtea on Wednesday November 29, 2017 @01:23PM (#15809358)
Because the media says so?
Re:Pixelmator Pro released by laythea on Wednesday November 29, 2017 @01:33PM (#15809456)
Because not enough people stop buying/using their products.
Re:Pixelmator Pro released by bitshiffed on Wednesday November 29, 2017 @03:53PM (#15810740)
I love Pixelmator. I would definitely pay the $60 for pro, just for the single-window interface; but each new OSX version just gets worse. I've planted my feet in Yosemite, until either things turn around, or gets old enough to force me onto full-time Linux.