Not sure I can get behind this one. This is a quote from the write up you linked and while I agree these comments are dumb, a “don’t use this because our font won’t support it or a no it’s the editors that are wrong and should change” approach feel ridiculous.

Sometimes programmers rely on the monospaced grid to create a second column of values or comments on the right side of the page. It’s true, these secondary columns won’t align in a proportionally spaced font. But why are we making these columns in the first place? Even in a monospaced font they can be finnicky and hard to maintain. In virtually every other form of typography, the responsibility of alignment is given to the typesetting application, not the font. If source code editors can highlight syntax, they could also interpret tabs and syntax to create true, adjustable columns of text.

+1 for Go and Input fonts. You have the same stack as me.

I just don't see how this:

^(https?://)?([\da-z.-]+).([a-z.]{2,6})([/\w .-])/?$

Is easier to read than this:

^(https?:\/\/)?([\da-z\.-]+)\.([a-z\.]{2,6})([\/\w \.-]*)*\/?$

It's not about alignment - tabs work in any decent editor. I just think it's easier to read fonts that are a little more spread out especially with operators.