Yes, in the late 80's, I was frustrated how slow PL/M was to compile even the most trivial program (order of 5 minutes for DO ... END). I developed PLD which had had fast compile as its objective. I separated all tokens with spaces and code was strictly left to right (e.g A + B -> C ; rather than C = A+B;). The first self-compiler was about 1500 lines and self-compiled (after some optimizing) in about 45 seconds on same hardware as PL/M above.
Can such standard also include setting the default for echoing the password? Seeing that I have entered ### for a 5 character password is perfectly adequate. But for a 17 character password, echoing ######### does not give me useful feedback where I am or allow me to meaningfully edit mistakes.
Yeah, if I am projecting my screen in front of an audience of 300, I do not want my password echoed. But when I am using my mobile phone, getting feedback is far more useful than guarding against someone reading my screen.
Before you get too far, try an A/A test. By this, I mean let the A and B choices be identical. You would certainly expect the outcomes to be equal. Right?
I have seen statistically significant differences in outcomes in A/A testing.
A/B testing has value but being sure to A/A test may temper your expectations and/or point at problems in your setup before you get too far.