Boy, finally somebody who also hates a certain letter. I hate c - it’s totally garbage letter.
Take for example Pacific Ocean. Every damn c in that two word is pronounced differently. Worst part, you could replace it with other letters (Pazifik Oshean). It’s redundant.
For example, in Year 1 that useless letter "c" would be dropped to be replased either by "k" or "s", and likewise "x" would no longer be part of the alphabet.
The only kase in which "c" would be retained would be the "ch" formation, which will be dealt with later.
Year 2 might reform "w" spelling, so that "which" and "one" would take the same konsonant, wile Year 3 might well abolish "y" replasing it with "i" and iear 4 might fiks the "g/j" anomali wonse and for all.
Jenerally, then, the improvement would kontinue iear bai iear with iear 5 doing awai with useless double konsonants, and iears 6-12 or so modifaiing vowlz and the rimeining voist and unvoist konsonants.
Bai iear 15 or sou, it wud fainali bi posibl tu meik ius ov thi ridandant letez "c", "y" and "x" -- bai now jast a memori in the maindz ov ould doderez -- tu riplais "ch", "sh", and "th" rispektivli.
Fainali, xen, aafte sam 20 iers ov orxogrefkl riform, wi wud hev a lojikl, kohirnt speling in ius xrewawt xe Ingliy-spiking werld.
In the same vein, as a non-native speaker, I sometimes find it funny when even words that are written the same way (or are very close) are pronounced differently. E.g. read vs. read.
And then I also hear from movies that people pronounce "interesting" in different ways and begin to question how it should be done.
Of course, my native tongue has it's own quirks and peculiarities. I guess languages are the ultimate legacy projects with massive amount of contributors :).
The redundancy comes in part from the oldest forms of the Latin alphabet, where there were 3 forms of C, K was used before A, C was used before E or I and Q was used before O or U.
Later they have understood that writing with different letters minor variations in pronunciation of the same phoneme is useless, so they began to use C in almost all cases where previously either K or C or Q were used, but K and Q have survived for some niche uses.
The next complication has arisen in the Middle Ages, when in many European languages the pronunciation of C before E and I has been changed and instead of being the same as K it has become like the pronunciation of either English "s" or English "sh" or English "ch" or English "ts".
Because English has borrowed many words from a lot of languages, keeping their spelling, it has gathered all these pronunciations, so as you have pointed, all these different pronunciations are possible in English and it is unpredictable which of them must be used in a given word.
Yes, you got me, I‘m German. German is even worse when it comes to the letter c. Chemie vs. Choreografie… and I know there are lunatics who pronounce it „Kemie“, but still.
For non German speaker, both words start with „ch“, one is commonly pronounced softly like „shemie“ while the other one is pronounced like a „k“ - similar to the English choreography. Even in English „chemistry“ is pronounced similar with „k“.
I just took a look at Sanskrit, and it doesn't represent everything.
It has a larger consonant inventory than any other natural language that I've ever seen, which is impressive, but that doesn't make it phonologically universal.
Some things that American English has that Sanskrit doesn't include /ð/, /θ/, [ɹ] as a realization of /r/, and contrastive /v/ and /w/ (like "vein", the body part, versus "wain", the old word for a wagon; or "vine", the plant, and "wine", the beverage made from it).
I'm unclear on the effects of the vowel gradations, so I don't know whether they approximate other languages' vowel inventories well.
It also looks like Sanskrit doesn't have any uvular, pharyngeal, or glottal consonants, and no velar or post-velar fricatives. For example, I don't see that it could represent Hebrew חָכָם 'wise, smart' (pronounced /χa'χam/).
I could see that Sanskrit might have been the best single choice for transcribing a wide range of unrelated languages at some point in history, but now that we have IPA, we can make lots of distinctions that Sanskrit doesn't.
As a commenter points out, that’d make programming a difficult pastime. Can’t think of a non-esolang without if and for apart from Brainfuck, and that’s got an f in the name.
Easy in Common Lisp without sacrificing ergonomics or getting stuck in a Turing tarpit.
We'd make a small preamble to define new names for things like DEFUN, Lisp's operator to define new functions. No F's needed to do that either. We can do this by taking advantage of read-time evaluation.
First we get references to the symbols DEFMACRO and DEFUN.
This technique can be used to access any symbol in Common Lisp that may have an F in it.
Now, to make life-without-F easy, we define new names for DEFMACRO (mac) and DEFUN (proc) without actually lexically referring to the F-infected symbols:
Now we can define functions with PROC instead of DEFUN. Here's the Fibonacci function, with the F censored out. Note that we don't need IF since Lisp has the superior COND:
This is excellent! I was playing around with a lisp (hy) recently, and hadn't really used macros before then. It's amazing how much you can reengineer lisp from within to meet your needs, even if they're as small as "I don't want to use F".
I haven't seen any non-lisp languages that give you that kind of power, for better or worse.
Would it be better for you if we took the Nth symbol in alphabetical order from the list of 978 standard symbols? You could do that.
How about searching for all symbols with the letters DEMACRO that are 8 letters long? We could do that too.
The technique works so long as you can uniquely determine the symbol through some combination of standard Lisp functions that don't contain F. Lisp has a big library, so it's not tough.
"70" isn't a number that is associated to F in any common person's understanding, and the pronunciation of the number "70" in English has no objectionable F sounds, so I don't agree it's cheating. :)
In Lil[0], avoiding "F" is doable, but not very convenient.
The if/elseif keywords are off the table, but you still have both explicit looping constructs and function declarations:
while x ... end
each x y z in w ... end
on name x y do ... end
There are five primitive operators with "F": typeof (rarely needed), floor (inconvenient to work around but at least you still have % for modulo), first (can be replaced with indexing), flip (transpose a matrix/table; this could be replaced (slowly) with a user-defined function), fuse (join a list of strings into a single string; very difficult to do without, since Lil doesn't have a vanilla string-concat operator), format (string formatting; this removes tons of functionality and the easiest ways of working around not having fuse).
Most of the query forms (select, extract, and update expressions) would be OK, but they all need a "from" clause to specify the source table, so no dice.
What you're left with is still very much Turing-Complete, but much less ergonomic.
“Mapping from source file (other than a UTF-8 source file)(since C++23) characters to the basic character set(until C++23)translation character set(since C++23) during translation phase 1 is implementation-defined, so an implementation is required to document how the basic source characters are represented in source files.”*
JavaScript gives you the ternary operator (?/:) to handle conditionals plus switch/case. Plus you get map/reduce methods on iterables, and you can write procedures with “const thing = ()=> {}”
I think I could write an arbitrarily complex program without major issue.
> and a convoluted while where you could write a “for”
What's convoluted about it? A `for` is about as simple as syntactic sugar gets.
for( a; b; c ) {
}
is exactly equivalent to
a;
while( b ) {
c;
}
(OK, a variable declared in `a` will remain in scope after the while loop terminates, but the only way for this to have an effect on anything is if you intentionally refer to it afterwards, in which case you needed to predeclare it for the for loop too.)
I wonder how easy it would be to avoid that letter when programming. It would certainly be easier in Perl, since you can use unless conditionals and while loops, and subroutines are simply called sub. In the case you absolutely need a module using the dreaded letter, require can be used instead of use so that letter can simply be escaped. The same applies to method calls, just call indirectly. The idea reminds me about JS*uck.
While he hates the letter F because it looks like an incomplete letter E, this resemblance is relatively recent and it is due to the Ancient Greeks.
The letter F was originally the letter "waw" of the North-Semitic alphabet, then of the Phoenician alphabet derived from it.
In the Phoenician alphabet, the letter "waw" looked like a Y.
When some Greeks have derived the Greek alphabet, they have created two distinct letters from the letter "waw", the letter that was later named digamma, which retained the position in the alphabet of the Phoenician "waw", and the letter that was later named upsilon, which was appended immediately at the end of the alphabet, after the last of the Phoenician letters.
For unknown reasons, upsilon has kept the form Y, while the top of digamma has been rotated, becoming F.
The letter digamma has continued to be pronounced like in Phoenician, where it was used to write the consonant a.k.a. semivowel form of U (which in English is normally written as W). The letter upsilon was used to write the vowel form of U.
So the Greeks have created two letter variants of the original "waw", written as F and Y, to distinguish the consonant and vowel uses of U, like English has created W to be distinct from U, for the same purpose.
The letter E comes from the Phoenician "he", where it had a similar form, but it was reflected. The reason why the Greeks have reflected E is likely to be the change of the direction of writing from right-to-left to left-to-right. So it is in the Greek alphabet where E and F began to look similar.
Most Greek dialects have lost the semivowel U, therefore also the letter digamma, but that had not happened yet in the dialect from which the Etruscans and the Latins have taken the alphabet, so it still had F.
Latin had a consonant not present in Greek, that which now is written F. Because there was some resemblance between Latin F and semivowel U, both being labial, the Latins have chosen F to write this consonant. Moreover in Latin the form of Y has been simplified to V. Also Latin had both semivowel U and vowel U, but they have chosen to write both of them as V. The letter U has appeared only in the Middle Ages, initially only as the small letter "u", which was the small variant of "V", the forms "v" and "U" have been added later, together with the different pronunciations attached to the letters. Some centuries after the first variants of the Latin alphabet, the letter Y has been appended to it, because by that time the Greeks no longer pronounced it as U, but it had become a front rounded vowel, like German U-umlaut or French U or Danish Y.
Therefore the current Latin alphabet has 5 letters derived from Phoenician "waw": F, U, V, W and Y.
Take for example Pacific Ocean. Every damn c in that two word is pronounced differently. Worst part, you could replace it with other letters (Pazifik Oshean). It’s redundant.
C is just a nightmare…