For some reason this reminds me of [https://en.wikipedia.org/wiki/COBOL](the COBOL programming language), though not even COBOL was batshit enough to use numerals written in plain English. Everything else was in plain English, though, which was supposed to make it easier to read and write, but is in reality a horrible idea.
Though all caps just reminds me of early programming languages in general, since we didn’t separate uppercase and lowercase in all machines back then, instead using encoding schemes like DEC SIXBIT. Saving memory by using only six bits per character instead of seven or eight, and such. Six bit characters had matching word lengths, before the concept of a byte there used to be loads of 12-bit and 36-bit architectures, that more-or-less went away when the industry almost collectively decided to take byte-addressed memory into use.
How about, ONE POINT SEVEN FIVE TRILLION KILOGRAMS PER HECTARE SQUARED!
Or perhaps, TEN BILLION FOOT POUNDS PER SQUARE INCH!
Or even, FOURTEEN MILLION ONE HUNDRED AND SEVENTY FIVE THOUSAND, TWO HUNDRED AND SIXTY THREE CUBIC DECILITERS PER YEAR!
For some reason this reminds me of [https://en.wikipedia.org/wiki/COBOL](the COBOL programming language), though not even COBOL was batshit enough to use numerals written in plain English. Everything else was in plain English, though, which was supposed to make it easier to read and write, but is in reality a horrible idea.
Though all caps just reminds me of early programming languages in general, since we didn’t separate uppercase and lowercase in all machines back then, instead using encoding schemes like DEC SIXBIT. Saving memory by using only six bits per character instead of seven or eight, and such. Six bit characters had matching word lengths, before the concept of a byte there used to be loads of 12-bit and 36-bit architectures, that more-or-less went away when the industry almost collectively decided to take byte-addressed memory into use.