At first I read SIMD bucks and I thought they must take optimizing code seriously.

I think you guessed right. It could be phrased more clearly but I think they were just pointing out that since your comment is partially censored and your instance is known for word filter censoring, in their opinion your instance is not suitable for commenting properly. Maybe they wanted to inform you in case you didn’t notice or it was just a dig at lemmy.ml.

It’s not good for readability when random parts of text gets removed. I’m not familiar with the topic of this thread so I can’t deduce what Raremoved even means.

I think it’s just that raremoved part. Which comment didn’t make sense?

Can you give an example how that would happen?

I’ve always thought that macros in vim are slow and clumsy to use. You have to think about getting back to initial state as you record if your intent is to repeat the macro several times. If you make a mistake you have to either record an action that corrects the mistake or edit the macro later after recording. You have to know beforehand how many times you want to repeat the macro or run it one at a time which is clumsy at least with Finnish keyboard layout.

Norm command is much faster to use for my purposes because I can use it for several lines at a time without thinking about the state. I can use it with ranges or with g/re/ and v/re/ commands. If I make a mistake I just delete it. Only thing on the plus side I can think of for macros is it’s WYSIWYG approach. You have to have a visual editor in your mind when you write long norm commands.

Here’s a tip for you: use :%norm @a to run the macro in register a for every line of the file.