yeah the third item on your list is what drove me here to complain. how do you expect me to read any text on your site when it moves up or down approx. an inch every second?
Even if it writes the same or even somewhat worse rust than python, assuming the output is the same you are likely to get a speedup + a better distribution story.
This is unfortunately exactly why I never used (neo)vim or kakoune (or tbh, sublime text whose lsp integration I have never successfully gotten working). Going from school (Java + NetBeans/C# + Visual Studio) to work (C#/JS + Visual Studio -> C#/TS Visual Studio Code) I had expectations for certain language features being available by default. Helix is the first editor of its ilk to get configuration out of my way so I can effectively write code the way I'm used to.
Why would that happen? Participating large businesses are completely fine with the existing practice. Sure, someone can bid on your trademark, but you can also bid on theirs and probably don't want to lose that ability.
The author is clearly not talking about left-pad like that library is still specifically an issue. He's raising it up as an example of a problem that is still occurring. He then makes the point that maybe we should have less packaged JS code in general and that more software solutions should exist (and should have always existed) as part of the standard library or well-maintained packages like Lodash (although he doesn't reference it by name, just the concept it exemplifies). It feels like you've missed the forest for the trees.
Someone else mentioned evil-helix if you really want those keybindings but, admittedly, I think the different keybindings (and more specifically the select then operate model) are a major point of why helix (and its inspiration, kakoune) exists.