Good idea, but in the example, sortedList was meant to be imagined as an expensive operation, mimicked by [...list] that operation still happens each time the count is increased and is still <101.
So this can be a way to work around the described problem in some scenarios but doesn't completely fit the imagined scenario here.
Hmm yeah, but if it's the sorting that's expensive then you could have a computed property for the sortedList instead. It's the same thing, the idea is to separate the expensive operation into its own computed property.
Good idea, but in the example,
sortedListwas meant to be imagined as an expensive operation, mimicked by[...list]that operation still happens each time the count is increased and is still <101.So this can be a way to work around the described problem in some scenarios but doesn't completely fit the imagined scenario here.
Hmm yeah, but if it's the sorting that's expensive then you could have a computed property for the sortedList instead. It's the same thing, the idea is to separate the expensive operation into its own computed property.
While you may be right here, I don't think this is supposed to be a perfect example.