Function-based component API (extended discussion) about rfcs

[yyx990803]

I think most of your arguments have been addressed in this reply.

[jonaskuske]

(I need to find in setup() where a value is, where a method is, and which fields are computed, whether a field named isEnabled is value or computed)

With the current API, you need to figure out whether isEnabled is a value or computed so you can find it, because they are in different locations.
Then you need to find where a related method is, because it it somewhere further down the file, between other methods doing completely unrelated things.

With the function-based API, you just need to figure out "what is this code doing", get to that part of setup() and everything will be right there – isEnabled can be there no matter if it's a value or computed, the respective methods can be right next to it, no searching necessary.

You probably use Single File Components, instead of putting all the <script> sections of your components into one folder, the HTML template into another folder and the styles in a third. Precisely because grouping things that are related and have the same concern makes for better ergonomics.

All that said, if you want to group by type, the setup() API is flexible enough to allow for that.