emoeller

dewme said:

I gave up on this native feature because it seemed overly finicky and bought the Copied clipboard manager app that works all of the time and has a history list / stack. It works on iOS and MacOS and uses iCloud sync. 

I agree, I have used Copied on all of my devices for more than a year without fail.   Very handy app.  

I had a 2009 iMac that just wouldn't work with Universal Clipboard, which is why I purchased Copied.   But my new 2017 iMac does work with my 2013 MPP, iPad Pro and iPhone 7 -- but as noted Copied has a LOT more features.

Sigh, this is a buying opportunity.   Usually there is a run up to Apple's quarterly reporting (which is this Thursday) and then drop on the usually good Apple news.   This time I believe it will be the reverse.

I hope they don't ditch DVD player - how would I watch DVD/netflix rentals?  I live in a rural area with limited broadband coverage...

The easiest way to determine what KIND of program is running is to use Activity Monitor.   From the top menu under View/Columns select KIND -  it will show whether the program running is 64 or 32 bit.   

I have some older utilities and drivers for hardware that are 32 bit that most likely can not be updated.    I have just replaced my 2009 iMac with a new 2017 iMac (big shout out to AppleInsider and their sponsor Adorama - they had THE BEST price and their service was excellent) and I'll use my old machine to run those older programs and hardware going forward.  

I watched Intel's CEO interview live ( https://www.cnbc.com/2018/01/03/intel-ceo-brian-krzanich-on-security-flaw.html ) and I would characterize it as damage control, with little substance.  AMD has already rebuked Intel's statement  ( https://www.cnbc.com/2018/01/03/amd-rebukes-intel-says-flaw-poses-near-zero-risk-to-its-chips.html ).

There is MUCH more to this story (Intel claims this was uncovered by Google "a couple of months ago", but Apple had a fix out Dec 6th (OS X 10.3.2)).  In the Interview Intel's CEO seemed to the scold the press for highlighting an unfortunate leak by a Linux programmer (who posted his findings on GitHub).   

Intel also notes how the "industry" is working together to provide software fixes - without noting that those don't solve the hardware problem.  And if not carefully tailored to fix the kernel issues on an individual chip basis the software fixes could cause serious issues for non-affected chips (including Apple's and AMD's - remember that virtual OS can be chip agnostic).