Comparison of ArcMap & ArcGIS Pro - Feelings

[RTPL_AU]

I have come to the conclusion that my feelings toward Pro can be summarised as follows.

In ArcMap I looked for workarounds due to limitations. This process is rewarding and stimulating.

In Pro I feel as if I spend a lot of time looking for workarounds due to bugs, bad performance, or UI/UX design flaws. I experience this process as frustrating, mind numbing, and distracting. 

You're on a roll doing some cool work for a client and then BANG - you get an error about spaces in a path. 
I did the same workflow a few weeks ago on the same project with the same data so obviously I did something wrong? Wrong. I made the mistake of applying an update in the hope that something else is fixed!

OK. Now distracted from the client's slope problem, how do I fix the process problem?
Restart Pro and clear cache always !works... Nope.
It must be the data  - something new was added?  After 15 min - Nope.

Start another machine and do the same thing in 3.3.5 - guess what. It works fine.
There goes 30min of wasted time and 60min of distraction while trying to get back into focus to solve the client's slope problem.

Is Pro useful? Yes. More than ArcMap? Yes.
Was it good at launch in 2015?  No.  
Has it improved over the last DECADE? Yes. A lot. 
Is it 'good' to use? Maybe, as long as what you're doing doesn't brickwall you into its issues.
Should 7 figures in licensing cost for a single person come with less frustration than stuff that cost a few hundred a year? For sure.

Where should Pro be in another 10 years?

Where can we lodge Ideas for ArcGIS Next? 

Who should guide the requirement spec for ArcGIS Next? 

[JohnGuilfoyle]

I have been using ArcMap for routing for about ten years. I have just
switched to Pro and am experiencing the Growing Pains associated with any
new platform.
I was dumbfounded that the Primary tool I relied on for Network Analyst
Routing did not make the transition.
The Network Analyst Window showed the stops and their Property Numbers in
numerical order. A stop could be dragged and dropped, or a group Cut and
Pasted to reorder their sequence. This is gone and replaced with the
attribute table, where the new sequence numbers must be manually entered
over the previous values. This leaves massive room for keystroke errors or
sequencing errors when you have to reverse the order of stops.

A stop that was moved on the map in ArcMap had its Network Location
information updated automatically and immediately. No, the Network Solver
or Calculate Locations tool must be Run to get that same value.

It seems a serious step backward to lose such basic functionality.
When contacting technical support, it seemed odd that the last few issues
on which I needed help had no answers available. Twice, in follow-up, I
was told that the issue had been known and registered as a Bug years ago,
and that the Development Team was working on a solution.
Being new, it seemed disconcerting that functionality was lost with a newer
version of a product.

I can't be the only one who uses NA Routing.

[LetaFranklin]

There are a lot of threads with grievances about this on Reddit. It did totally derail my career as I'd just finished getting a Master's in GIS using ArcMap Desktop and it was literally like starting from scratch for me. Nothing made sense. I felt they (1) gave us long-time users very little support for the transition, and (2) released a very incomplete product. Only now am I comfortable with ArcGIS Pro--very comfortable, in fact--but it has taken me years to get here. The product feels pretty complete, at last. I'm currently studying to take the Associate exam to add to my resume and, hopefully, get a proper job.