When I first proposed some of the ideas like quasiforms, they were quite foreign.
Now they're familiar. Given their familiarity, I start to wonder if the "weird" nature of null and okay is tolerable for source code. e.g. might you write:
var: ~null~
...instead of...:
var: null
It's a bit annoying to type, but if you get used to it, it's not necessarily bad to stand out in that way.
Not that this should matter too much, but using ~null~ is inherently faster. There's no variable to look up... you're just turning a WORD! at the quasiform lift level to the antiform lift level. (Technically that does require validation, since not all quasi-words are legal anti-words, but this validation can be arbitrarily fast.)
One negative side of using the quasiforms is it may add noise where it's not something you want to emphasize. As such, maybe this is a decision to be made on a case-by-case basis... do you want to draw attention or not, like... "HEY, I'm setting this to NULL and that's an important point!"
Not sure. But I find myself tempted to use the quasiform now and again, and usually decide to back it out because I feel like it should be "always do it" or "never do it". But maybe that's the worng dichotomy.