> "... Apple re-organized its software engineering department so there's no longer a dedicated Mac operating system team. There is now just one team, and most of the engineers are iOS first, giving the people working on the iPhone and iPad more power."
The new PDF editing solution is to fumble around with our fat fingers on a clunky oversized iPhone named "iPad Pro" , hooray.
By the way, when was the last time you heard something positive about the Mac, Mac OS, or the Apple effort with the platform?
* fully interoperable with PDF
* HiDPI that always works
* a clean and consistent configuration system for the OS and third party apps (defaults system), making it easy to (a) configure anything and (b) reset anything back to factory
* superb touchpad support
I guess you can now knock off the first one from this list and there seems to be movements on the Windows side to fix HiDPI and touchpad support (always 2x / precision touch). I'll check back in a year to see whether this has worked and whether Windows laptops have reached an acceptable state in these matters. Macs are loosing their distinct advantages one by one currently, mostly by total mismanagement of an almost early-90ies-Apple magnitude.
Also, figures often render as black boxes on other machines (it embeds figures with alpha channels where it shouldn't), and so on.
Still running 10.11 on my laptop, but I noticed that the pdfs are super blurry on cinema displays. If you use the mouse to drag the image, it renders nicely with proper subpixel hinting. When you release the mouse button, it does a second antialiasing pass or something, blurring the edges of the fonts. This doesn't seem to matter much one way or another on retina displays, fwiw.
Sierra's Preview.app appears to at least mostly fix that regression... apparently at the cost of breaking everything else, but at least PDFs are legible for viewing now.
Not a huge deal, but just another thing it used to do better than the competition and now doesn't.
Goto page has never worked reliably for me, even prior to the update.
That said, apparently one of my C++ working drafts actually causes Preview to spend 20+ seconds at 100% CPU when opening on macOS 10.12.2. That's no good, and I don't recall it doing this before. Time to go file a radar I guess.
They added the goto in an update, but the failure to remember last page read is still a sickness in just about every major PDF reader.
Oh, and while I'm ranting, it ought to show the first page of the PDF as the thumbnail. Some do it, some don't. C'mon, guys, it's 2017. It's like getting an update to your favorite programming language and they removed scoping of declarations.
Here's one: open any pdf in Preview in 10.12.2, choose the Rectangular Selection tool, and try to copy a rectangle from your PDF. On my own machines running 10.12.2 as well as the couple machines I've tried in the Apple Store, inevitably this leads the whole page to go blank. AFAIK the file is not affected, it's purely a UI thing, but bugs like this make the software very annoying to use at the very least.
Apple is putting their money into iOS development. And in breaking things in OSX which previously used to work...
It was (and still is) a great OS to use - but to pretend that pre 2007 existed a time where everything was perfect and no problems existed is absurd.
Yosemite was by far the worst macOS version I've ever used. I'm pretty happy with El Capitan though and I won't upgrade until I really need to.
> lot more bugs and problems since Apple switched to a yearly
> release cycle.
This has worked more or less ok for me with the major exception of Yosemite. Snow Leopard and Mountain Lion were the most stable and polished versions I've used.
Does the old stable still get equal security fixes?
> I hope that's sarcasm.
In fact, i haven't found a single .ps file it didn't hang on so far, but maybe i'm unlucky.
(so, basically, when i go to open an older paper, i have to go kill preview, run the paper through distiller, and then load it in something that isn't a disaster once i realize preview is also highly broken for pdfs anyway)
And out of curiosity, was the CPU busy or idle during the long-running conversion step?
I've attached debuggers to them and they appear to be sitting around in the same loop, probably never to exit ...
I've had this complain (and bug filled) for a long time. They changed it a few years ago, blacks are completely washed out.
But I haven't yet had the inclination to install Sierra.
And you are right - this started pre Sierra already (can't remember which version)
But I'd disagree. No Adobe software does this by default. Trying to simulate a reflective medium in a emissive one by decreasing the latitude can be useful at times, but simply showing it like that with no option to turn it off seems crazy to me.
It goes to the very heart of the industry, though: our self conception, so it would be a very hard transition.
Second, the rampant rewrites are as much an issue in FOSS projects as they are in the industry (and in fact Microsoft for one, besides introducing the occasional new API has been careful with backwards compatibility to the point of paranoia).
Again, I think it is a deep problem, involving the self conception of the tech world (not only the marketing departments, although there is mixes with self interest.)
Apple has traditionally been pretty good in the quality department, but they have never given a rat's ass about backwards compatibility. As they move forward with the whole iOS-is-the-future vision and OS X goes into legacy mode I shudder to think how bad things will get.
I still use Skim from time to time but the comment annotation UI being broken in 10.12 was a deal-breaker.