I actually recognized that in one of my other posts when I brought up skill feats. I think it’s a good idea, but it screws up the simplicity.
When I say the framework is consistent with few exceptions, I mean the framework. You get three actions and a reaction, and you don’t have various exceptions written into the framework. We don’t need to have discussions about how many times a paladin can smite in a round or whether under some circumstances we can cast two spells because the action economy handles that. We also don’t need to memorize a table of situations where something provokes an AoO, but we also don’t have to give up the richness that 3e and PF1 had by simplifying it down to one or two events. Yes, there are traits like [Flourish] and other traits, but if you’re not dealing with those, you can ignore them. If you are, they’re explicit about what they do.
The same goes for making rolls. Everything is a check. Everything works on a same scale. If you can justify rolling a Reflex attack versus an Attack DC, the math will work. Something modify Strength checks? Then yes it affects your attack roll. They restate that in conditions like enfeeble, but I think that’s just to accommodate people who are used to attacks and saves and checks all being distinct things.
This is true.
Had Paizo been able to resist cluttering this down to the point where this clean design is entirely obscured by fiddly exceptions I would agreed. Now I merely see myself some 15-20 levels ago, before I got disillusioned.
After all, we're not playing the framework. We're playing the full game.
Let's take an analogy from the computing world, just because people here seems to be itchin' for a computative dick-measuring contest!
PF2 comes across as if a competent programmer (let's call him "Kenada") went down the basement and came back up a year later with a elegant core engine that just hums, across all levels. Pressing F11 gets you consistent results, just stronger as you level up. Then you have the sales force that just say "yes" to every customer, no matter how ridiculous or incompatible their demands, forcing this "Kenada" to create all sorts of subroutines and overlays. You press F11 to do this, except you can't if these three circumstances are in play (but do press CTRL+L to allow F11 even when that middle circumstance has happened!), and if you've installed this thing over here, it actually does the reverse of what you want it to do, but you'll have to remember that yourself.
This framework you are speaking of is the core engine. The subroutines and overlays foisted upon it by the sales dept are the feats, and the items, and the individual skill actions.
The problem is that at level 1, you're mostly interacting with the core framework, easily compartmentalizing the odd feat rule, dismissing the weirdly limited skill rule as "we're just level 1" and probably not interacting with magic items at all. At this point I would not recommend making predictions about your future experience, at level 11 or 19... Just sayin'