Core ships IntegerItem, DecimalItem, and FloatItem field types. The core Options module adds ListIntegerItem and ListFloatItem.
This means if you want to add a field to 'store a number', you have five choices - it is overwhelming.
I don't think I have ever used FloatItem on a site, ever.
Since these are plugins, they should be straightforward to move to contrib.
When we originally added fields to core in Drupal 7, the idea was to bring in all the field types we could think of (except location co-ordinates afaict) so that people could build things just in core with fields + views. However the sheer array of similar field types undermines this a bit and makes it more likely that people will make bad choices (or get stuck), and project browser should make it easier to find and add field types from contrib.
Deprecate both 'float' field types, leave decimal and the two integer fields for now.
Active
11.0 🔥
Usability improvements related to the Field UI
It is used to alert the product manager core committer(s) that an issue represents a significant new feature, UI change, or change to the "user experience" of Drupal, and their signoff is needed. If an issue significantly affects the usability of Drupal, use Needs usability review instead (see the governance policy draft for more information).
Tagging with Field UX to make this visible on our board: https://contribkanban.com/board/FieldUX
Re-titling to use the names of the field types as they're shown in the UI.
I think @lauriii is +1 but tagging explicitly for product manager review since this is removing a user-facing feature.