Pitch me. I could switch, but it would help a great deal to understand more about why. I’m open to change, but not eager to change.

I’m very happy. I had the same early experience as you, but I kept with it. I’ve been using it several years now. When I’m forced back to vim, my fingers remember just enough, but I have to undo pretty often.

I kakoune instead.

The fact that the loop is doing “find first driver matching these strange criteria” seems most obviously obscured by the pattern of assigning a value, then killing the loop or not. This strikes me as the part that makes the algorithm tedious to test, since it forces us to use a collection to test the intricacies of the inner conditions.

Once we isolate “find first driver matching condition” from computing the condition for each driver, I consider the rest a question of personal taste. Specification pattern, composition of filters, something like that. Whatever you find easier to follow.

Only if temperature distribution is a continuous function.

I guess it’s time for a “mark this time so I can go back to it” feature, to reduce the need to pause. 🤷‍♂️