New 955 user here. Love the touchscreen functionality, especially for maps (and I like the way touch still works in map pan/zoom mode even when it's disabled for activities.) The current gen of Garmin touchscreens is a lot better than some of their old stuff, like 630, in term of responsiveness and fluidity. 630 was so laggy and unresponsive that I gave up changing data pages during winter runs when I was wearing gloves (that watch lacked UP/DOWN buttons, so you were forced to use the touchscreen to scroll.)
Just to get this out of the way, I'm not going to wade (again) into the debate about whether or not touch should be disabled on the pause page (which gives you access to Save, Discard and other options). I can see the arguments on both sides, although I will say that I've owned a 630 in the past and I absolutely had problems with accidentally saving or discarding an activity when it was paused and I was wearing a long sleeve shirt or it was raining. I also saw people post the same complaints about Vivoactive 3 and 4, which also have a touchscreen.
Having said all of that, where's the logic in disabling the touchscreen for the activity pause page (obviously to prevent accidental Save/Discard), but leaving touch enabled for the Discard confirmation prompt itself? (This is obviously only in the case where touch has been enabled for the activity). Hypothetically, if someone accidentally selected Discard while it's raining, the rain could trigger a positive response to the confirmation prompt.
I realize the workaround here is to simply leave touch disabled for activities, but I actually think it's kind of nice to be able to scroll pages with touch (now that it's actually fluid and responsive, unlike the old 630). Of course the other issue with touch in activities is that data fields can be changed by accident, but that's less of a problem than accidental Discard.
Probably not a huge deal for me personally since I've never accidentally triggered Discard via a button press, and if it's something that becomes a problem I can just disable touch for the activity, but it seems like an oversight/bug/inconsistency.
I also think that a touch confirmation for this kind of thing should be a swipe, not a tap of the 
button. I know that a lot of people hate the fact that touch is disabled for the pause screen, so here's my modest proposal for a compromise. If touch is enabled for activities, then the pause menu supports touch, but any action that's "destructive" or not undoable (like Save/Discard/Lap) now needs to be confirmed with either a physical button press or a swipe. I realize that would kind of suck from a consistency/predictability POV, so it's probably not going to happen.
Anyway, thanks for coming to my TED talk.
