For the "Page" content type that comes pre-configured with a normal Drupal install, I advocate for using the "long text" field type instead of "Long text with summary" for what used to be the body field.
The Page use-case wouldn't likely need a summary. And the UI with the long text with summary is still somewhat problematic, with a confusing "edit summary" link next to the Full text label. I think that having an alternative approach to handling a text field pre-installed is of great benefit. And the fact that the data-entry UI would be so much simpler is a real plus.
On the support side of things, when people are confused with the full text with summary UI we could point them to the Page content type and easily show them an example of a different solution that might get them what they want with a simpler UI. It's a lot easier to tell people, "Go to node/add/page" then it is to give them instructions on adding a new content-type and adding a field.