And the last round of changes we made to attempt to mitigate that remain largely un-adopted, because of the drastic nature of *those* changes. At least the last round didn't change the API people expected for attribute retrieval - this one makes even the longest standing attribute lookups break. You're breaking every recipe, every blog post - 6 years of knowledge. You think it sucks now? Wait'll you see what doing it again this close does. You really think it will delight people to have to search and replace:

```ruby
s/node['ipaddress']/node.sys['ipaddress']/g
```

Cause I know what I would tell you. I'm telling you right now, actually. :smile:

The appetite for our actual users to suck up another dramatic breaking attribute change like this is not high, at least not amongst the customers I've talked to in the last 6 months, all of whom are still struggling to deal with the last one. 

Better handrails? Better error messages? Notifications? All kinds of things could make the experience better. I even think we don't have much choice but to fix the desired/observed state mix up. Lets focus on how to make the experience of what we have better, not how to inflict another global rewrite.