Lightroom Classic on Mac :: breakdown of two screens doing separate work

  • 1
  • Question
  • Updated 2 months ago
I have been using Lightroom since its first release, on Mac. I have also been using two screens, one a thunderbolt.

ever since Lightroom has become Lightroom classic, which to me indicates a movement away from active development in terms of coder career choice. that is, I have worked at bell labs and Microsoft, and whenever a product becomes classic, it's not really professionally optimal to be on it any longer. this was also true in animation. no one at PDI wanted to be on the Skrek treadmill by the third version. in fact, we got Pixar recruits just for their sanity.

what happens with depreciated development within a power organization is that hard problems of infrastructure or scale get dropped ... one of the nasty secrets of software development --  I was one of the determinators of what got fixed or not of the many thousand bugs reports on our c++ compilers each day, and we don't fix everything, and the less valuable the product in our future, the less etc.

so, when I can no longer use the two screens independently but have Lightroom interfering with my other screen, and therefore the arena, I assume this product has been deprecated, but is not being publicly pronounced.

when I was editor of the c++ report, I had inside knowledge of all the pc compiler vendors for c++, and they lied barefaced about their support for essential c++ libraries. I was at Microsoft as architect of the c++, and we wouldn't ever tell anyone the truth of what we intended, which was dictated not by users but our money customers.

so, what I am asking is. is adobe really committed to fixing usability problems in Lightroom on a single machine any longer, or it is going to throw us oldies under the bus for a new generation, and how soon should I jump ship before I drown in a tsunami of nits that make adobe on a single Mac almost a Microsoft experience. I mean, really now.

old coders just decohere. there is no sense of generation or history among coders, I find. it is worse than sports ... bill Russell. bill joy. give me a break. sorry for the rant. this is my end game, and all the bits seem to be changing. peace.
Photo of stanley lippman

stanley lippman

  • 8 Posts
  • 1 Reply Like

Posted 2 months ago

  • 1
Photo of stanley lippman

stanley lippman

  • 8 Posts
  • 1 Reply Like
here is a nit example: I had just gotten home from a bone chilling waterfront photo session of two hawks making a nest. so I uploaded the photos to Lightroom, and I just wanted to fix the light to see how many were actually in focus since they were moving and I was using a 600mm lens without a tripod.

so, I have Lightroom on my left, and I need to prepare to game of thrones, so I am watching the battle of the bastards on my right. good stuff all around.

as soon I begin putzing with getting the details of the poorly lit shot, I lose the battle of the bastards, and I am back on my home left screen. oh. that's not cool. 

I have lost touch with all the details of my os, so I switch the apps and put Lightroom on my master display. same thing. that should not happen. Lightroom should not disturb the universe of the os, thank you very much.

or, am I just being an old dog, and querulous? there are a thousand nits I can detail, but what it amounts to is, I can't use two screens, except if the second one is also owned by Lightroom. that is what I call Microsoft code intelligence. doh.

or else I'm just braindead and can't calibrate my Mac any longer. the first rule of software coding is to first assume you're the dunce. it use to be I could walk down the hall and find revelation. now, winter is coming, and I can't use Lightroom and watch.
Photo of stanley lippman

stanley lippman

  • 8 Posts
  • 1 Reply Like
sorry, second paragraph, 11th word: for ...
this is how I use to correct sadly every addition of the c++ primer I was author to. 
I was at bell labs when Kodak contacted Bjarne about using c++ to create a digital photo system ... that was only twenty years ago. nobody really has any clue where we were headed with all this. I hope adobe doesn't fall off a ledge following mobility ... I watched 2d animation die at Disney ... why does adobe think its domain is impervious. I'm irritated at their triviality and sucking up to mobility ... it is insulting to those of us who understand color and light and pixels ... I defended adobe against all attempts at the free software folks to duplicate photoshop and drive adobe to its knees. but I wouldn't do that again.