<?xml version="1.0" encoding="UTF-8"?>
<rss  xmlns:atom="http://www.w3.org/2005/Atom" 
      xmlns:media="http://search.yahoo.com/mrss/" 
      xmlns:content="http://purl.org/rss/1.0/modules/content/" 
      xmlns:dc="http://purl.org/dc/elements/1.1/" 
      version="2.0">
<channel>
<title>Vaishnav Sudarshan&#39;s Blog on Cool Stuff</title>
<link>https://vaishnavs.net/</link>
<atom:link href="https://vaishnavs.net/index.xml" rel="self" type="application/rss+xml"/>
<description>Vaishnav Sudarshan&#39;s blog on linguistics, math, computer science and natural language processing</description>
<generator>quarto-1.7.32</generator>
<lastBuildDate>Sun, 02 Aug 2026 18:30:00 GMT</lastBuildDate>
<item>
  <title>Semantics Part 1: Theory Behind Meanings</title>
  <dc:creator>Vaishnav Sudarshan</dc:creator>
  <link>https://vaishnavs.net/posts/Semantics/</link>
  <description><![CDATA[ 





<section id="semantics-intro" class="level1">
<h1>Semantics Intro</h1>
<p>Semantics is the study of meanings and how they are derived. Just from writing, it’s not always possible. For example, take the words “cat”, “dog”, and “catastrophe”. If you didn’t know English, you might guess that perhaps “cat” and “catastrophe” are close in meaning, but that’s not true, relative to “dog” (dog-lovers, I know you’ll strongly object and point out that cats are a form of catastrophes). The words “dog” and “cat” are in fact actually more closely related to each other than to “catastrophe”, because they both are pets.</p>
<p>But why would you need an entire subfield of linguistics dedicated to meanings? You can just look up a word in the dictionary, right? WRONG! For one, it’s very hard for dictionaries to account for language variation - semantic drift is omnipresent, and different dialects or idiolects perceive meanings differently.</p>
<p>In this blog post, we’ll talk about the origins of semantics and modern semantics, and the second part will be all about how LLMs understand meanings.</p>
</section>
<section id="philosophy-of-language" class="level1">
<h1>Philosophy of Language</h1>
<p>The first people who pondered about how meaning comes from words were actually not linguists, but philosophers! Some of the ideas presented by them are now core concepts in semantics.</p>
<p>The ancient Greek philosopher <a href="https://en.wikipedia.org/wiki/Plato">Plato</a> believed that a word represents a perfect abstract concept. For example, the word “dog” represents some idea called “dog” that doesn’t exist in the real world. All instances of a dog that you actually see are just imperfect imitations of that concept. Plato also thought that individual phonemes had some universal, objective, inherent meaning to them, but as you know, this is false, because sound has nothing to do with meaning. This is why Plato isn’t the most trustworthy source, but you can still take that first theory into consideration if you want.</p>
<section id="sense-and-reference" class="level2">
<h2 class="anchored" data-anchor-id="sense-and-reference">Sense and Reference</h2>
<p><a href="https://en.wikipedia.org/wiki/Gottlob_Frege">Gottlob Frege</a> first created the distinction between sense and reference. Reference is the actual thing (or set of things) that the word <em>refers</em> to, hence the name. Meanwhile, sense is the ideas and concepts behind what you express that reference as, and how you perceive it.</p>
<p>Multiple senses can have the same reference - for example, a 2D plane with evenly spaced, perpendicular gridlines of unit length and a fixed origin can be thought of as either the Cartesian plane where each point is of the form <img src="https://latex.codecogs.com/png.latex?(x,%20y)">, the complex plane where each point is of the form <img src="https://latex.codecogs.com/png.latex?x%20+%20i%20y">, or a vector space with basis vectors of <img src="https://latex.codecogs.com/png.latex?%5B1,%200%5D"> and <img src="https://latex.codecogs.com/png.latex?%5B0,%201%5D">, where each point is a vector of the form <img src="https://latex.codecogs.com/png.latex?%5Bx,%20y%5D"> starting from the origin.</p>
<p>One sense can also point to multiple references - for example, if you think of a “person”, then that reference points to over 8 billion people. You could potentionally solve this problem by saying that the set of all people is still a single set.</p>
<section id="sapir-whorf-hypothesis" class="level3">
<h3 class="anchored" data-anchor-id="sapir-whorf-hypothesis">Sapir-Whorf Hypothesis</h3>
<p>There was once a theory, the Sapir-Whorf Hypothesis that the words a language contains limits what the speakers’ brains can perceive. This is now considered to be pseudoscience. A brain’s capacity to perceive meanings isn’t strongly tied to how many distinct senses there are. There is now a less bold claim that is more widely accepted, called <em>linguistics relativity</em> - that someone’s language may affect how they perceive the world, but that doesn’t mean if their language doesn’t distinguish certain references, then their brain is incapable of understanding the difference.</p>
</section>
</section>
<section id="family-resemblence" class="level2">
<h2 class="anchored" data-anchor-id="family-resemblence">Family Resemblence</h2>
<p>Traditionally, meanings of words were given through their dictionary definitions. However, <a href="https://en.wikipedia.org/wiki/Ludwig_Wittgenstein">Ludwig Wittgenstein</a> thought that maybe words can’t be directly defined, but instead speakers can tell what concepts match a word well. This is called family resemblence. For example, what is a game? There’s not a single answer that can always indicate whether something is a game or not. Chess, FizzBuzz, Monopoly, and soccer are all considered games, but you can’t really find a defining feature that is common to every single example of a game. All examples of games have links to other examples, but not necessarily to every single example, forming a <em>family</em>, hence that name.</p>
</section>
<section id="necessary-and-sufficient-conditions" class="level2">
<h2 class="anchored" data-anchor-id="necessary-and-sufficient-conditions">Necessary and Sufficient Conditions</h2>
<p>Necessary and sufficient conditions are also very important in semantics when it comes to determining the criteria that should be present in a definition. A condition is <em>necessary</em> when a statement is true if and only if that condition holds, while it’s <em>sufficient</em> when if the condition holds, then the statement must be true, but the statement <em>can</em> also be true otherwise.</p>
<p>You can also think of it as the sufficient condition being a subset of the necessary condition, because if the sufficient condition holds, then the necessary condition holds too.</p>
<p>An example of this is when it comes to defining life. In biology, an organism is living if and only if it has cells and DNA (among five other conditions) - if it doesn’t have them, then it’s not living. This is a necessary condition of life.</p>
<p>On the other side, if an organism is an animal, then that is a sufficient condition to say that it is living. However, not all living organisms are animals. Again, you can view it like this: animals are a subset of anything with cells and DNA, and there aren’t any animals without cells and DNA - then it wouldn’t be sufficient to say that if something it an animal, then it is living.</p>
<p>Note that some biologists consider viruses to be living, even though they don’t satisfy all the seven characteristics of life.</p>
</section>
</section>
<section id="compositionality" class="level1">
<h1>Compositionality</h1>
<p>A major concept in semantics is the Principle of Compositionality. Basically, since there are infinite possible meanings in the world but you can’t have a brand new word for EVERY single new concept due to the finite amount of mental capacity you have, more complex meanings must be derived from simpler ones.</p>
<p>Of course, if you’re going to use a concept very often, and it’s tedious to describe it using many words, it can either shorten or take a loanword.</p>
<p>For example, English took “déja vu” from French, which literally translates to “already seen”, which, in grammatically correct English (for most people’s internal grammar), would have to be expressed as “the feeling of having experienced something before” if not for this loanword. This is obviously much more concise.</p>
<p>Words can also shorten. The full name of “soccer” originated from “association football” (which obviously no one wants to say every time), so that became “assoc”, and then “soccer”.</p>
<p>However, these cases don’t take away from the main point that meanings as a whole are derived from smaller parts - that’s how you understand this sentence, for example. <a href="https://vaishnavs.net/posts/Syntax%20Part%201/">Syntax</a> might allow you to arrange these meanings in the correct way, but compositional semantics allows you to get the overall idea as to what the sentence is actually saying. If you understand each smaller part, then you will understand the whole sentence, even if you haven’t seen this specific syntactical structure before.</p>
<section id="non-compositional-meaning" class="level2">
<h2 class="anchored" data-anchor-id="non-compositional-meaning">Non-Compositional Meaning</h2>
<p>One complication that arises from the idea of compositionality is that sometimes, the meanings of whole phrases can’t be derived from their smaller units.</p>
<p>Imagine if someone says, “That problem was a piece of cake”. Are you REALLY going to interpret this as something absurd like “ah yes, the problem they’re talking about was secretly part of a cake in disguise”? I think not. The meaning of “piece of cake”, even if it was derived from this image, just means “easy”.</p>
<p><a href="piece_of_cake.png" class="lightbox" data-gallery="quarto-lightbox-gallery-1" title="What the person did NOT mean"><img src="https://vaishnavs.net/posts/Semantics/piece_of_cake.png" class="img-fluid" alt="What the person did NOT mean"></a>.</p>
</section>
</section>
<section id="hyponyms-and-hypernyms" class="level1">
<h1>Hyponyms and Hypernyms</h1>
<p>Now, let’s get into how words relate to each other in terms of how specific they are. A <em>hyponym</em> is a more specific meaning, and a <em>hypernym</em> is more general. So, “cat” is a hyponym of “animal”, and “animal” is a hypernym of “cat”.</p>
<p>To be precise, the hyponym is a subset of the hypernym. This is why every cat is an animal, but not every animal is a cat.</p>
<p>The same concept of unions and intersections from set theory also applies here. “green cat” is just the intersection of anything that is a cat and anything that is green.</p>
<p>You could represent the sets of everything that words or phrases refer to and how they interact using Venn Diagrams, but this stuff is mostly just common sense, not some deep concept in linguistics. There is <a href="https://www.naclo.org/resources/problems/2026/N2026-B.pdf">a NACLO problem</a> on this.</p>
</section>
<section id="negations" class="level1">
<h1>Negations</h1>
<p>One problem in semantics is about how negation works. You might think it’s relatively straightforward, until you realize there’s actually not a single way to “negate” something.</p>
<p>Imagine we have a spectrum (with integer values for simplicity) ranging from -10 (cold) to 10 (hot), and we wish to find the numerical value of “not hot”.</p>
<p>If you do computer science or logic, you might think of negation as the not/! operator, that switches a boolean. You might have a variable for the temperature, and “hot” means “temperature == 10”. With this logic, “not hot” means “temperature != 10”, which means it is any number from -10 to 9. This is the same line of reasoning from set theory, where negation might be the complement of a set (“hot” is a set with a single element, 10), so “not hot” means anything but 10.</p>
<p>However, “negate” literally means to multiply by -1, that’s why if you negate 3, you get -3, not every number but 3. So, the traditional view might say “not hot” is exactly “cold”, or “-10”.</p>
<p>Maybe “hot” just means anything that is leaning towards 10 (so it’s more hot than cold), so “not hot” is all the negative numbers.</p>
<p>You must also consider the pragmatic perspective (future blog post). Why would someone say “not hot” as opposed to “cold”? Depending on their intention, the range of what it represents on the spectrum can vary a lot.</p>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><a href="not_hot.png" class="lightbox" data-gallery="quarto-lightbox-gallery-2" title="Some of the interpretations for “not hot”"><img src="https://vaishnavs.net/posts/Semantics/not_hot.png" class="img-fluid figure-img" alt="Some of the interpretations for “not hot”"></a></p>
<figcaption>Some of the interpretations for “not hot”</figcaption>
</figure>
</div>
<p>If you think this is just a silly thought experiment, think again. One focus of semantics is to find out how languages convey negation. Here’s a more practical example of an English sentence. “I can not do it” could either mean “I am incapable of doing it”, or it could mean “I am capable of not doing it”. You can probably see the difference yourself.</p>
<section id="antonyms" class="level2">
<h2 class="anchored" data-anchor-id="antonyms">Antonyms</h2>
<p>Adding on to the idea of negation, we have the problem of <em>antonyms</em>, or pairs of opposite words. However, the concept of “opposite” is not really a single thing. There are different types of antonyms.</p>
<ul>
<li>Gradable: Two ends of a spectrum, allowing for stuff in between. For example, “hot” and “cold” are extremes, but you can also have “room temperature”, “somewhat chilly”, etc.</li>
<li>Complementary: Exist as a binary, nothing in betwen. For example, someone can be “alive” or “dead”, but there is a clear cutoff distinguishing the two.</li>
<li>Converse: Different ends of a relationship, and one can’t exist without another. For example, you can’t “buy” something without someone else there to “sell” it.</li>
<li>Reversible: One undoes the other. For example, you can “turn on” a light and then “turn off” the same light, which has the same result as not doing anything (in other words, it has an orbit size of 2).</li>
</ul>
<p>Again, it brings up the question of what “opposite” really is.</p>
</section>
</section>
<section id="questions" class="level1">
<h1>Questions</h1>
<p>There are actually a few different types of questions, if you think about it.</p>
<p>The first is a question with a binary yes or no answer, which would usually start with “is/are” or “do/does”, like “do you eat food” or “is the sky blue”.</p>
<p>The second is a question where there is a set of possible answers, possibly of infinite size, and your answer is a subset of that (which can be a single element), like “where do you live” or “who are all in your class”, but even something with a really long answer like “what is the meaning of life”. Semantically, the first type can be thought of as a special case of this type.</p>
<p>Then, there are questions where you list all the options, like “what do you want, tea or coffee”, which assumes you will pick one of them.</p>
</section>
<section id="time" class="level1">
<h1>Time</h1>
<p>Another topic in semantics is how languages express time through tense and aspect, as well as time words. If you want to mark when some verb took place, different languages mark the boundaries differently.</p>
<ul>
<li><p>English has past, present, and future, obviously, but it also accounts for whether something happens and it’s completed, or it’s reoccurring, or it’s completed after reoccurring, or it’s just general.</p></li>
<li><p>Thai doesn’t require that you distinguish tense or aspect, especially if you have context surrounding it.</p></li>
<li><p>Zulu has an extra tense, for distinguishing recent and distant past, but it’s also asymmetric because it only has a single future tense.</p></li>
<li><p>Hindi has something weird, where “yesterday” and “tomorrow” have the same word, “kal”.</p></li>
</ul>
<p>All this goes to show that distinguishing events based on time can work very differently based on the language.</p>
<p>There’s also a joke in Arthur that goes like this:</p>
<p>Mom: “You can stay up when you’re Arthur’s age, D.W.”</p>
<p>D.W.: “But I’ll never be Arthur’s age. He’s always going to be three years older than me!”</p>
<p>This is an interesting case of semantic ambiguity with time. I’m gonna use a bit of math (to foreshadow formal semantics, which is later) to formalize this, although you subconsciously get the joke because it’s common sense, and so is the math. Basically, let <img src="https://latex.codecogs.com/png.latex?t_0"> be the time right now, <img src="https://latex.codecogs.com/png.latex?A(T)"> be Arthur’s age at a moment in time, <img src="https://latex.codecogs.com/png.latex?D(T)"> to be D.W.’s age at a moment in time, and <img src="https://latex.codecogs.com/png.latex?t%20=%20A(T)%20-%20D(T)"> be their age gap. Their mom means <img src="https://latex.codecogs.com/png.latex?A(t_0)%20=%20D(t_0+t)">, but D.W. thinks it means <img src="https://latex.codecogs.com/png.latex?A(T)%20=%20D(T)"> for some <img src="https://latex.codecogs.com/png.latex?T">, which is impossible because <img src="https://latex.codecogs.com/png.latex?A(T)%20-%20D(T)%20=%20t%20%5Cneq%200"> for all <img src="https://latex.codecogs.com/png.latex?T">.</p>
</section>
<section id="kinship" class="level1">
<h1>Kinship</h1>
<p>One more interesting observation is that languages can distinguish words for family members differently. You may or may not have realized this problem, but English’s inventory for family members is kind of limited for relatively prominent stuff.</p>
<p>“Uncle” and “aunt”, for example, can mean both someone who shares a very recent common ancestor with you (their parents are the same as your grandparents) or it can mean someone who was married in to your family. Also, it doesn’t encode whether they are your father or your mother’s siblings / sibling in laws.</p>
<p>Tamil has a LOT of distinctions, meanwhile. Its vocabulary for “uncle” and “aunt” encodes for additional features, such as whether they are an older or younger sibling, whether they are a blood relative or not, etc.</p>
<p>In <a href="https://www.naclo.org/resources/problems/2026/N2026-G.pdf">this NACLO problem</a>, you see just how different other languages express kinship.</p>
<details>
<summary>
Spoiler: Explains the main idea of the problem
</summary>
<p>Basically, the way talking about siblings works in Manam is quite different from “brother” or “sister”. There is one word for “younger sibling of opposite gender”, another word for “younger sibling of same gender”, and a third for “older sibling” (apart from “I” in the problem, which should be obvious). However, “younger” and “older” are also symmetrical for the purposes of this problem, so you could get the same solution by making the younger sibling the one that merges genders.</p>
</details>
</section>
<section id="number" class="level1">
<h1>Number</h1>
<p>A final note on how different languages perceive meanings is for number. As you know, English counts numbers using base 10 (decimal numbers). However, different languages use other bases, though they are less rare.</p>
<p>The most common example is French. Although it mostly uses base 10, there are still remnants of vigesimal counting (base 20) from the previous Celtic languages in modern-day France before Latin arrived, like Gaulish (if you’re interested, Asterix and Obelix is all about the Gauls resisting the Romans). To observe this, look at these numbers:</p>
<ul>
<li>19: dix-neuf (this is base 10, literally “ten nine”, similar to how English “nineteen” is connected to “nine ten”)</li>
<li>79: soixante dix-neuf (literally “sixty nineteen”)</li>
<li>80: quatre-vingt (literally “four twenty”, instead of English “eighty”, connected to “eight ten”, very vigesimal)</li>
<li>99: quatre-vingt dix-neuf (literally “four twenty nineteen”, this is full-on base 20)</li>
</ul>
<p>For larger digit numbers, it goes back to base 10 (hundreds, thousands, etc), and base 20 is only used for the last two digits sometimes.</p>
<p>Base 10 likely originated because people have 10 fingers to count, so base 20 means they used their toes to count as well.</p>
<p>There are other bases too (such as base 60 from the Babylonians, which is where we get 60 in time and angles from), but they are much more uncommon. Even base 20 is rarely seen anymore.</p>
</section>
<section id="semantic-drift" class="level1">
<h1>Semantic Drift</h1>
<p>Semantic drift is when the meaning of a word shifts over time. Looking at some common examples might illustrate this better.</p>
<section id="incredible" class="level2">
<h2 class="anchored" data-anchor-id="incredible">“Incredible”</h2>
<p>“Incredible” means something like “amazing” or “awesome”. You might realize that “credible” means “believable”, so “incredible” means “unbelievable”… right? Well, it used to!</p>
<p>Friend: “Yo bro, I just got a 5 on all my 31 AP exams this year!”</p>
<p>You: “Really? That’s incredible!”</p>
<p>Friend: “HOW DARE YOU SUGGEST THAT I CHEATED??? WE’RE NOT FRIENDS ANYMORE!!!”</p>
<p>Obviously, that won’t actually happen. Why? Because “incredible” has semantically drifted to mean something closer to “amazing” than “unbelievable”. It was used for things that were so good that it was almost hard to believe, but eventually it was only associated with those good things. What’s very cool is that this causes non-compositional meaning, because the meaning of “incredible” is no longer derived from “in” and “credible”.</p>
<p>Just for the record, I think the friend did cheat.</p>
</section>
<section id="semantic-bleaching-with-lol" class="level2">
<h2 class="anchored" data-anchor-id="semantic-bleaching-with-lol">Semantic Bleaching with “lol”</h2>
<p>Semantic drift can cause something similar to push or pull chains in sound changes, except for word meanings.</p>
<p>The abbreviation “lol” on the Internet technically means “laughing out loud”, but nowadays, no one uses it for extreme humor. It has evolved to mean very mild laughter. If someone says a very hilarious joke, and you simply reply “lol”, that might even be offensive because you didn’t find it that funny.</p>
<p>Therefore, people started adding profanity to intensify their humor. This is why “lol” got replaced with “lmao” (which I’m not gonna write out). However, after being used so much, even this got less intense in meaning. So, they just added even more bad stuff to humorous reactions to make it less mild.</p>
<p>This is why now people might elongate the “o” or they might do all caps or even add even worse curse words in the middle (like the voiceless labiodental fricative one) or just shift to other things entirely, like the skull emoji / “I’M DEAD” (which itself is quite dead now), “son i’m crine”, or who knows what else these days.</p>
<p>Semantic bleaching is when a word’s meaning gets less intense or “bleached” over time, so it causes replacements to be necessary.</p>
</section>
<section id="euphemism-with-bear" class="level2">
<h2 class="anchored" data-anchor-id="euphemism-with-bear">Euphemism with “bear”</h2>
<p>In Proto-Indo-European (which has been talked about a LOT in <a href="https://vaishnavs.net/posts/Historical-Linguistics-2/">my historical linguistics blog post</a>), the word for “bear” was *h₂ŕ̥tḱos. This is the ancestor to “ṛ́kṣa” in Sanskrit and “ursus” in Latin. Checks out so far, let’s try Greek - “arktos”. Cool, now, uh, let’s try the next common Indo-European language that most people use as examples - English. Wait, “bear”?</p>
<p>Yes, that’s right. Turns out, *h₂ŕ̥tḱos was one of the world’s oldest no-no words. In Proto-Germanic, the word for “bear” was *berô, meaning “the brown one”. Early Germanic people must have been terrified of bears, and they thought even saying the word for it would summon one. So, they used this euphemism instead.</p>
<p>Slavic languages have the same story, except their euphemism is “honey-eater” instead of “the brown one” (“medvedj” in Russian).</p>
</section>
</section>
<section id="mathematical-representation" class="level1">
<h1>Mathematical Representation</h1>
<p>One way for linguists to avoid ambiguity is to represent stuff using mathematical notation. Note in advance that most of this is common sense.</p>
<p>For example, take the “I can not do it” example. If we use “¬” to mean negation (as in flipping a boolean value), then the two meanings can be represented as can(¬do(x)) or ¬can(do(x)). Modal verbs like “can” in this case are kind of like functions. Here, x is a variable that can stand for any element that we’re interested in, and it behaves like the parameter for the inner function.</p>
<section id="feature-vectors" class="level2">
<h2 class="anchored" data-anchor-id="feature-vectors">Feature Vectors</h2>
<p>Just like how you can make a vector out of features for phonemes, you can do the same for meanings. For example, “king” can be represented as [+ human, + male, + royal, + adult], while “queen” can be represented as [+ human, - male, + royal, + adult], and “prince” can be represented as [+ human, + male, + royal, - adult]. The specific features depend on what you’re interesting in representing and contrasting, but this is the main idea.</p>
<p>Since all these features are binary, you can even represent them in an <img src="https://latex.codecogs.com/png.latex?n">-dimensional boolean cube.</p>
</section>
<section id="formal-semantics---truth-conditions-logic-and-set-theory" class="level2">
<h2 class="anchored" data-anchor-id="formal-semantics---truth-conditions-logic-and-set-theory">Formal Semantics - Truth Conditions, Logic, and Set Theory</h2>
<p>Truth conditions are basically a way to decompose a sentence into what conditions must make it true (kind of like necessary conditions). In the Minecraft Movie’s famous line “I… am STEVE”, the truth condition is that the speaker is Steve, so the set of all worlds where this speaker is Steve make this sentence true.</p>
<p>Now, if someone says “I like cats and dogs”, then the truth condition, because of the “and”, is the intersection of the set of all worlds where the speaker likes cats and the set of all worlds where the speaker likes dogs. If it was “or” instead, it would be the union of those two sets, but it could also be the union minus the intersection if it’s intended to not be both (basically “xor”).</p>
<p>Quantifiers are symbols for how many elements in a set are being talked about. For example, the universal quantifier (∀) means “all” or “every”, and the existential quantifier (∃) means “at least one” or “a”.</p>
<p>Truth conditions are kind of like checking if-statements in programming. Building on this, constructing the set of all worlds is a lot like list comprehensions, where you can filter out invalid worlds.</p>
<p>“Every student passed” would be written as ∀x (student(x) -&gt; passed(x)). Basically, x can be anything, and if it is a student, then it passed, due to the universal quantifier. This should hopefully illustrate how formal semantics works without a bunch of yapping.</p>
</section>
</section>
<section id="conclusion" class="level1">
<h1>Conclusion</h1>
<p>Now that you know how humans traditionally understand meanings, let’s learn about how machines understand them. Stay tuned for part 2!</p>
</section>
<section id="further-information" class="level1">
<h1>Further Information</h1>
<ul>
<li><p><a href="https://www.youtube.com/watch?v=6geQjY8b7sA">Crash Course Linguistics Episode 5: Semantics</a></p></li>
<li><p><a href="https://ocw.mit.edu/courses/24-900-introduction-to-linguistics-fall-2012/resources/mit24_900f12_semantics/">MIT OCW Introduction to Linguistics: Semantics</a> especially for formal and compositional semantics</p></li>
<li><p><a href="https://www.academypublication.com/issues/past/jltr/vol02/06/27.pdf">A Short Introduction to Semantics</a></p></li>
<li><p><a href="https://plato.stanford.edu/entries/frege/">Gottlob Frege</a></p></li>
<li><p><a href="https://plato.stanford.edu/entries/wittgenstein/">Ludwig Wittgenstein</a></p></li>
<li><p><a href="https://people.ucsc.edu/~panand/Courses/0607/SemanticsB/handout1.pdf">Truth-Conditional Semantics</a></p></li>
<li><p><a href="https://www.youtube.com/shorts/klWFJ_-kA6c">Etymology of “bear” from nardi</a></p></li>
<li><p><a href="https://philpapers.org/archive/HAZSCF.pdf">Sufficient Conditions for Counterfactual Transitivity and Antecedent Strengthening</a> more in depth for formal logic</p></li>
<li><p><a href="https://arthur.fandom.com/wiki/Arthur%27s_New_Year%27s_Eve/Transcript">The Arthur joke is from this episode</a></p></li>
</ul>


</section>

 ]]></description>
  <category>Linguistics</category>
  <category>Philosophy</category>
  <category>Math</category>
  <guid>https://vaishnavs.net/posts/Semantics/</guid>
  <pubDate>Sun, 02 Aug 2026 18:30:00 GMT</pubDate>
  <media:content url="https://vaishnavs.net/posts/Semantics/not_hot1.png" medium="image" type="image/png" height="74" width="144"/>
</item>
<item>
  <title>Craftic</title>
  <dc:creator>Vaishnav Sudarshan</dc:creator>
  <link>https://vaishnavs.net/posts/Craftic/</link>
  <description><![CDATA[ 





<section id="introduction" class="level1">
<h1>Introduction</h1>
<p>After I made my conlang <a href="https://vaishnavs.net/posts/Limit%20riLmOtOpU/">“Limit”</a> (which was kinda mid), and then planned out “Proto-Zorbbbb” (I’m working on it), I felt that I needed to make something better.</p>
<p>It’s probably not better because, (a) it’s based on <a href="https://neal.fun/infinite-craft/"><em>Infinite Craft</em></a> which everyone was obsessed with in 2023, and (b) it took like 5 minutes to make.</p>
<p>So, enjoy!</p>
</section>
<section id="craftic" class="level1">
<h1>Craftic</h1>
<p>“Craftic” is an exonym. The endonym is this:</p>
<p>satatatatatabuloqutabuloqoquloqutatabuloqutabulqoqoqutatatatabulqutabuloqoquloqutatabuloqutabuloqoqoqoqutabutatatabuloqutabuloqo quloqoqoqutatatatatatatabuloqutabuloqoquloqutatabuloqutabuloqoqoqutatatatabuloqutabuloqoquloqutatabuloqutabuloqoqoqoqutabutatata buloqutabuloqoquloqoqoqutatatatatabuloqutabuloqoquloqutatabuloqutabuloqoqoqutatatatabuloqutabuloqoqulqutatabuloqutabuloqoqoqoqoqe</p>
<section id="nouns-and-noun-phrases-derived-from-phonology" class="level2">
<h2 class="anchored" data-anchor-id="nouns-and-noun-phrases-derived-from-phonology">Nouns (and noun phrases) (derived from phonology)</h2>
<p>All nouns are derived from Infinite Craft. Note that phonemes have no extra allophones, and would just be pronounced like how they would if the same symbol was written in square brackets. Sound and written representation:</p>
<p>l (/ɬ/) = water</p>
<p>k (/ʞ/) = fire</p>
<p>m (/m/) = wind</p>
<p>b (/ʙ/) = earth</p>
<p>u (/y/) = plus</p>
<p>a (/a/) = start parentheses</p>
<p>q (/ħ/) = end parentheses</p>
<p>Each phoneme is also a morpheme, you’re welcome!</p>
<p>If there are any adjacent vowels, put a [t] between them, and if there are any adjacent consonants, put an [o] between them (very restrictive CV phonotactics). If a vowel starts a word, add a [ç], written as “s”, and if a consonant ends a word, add an [œ], written as “e”.</p>
<p>Parentheses are required for adding any units that aren’t fundamental.</p>
<p>There is communtative property symmetry, where both ways to put two things together are valid with the same meaning (so a non-one-to-one mapping).</p>
<p>Cloud = [Steam] + [Smoke] = [Water + Fire] + [Fire + Wind] = salukoqutakumoqe</p>
<p>Oh yeah, I should have mentioned that you’ll sound insane if you try to pronounce anything.</p>
<section id="actual-noun-orthography" class="level3">
<h3 class="anchored" data-anchor-id="actual-noun-orthography">Actual Noun Orthography</h3>
<p>An alphabet (top/down) is used in actual Craftic, the romanization is just for simplification. Here is the key:</p>
<p><a href="craftic_table.png" class="lightbox" data-gallery="quarto-lightbox-gallery-1" title="craftic orthography for nouns"><img src="https://vaishnavs.net/posts/Craftic/craftic_table.png" class="img-fluid" alt="craftic orthography for nouns"></a>.</p>
<p>As you can see, all the letters start and end with the same shape. This allows for a word to be transcribed without lifting your pen, so it is continuous (however, the curve is not differentiable because some letters contain sharp turns). [t] and [o], as well as [ç] and [œ], don’t have their own glyphs, because they can be inferred when you read it - the environments and the sounds are one to one. At the start of a word, the first letter should start with a stroke going up-right before writing its normal variant, and at the end of a word, the last letter should end with another up-right stroke after writing its normal variant.</p>
<p>This is what the word “cloud” (salukoqutakumoqe) looks like:</p>
<p><a href="craftic_cloud.png" class="lightbox" data-gallery="quarto-lightbox-gallery-2" title="“cloud” written in the Craftic orthography"><img src="https://vaishnavs.net/posts/Craftic/craftic_cloud.png" class="img-fluid" alt="“cloud” written in the Craftic orthography"></a>.</p>
</section>
</section>
<section id="verbs" class="level2">
<h2 class="anchored" data-anchor-id="verbs">Verbs</h2>
<p>All verbs must be expressed by actually doing them. If it is biologically impossible to do so, or you will get in trouble for doing so, then try your best to mimic the action by gesturing.</p>
<p>There are some agreed upon gestures that you shouldn’t make your own of. For example, if others have already established the precedent that the verb “punch” is represented by punching the listener’s face, you must also use that same gesture for that word.</p>
<p>However, if others haven’t yet invented the gesture for a certain word, you may take the opportunity to seize the “First Discovery”, like how it works in Infinite Craft, and invent your own gesture for it.</p>
<p>For orthographical purposes, all verbs are pictogram representations of what they mean, usually involving a stick figure as a placeholder for the subject. For example, the word “jump” is written as this: <a href="craftic_jump.png" class="lightbox" data-gallery="quarto-lightbox-gallery-3" title="craftic symbol for “jump”"><img src="https://vaishnavs.net/posts/Craftic/craftic_jump.png" class="img-fluid" alt="craftic symbol for “jump”"></a>.</p>
<p>What if there is an object? Craftic doesn’t actually distinguish between transitive and intransitive. Instead, if there is an object, it is treated as a subject, that accepts the verb “accepts”.</p>
</section>
<section id="adjectives-and-adverbs" class="level2">
<h2 class="anchored" data-anchor-id="adjectives-and-adverbs">Adjectives and Adverbs</h2>
<p>So, adjectives and adverbs on their own don’t really exist.</p>
<p>If a noun phrase involving an adjective exists in Infinite Craft (like “little red book”), then you can just use that as a noun.</p>
<p>Otherwise, just use a noun that the adjective is close to. For example, if you want to say “scary”, say “monster” instead. Once a speaker coins a new match, that is what sticks forever. Adverbs work very similarly. Instead of saying “quickly”, just say “cheetah”. Both come before the thing they modify.</p>
</section>
<section id="prepositions" class="level2">
<h2 class="anchored" data-anchor-id="prepositions">Prepositions</h2>
<p>Prepositions can’t really be expressed as words, but instead are shown through verbs.</p>
<p>“of” is expressed using “have”, “in” and “from” are expressed using “exist”, etc.</p>
</section>
<section id="general-syntax" class="level2">
<h2 class="anchored" data-anchor-id="general-syntax">General Syntax</h2>
<p>In speech, the verb gesture is performed at the same time as the subject, and is elongated for as long as it takes to finish pronouncing the subject.</p>
<p>In writing, the subject is written on the top, letters horizontal and left to right, then the verb is written underneath.</p>
<p>There aren’t technically any grammatical case markings. The accusative and dative cases are their own pair with the verb “accept”. The genitive case doesn’t really exist.</p>
<p>By the way, the symbol for “accept” is this:</p>
<p><a href="craftic_accept.png" class="lightbox" data-gallery="quarto-lightbox-gallery-4" title="craftic symbol for “accept”"><img src="https://vaishnavs.net/posts/Craftic/craftic_accept.png" class="img-fluid" alt="craftic symbol for “accept”"></a>.</p>
<p>For comparing A to B in quality X, just say “A X, B ! X”</p>
<p>This is what “my evil cat from France eats yummier food than the dog” would look like:</p>
<p>I have</p>
<p>Villain cat accept</p>
<p>Villain cat exist</p>
<p>France accept</p>
<p>Villain cat eat</p>
<p>(Ice cream) food accept</p>
<p>Dog eat</p>
<p>(Brussels sprouts) food accept</p>
</section>
</section>
<section id="conclusion" class="level1">
<h1>Conclusion</h1>
<p>Please feel free to roast Craftic in the comments.</p>


</section>

 ]]></description>
  <category>Linguistics</category>
  <guid>https://vaishnavs.net/posts/Craftic/</guid>
  <pubDate>Wed, 15 Jul 2026 18:30:00 GMT</pubDate>
  <media:content url="https://vaishnavs.net/posts/Craftic/craftic_jump.png" medium="image" type="image/png" height="164" width="144"/>
</item>
<item>
  <title>What is a Language?</title>
  <dc:creator>Vaishnav Sudarshan</dc:creator>
  <link>https://vaishnavs.net/posts/WhatIsALanguage/</link>
  <description><![CDATA[ 





<section id="what-makes-a-language" class="level1">
<h1>What makes a language?</h1>
<p>Since linguistics is the scientific study of language, you can’t really do that without knowing what a language is. A lot of this content will overlap with a field of linguistics called sociolinguistics, but this is more on the philosophical side.</p>
<p>Most people would agree that a language is a system to communicate with others.</p>
<p>Natural languages (natlangs) like English, French, Hindi, Korean, and Quechua are what most people think of when they think about languages, and they can express most things that the speakers find relevant, usually including abstract thought. Constructed languages (conlangs), like Klingon, Esperanto, Ithkuil, Toki Pona, and Sindarin, though they didn’t develop naturally, are typically able to do the same things.</p>
<section id="programming-languages" class="level2">
<h2 class="anchored" data-anchor-id="programming-languages">Programming languages</h2>
<p>What about programming languages? They allow people to directly communicate with computers (besides speaking in English to LLMs, which some view as a 5th generation programming language). You can tell the computer how to do a sorting algorithm (though you must give it every single detail, which is a constraint not really present in natural languages), but you can’t really ask it how the weather is, while using, say, Python. However, a computer doesn’t really communicate back to you, apart from maybe the program’s output (which still isn’t in that programming language), so it’s not really a language in the same sense as a natural language. It’s also kind of weird when sometimes, you’re telling the computer how to interact with another user. I think most people would agree that programming languages are, in some ways, languages.</p>
</section>
<section id="animals" class="level2">
<h2 class="anchored" data-anchor-id="animals">Animals</h2>
<p>And what about when a dog barks for different emotions, like if it doesn’t recognize someone or if it’s hungry? You might argue that it’s not, because the barking just points to whatever is going on, so the communication is dependent on whether the thing being talked about is physically present, which is not the point of language. However, barking could just be a very limited language, similar to how programming languages are also limited.</p>
</section>
<section id="dna-and-more" class="level2">
<h2 class="anchored" data-anchor-id="dna-and-more">DNA and more</h2>
<p>Would any sort of code also be a compiler for a language? For example, you could think of the genetic code as a way to translate every three nucleotides of DNA to a protein, and in that sense, DNA is almost like a programming language because it dictates what proteins to make. I’ll probably write a blog post about this in more detail in the future. There’s even a NACLO problem, <a href="https://www.naclo.org/resources/problems/2009/N2009-G.pdf">Sk8 Parsr</a>, about a “language” used to represent a video game.</p>
</section>
<section id="how-about-what-makes-different-languages" class="level2">
<h2 class="anchored" data-anchor-id="how-about-what-makes-different-languages">How about what makes different languages?</h2>
<p>The introduction of the book “The Art of Language Invention” by David J. Peterson goes over the different types of languages in a lot more depth. For the purposes of this blog post, I’m going to stick to natlangs, because that’s where most of the tension is (there isn’t much <em>physical</em> hostility between C and C++ users or anything).</p>
<p>Just getting a baseline definition of what a language is already causes so much disagreement, just wait until you argue about whether languages are distinct or not, which is what we’re going to talk about for the rest of this blog post.</p>
</section>
</section>
<section id="mutual-intelligibility" class="level1">
<h1>Mutual Intelligibility</h1>
<p>Usually, two languages are said to be the same language if they are <em>mutually intelligible</em>, which means speakers of one language can understand speakers of the other language for the most part. Since American and British English are similar enough to be mostly understood by each other, they’re considered the same language.</p>
<p>However, this has some problems. How intelligible is intelligible enough for two languages to be the same, and wouldn’t making such a line be subjective and arbitrary? Also, what intelligibility score would you use?</p>
<section id="lexical-similarity" class="level2">
<h2 class="anchored" data-anchor-id="lexical-similarity">Lexical Similarity</h2>
<p>For the second question, you might suggest using <em>lexical similarity</em>. This is when you take a large list of vocabulary between two languages, and find the percentage of vocabulary where both languages use cognates. However, lexical similarity can’t really dictate mutual intelligibility. For example, French and Italian have an 89% lexical similarity, but the words in common are pronounced very differently - “mangiare” and “manger”, both meaning “to eat”, might be unrecognizeable in speech. Another issue is that in writing, the vocabulary would be a lot more recognizeable, which might lead us to inconsistently group languages based on the medium they’re present in.</p>
</section>
<section id="understanding" class="level2">
<h2 class="anchored" data-anchor-id="understanding">Understanding</h2>
<p>Maybe instead of having a metric based on the language, you can have a metric based on individuals instead. If you take speakers of two languages, you can make them listen to a short story in the other language, and then quiz them on what happened. The main problem with this is that it’s hard to define what would make a good story to test speakers on. As a result, judging intelligibility is usually going to be a qualitative phenomenon, because there’s not a single good way to measure it quantitatively.</p>
</section>
<section id="asymmetric-intelligibility" class="level2">
<h2 class="anchored" data-anchor-id="asymmetric-intelligibility">Asymmetric Intelligibility</h2>
<p>There is also asymmetric mutual intelligibility. Danish sounds a lot different from Swedish and Norwegian, because its phonology is a lot more complex and it’s evolved differently. So, Danish speakers can understand Swedish and Norwegian speakers pretty well, because the grammar (apart from the phonology) is very similar, and the vocabulary is too. However, Swedish and Norwegian speakers cannot understand Danish speakers because they don’t understand their accent.</p>
<p>It’s a very similar situation for Portuguese and Spanish too, where it’s much easier for Portuguese speakers to understand Spanish than the other way around. Asymmetric mutual intellibility really points out a major flaw of using mutual intelligbility as a criteria for distinguishing languages. If Portuguese speakers understand Spanish but not the other way around, then you might say “Portuguese is the same language as Spanish” but “Spanish is not the same language as Portuguese”. However, that clearly doesn’t work out logically.</p>
</section>
<section id="ciphers" class="level2">
<h2 class="anchored" data-anchor-id="ciphers">Ciphers?</h2>
<p>As a side note, would Pig Latin be considered part of English or not? Pig Latin, if you didn’t know, is when you take each English word and apply a rule to it. If it starts with a vowel, you add “y” or “w” to the beginning, and then apply this next rule. If it starts with a consonant (all words at this point will), you move it to the end and add “ay” after that.</p>
<p>Technically, the lexical similarity is 100%, because all words from Pig Latin are derived from English. However, if someone is talking to you in Pig Latin, you’ll likely not understand anything they say unless you know or figure out the cipher. Linguists don’t really deal with ciphers that much, so they don’t need to worry about this problem, but mathematicians do, because it’s part of cryptography.</p>
</section>
<section id="dialect-continuums" class="level2">
<h2 class="anchored" data-anchor-id="dialect-continuums">Dialect Continuums</h2>
<p>Even if you do come up with a good enough way to measure mutual intelligibility, and you say whether any two languages are mutually intelligible or not, and therefore are the same language, that still leaves a giant issue.</p>
<p>Languages inherently have at least minor variation from one location to the next, because the people are different and therefore speak a different dialect (if you break it down further, it comes down to idiolects, which we’ll talk about soon).</p>
<p>A dialect is just the form of a language from a specific group of people, whether that is naturally based on geography (like Scottish vs.&nbsp;Nigerian English) or social groups (like brainrotted gen alphas vs.&nbsp;college professors). Everyone has a dialect, because everyone’s version of their language is slightly different.</p>
<p>Look at the Indo-Aryan languages. Sometimes they are classified under what Prakrit (once Sanskrit started evolving, it split up into Shaurasheni Prakrit, Magadhi Prakrit, and Maharashtri Prakrit) they evolved from, but it’s not really a clean divide like that, since they constantly have been in contact with each other. It’s more accurate to call them a dialect continuum.</p>
<p><a href="indo-aryan.png" class="lightbox" data-gallery="quarto-lightbox-gallery-1" title="This is how the Indo-Aryan languages are related"><img src="https://vaishnavs.net/posts/WhatIsALanguage/indo-aryan.png" class="img-fluid" alt="This is how the Indo-Aryan languages are related"></a>.</p>
<p>Note that adjecent points aren’t necessarily that mutually intelligible, because to draw a true dialect continuum where one point has no issue communicating with another point, the diagram would be very very very cluttered. However, you can still see how hard it is to define what a language is in this case. Here’s a bit more explanation.</p>
<p>Someone in Punjab will definitely understand someone from a neighboring village a little further East, and that person will be able to understand someone else from another village even more to the East, and so on, until you eventually get to Bangladesh. However, it’s clear that Punjabi and Bengali are not intelligible in the slightest. Adjacent villages speak the same language, according to the mutual intelligibility criterion. However, that would lead to the conclusion that Punjabi is the same language as Bengali, which, looking at their genetic relationship, is like saying French is the same language as Romanian - it’s simply not true. Therefore, the problem of dialect continuums hints at the idea that there must necessarily be some minor variation of language as it spreads across geography, and you can’t say that any two varieties are the same, identical language.</p>
</section>
<section id="language-evolution" class="level2">
<h2 class="anchored" data-anchor-id="language-evolution">Language Evolution</h2>
<p>Just as language varies across space, it also varies across time. For example, take this excerpt from the Old English text Beowulf:</p>
<p>“Hwæt. We Gardena in geardagum, þeodcyninga, þrym gefrunon, hu ða æþelingas ellen fremedon. Oft Scyld Scefing sceaþena þreatum, monegum mægþum, meodosetla ofteah, egsode eorlas. Syððan ærest wearð feasceaft funden, he þæs frofre gebad, weox under wolcnum, weorðmyndum þah, oðþæt him æghwylc þara ymbsittendra ofer hronrade hyran scolde, gomban gyldan. þæt wæs god cyning.”</p>
<p>If you’re a regular human being, and not some group of extraterrestrials that’s been spying on humanity ever since it built the pyramids of Giza, chances are that you have no idea what that just meant.</p>
<p>In modern English, here is the translation of that text:</p>
<p>“So. The Spear-Danes in days gone by and the kings who ruled them had courage and greatness. We have heard of those princes’ heroic campaigns. There was Shield Sheafson, scourge of many tribes, a wrecker of mead-benches, rampaging among foes. This terror of the hall-troops had come far. A foundling to start with, he would flourish later on as his powers waxed and his worth was proved. In the end each clan on the outlying coasts beyond the whale-road had to yield to him and began to pay tribute. That was one good king.”</p>
<p>This probably still doesn’t make much sense to you, unless you study extremely boring subjects too much, but the point is that at least you understand what most of the words mean, and the syntax makes sense to you.</p>
<p>Old English was VERY different from modern English. Its grammar was closer to modern German. Morphologically, both have three genders and four cases - much richer synthetic morphology than modern English, which is much more analytic (if you don’t know what that means, read my blog on <a href="https://vaishnavs.net/posts/Morphology">morphology</a>). Syntactically, Old English and German both have extra verbs go to the end of a sentence. For example, in German, “I must want to have a dog” is “Ich muss einen Hund haben wollen”, or literally, “I must a dog to have to want”, which would sound nonsensical to an English speaker. Similarly, Old English does the exact same thing.</p>
<p>So at what point did the language spoken in England stop being Old English and start being modern English? Kids of one generation always spoke just slightly differently from their parents, but they still had basically no problem communicating. Even when a bunch of vocabulary from Norman French was borrowed into English, it was pretty gradual, and parents would never have thought they were speaking a different language from their kids. There’s not a single line you can draw that says, “aha, anything spoken before this year must be Old English, and anything spoken <em>after</em> that year must be modern English!” Even if you define modern English to be however far back you can still understand, the problem remains that “understanding” isn’t a binary. Your language isn’t even 100% identical to that of your peers, and it’s not like Old English is 0% intelligible either, so defining a line is still arbitrary.</p>
</section>
</section>
<section id="role-of-politics-nationalism-and-standardization" class="level1">
<h1>Role of Politics, Nationalism, and Standardization</h1>
<p>Lots of times, countries have the need for a national identity so that they will remain unified. A really strong way to do this is to make all the citizens feel like they have the same culture, and that other countries have different cultures, and a really strong indicator of culture is language. So, if a country says “we are the sole speakers of this language, and this other country speaks a separate language”, then their national identity will likely be much stronger.</p>
<p>One example of this is how Hindi and Urdu are considered separate languages today. When India and Pakistan split, they both wanted to have a secondary national language apart from English. Hindi and Urdu are both just varieties of the larger <a href="https://en.wikipedia.org/wiki/Hindustani_language">Hindustani</a> dialect continuum (it’s sometimes considered a single language too - I know this entire blog post is about how defining what makes a language distinct is very hard, but their spoken forms are much closer than, say, Canadian and Senegalese French, which are considered a single language).</p>
<p>Hindustani as a dialect continuum existed before the partition of India and Pakistan and was spread out on both sides of the modern border. So, if you ignore politics, there shouldn’t be any reason to say that the language spoken one millimeter into the Indian side is the same language as the one spoken way way way inland, but it’s a different language from the one spoken one millimeter into the Pakistani side.</p>
<p>Hindi and Urdu are basically mutually intelligible colloquially, but their formal written forms are very different - for one, they use completely different orthographies, so the speaker of one can’t read a single word of the other.</p>
<p>Standardization allows for national languages to make themselves distinct. Formal Hindi, which is emphasized in Indian schools, takes a lot more modern borrowings from Sanskrit vocabulary, while formal Urdu, which is emphasized in Pakistani schools, has a lot more Persian and Arabic loanwords. So, while speakers of either language can understand each other when speaking colloquially, their respective governments tried to make the standard forms diverge more.</p>
</section>
<section id="idiolects-and-code-switching" class="level1">
<h1>Idiolects and Code-Switching</h1>
<p>Right now, we’ve seen how languages can differ through space and time. However, it can also vary at an individual level too.</p>
<section id="variation-among-individuals" class="level2">
<h2 class="anchored" data-anchor-id="variation-among-individuals">Variation among individuals</h2>
<p>Even people who are very close have some differences in their internal grammars.</p>
<p>For example, me and my sister disagree on what the answer to this question is:</p>
<p>The group of aliens (was/were) evil.</p>
<p>I say “was”, because I reduce the entire noun phrase to just “group” (which means I have an advantage for the SAT because my brain works similarly to that of the prescriptivists), but my sister says “were”, because she sees “aliens” next to “were”.</p>
<p>Despite adhering to the rules of standard English decently well, I also differ from it. Usually, you’re expected to say “if I were to”. However, my internal rules say that “I” and “were” can’t go together unless the “I” is part of something plural, which in this case it is not. Standard English suggests that the rule for making the subjunctive overrides a singular going with “were”, but for me, a singular can never go with “were” no matter what, and this overrides any other rules. This gets into something called Optimality Theory, which may be a future blog post.</p>
<p>This just goes to show that because everyone’s brain works slightly differently, their internal grammars differ as well. Each individual’s way of speaking is called an <em>idiolect</em>.</p>
</section>
<section id="variation-within-individuals" class="level2">
<h2 class="anchored" data-anchor-id="variation-within-individuals">Variation within individuals</h2>
<p>One person can also have many different ways of speaking within themself. If you’re talking to your friends, it might be ok to omit the copula and say, “whatcha doing”, which without the palatalization sandhi is “what ya doing”. However, in a professional environment, you’re expected to say “what are you doing”. This is quite literally a different set of phonological and morphosyntactic rules, albeit very similar. So, you could say that these are different languages, because, as we’ve seen, it’s very hard to draw a line for how similar two sets of rules must be to say they’re the same language.</p>
<p>The practice of changing the way you speak depending on the context is called <em>code switching</em>.</p>
</section>
</section>
<section id="my-own-solution" class="level1">
<h1>My own solution</h1>
<p>So, we’ve seen the complications of defining and distinguishing languages, and it’s still not entirely agreed on by linguists. So, let’s see how I personally solve this dillema.</p>
<p>I think that everyone has their own languages that just overlap similarly enough to be able to communicate. There’s no point in asking if my English is the same as your English, because the answer will always be no. Even if we understand each other perfectly, because our differing rules won’t necessasrily take away from understanding, we both may still have a different idea of what certain words refer to exactly. This distorts the meaning by a nonzero amount, but usually the meaning being distorted isn’t the main point being made, so it doesn’t matter. Defining English is like defining a game, because it could be a family resemblance (for more information, read my upcoming semantics blog) - instead of a single unifying feature, it’s just a network of languages that have close connections to some of the others, but not all.</p>
<p>Your own language is also continuously changing - for example, you can say the same word over and over again, and there will always be very slight phonetic differences, since frequency is a real number, not a discrete quantity like rules, so it’s nearly impossible to replicate exactly. Obviously, this is a terrible and nitpicky example. A better example is how your language always gets shaped by other people. When I was new to Discord, I used to always use the actual laughing emoji to indicate that something was funny, but then I saw that others used the skull emoji in that same context, so I started to use that instead.</p>
<p>Mutual intelligibility is relative. Even though that there’s not a specific metric that can perfectly quantify it, people can generally tell how well they understand other languages. It’s definitely not a binary - even though you might understand 0% or 100% of some text, these are just the extreme cases.</p>
<p>The specific language that someone speaks is a function of them, their audience, and the occasion. Obviously, a language can’t just be based on a single person, because the point of it is to communicate with someone else. Even if you speak multiple “different” languages (as in, not thought of as English, and very little intelligibility, such as French), your brain still can choose this - you’ll only speak French to another person who knows French, but you probably won’t speak it to a random person in the USA who may or may not know French. And maybe if in the exact same occasion and audience, you could speak in two different ways (like speaking to someone in your French class in English, because they can converse with you in either), the way of choosing this is more conscious than subconscious, but maybe you can consider the conscious decision as part of the occasion too.</p>
<p>If everyone speaks multiple languages, then how do you define multilingualism? I’d say that for most people who only speak a variety of English, the differences are too negligible to say that you speak 50 languages. When accounting for code switching, you should only count changes that alone are unintelligible. So, the total languages I speak between my sister and my friends would only be 1.001 or something very close to 1, because only a small amount of vocabulary, pronunciation, and grammar is different. Now, if I hypothetically speak only standard English and standard Chinese, that should count as almost 2 languages, maybe 1.998, because Chinese and English have almost no vocabulary in common (shared word order shouldn’t really count for intelligibility if none of the vocabluary or genetic relationship is common), apart from the very few loanwords that exist. If I speak hypothetically only standard English and standard German, that would maybe be 1.7 languages or something like that.</p>
<p>There must in theory be some metric to measure mutual intelligibility that can fit this criteria, even if it’s hard to actually compute. I think this really is the problem with distinguishing languages. If there is a real, objective score for saying how different two languages are, then our problem is solved! However, for now, this is still based on vibes, so we can only say that they are not the same language.</p>
</section>
<section id="conclusion" class="level1">
<h1>Conclusion</h1>
<p>As you can see, there are many complications when it comes to defining a language. If you disagree with my solution to this issue (which you likely will), please write your interpretation in the comments, because different opinions will be very cool.</p>


</section>

 ]]></description>
  <category>Linguistics</category>
  <category>Philosophy</category>
  <guid>https://vaishnavs.net/posts/WhatIsALanguage/</guid>
  <pubDate>Sat, 11 Jul 2026 18:30:00 GMT</pubDate>
  <media:content url="https://vaishnavs.net/posts/WhatIsALanguage/indo-aryan.png" medium="image" type="image/png" height="95" width="144"/>
</item>
<item>
  <title>SLIYS - a linguistics summer program for high schoolers</title>
  <dc:creator>Vaishnav Sudarshan</dc:creator>
  <link>https://vaishnavs.net/posts/SLIYS/</link>
  <description><![CDATA[ 





<section id="linguistics-in-high-school" class="level1">
<h1>Linguistics in High School</h1>
<p>If you’re in high school and you are interested in linguistics, chances are that your opportunities are pretty limited. The major thing you can do is take the North American Computational Linguistics Open (<a href="https://naclo.org/">NACLO</a>). However, the entire contest is built around the fact that most high schoolers don’t have background linguistics knowledge, which is why the problems are based on logic and puzzle solving rather than linguistic theory.</p>
<p>While I find language puzzles to be very fun, and they do sometimes teach you certain concepts in linguistics, they still don’t replace actually learning linguistics. It’s kind of like the difference between sudoku and algebra.</p>
<p>During 8th and 9th grade, I learned linguistics through a combination of YouTube, Wikipedia, ChatGPT, Discord, and books - it’s ok but not that good compared to learning it formally.</p>
</section>
<section id="sliys" class="level1">
<h1>SLIYS</h1>
<p>That’s why I was thrilled to learn that every summer, the Ohio State University hosts a program called <a href="https://linguistics.osu.edu/undergrad/sliys">SLIYS</a> (Summer Linguistics Institute for Youth Scholars) that actually formally teaches you the basics of linguistics. They have two one-week online sessions - SLIYS 1 and SLIYS 2, which are more introductory and more in-depth respectively. You have to take SLIYS 1 in order to be eligible to take SLIYS 2 later on. Sadly, I was only able to take SLIYS 1 this summer, because I had a schedule conflict during SLIYS 2, but I hope to take it next year.</p>
<section id="content" class="level2">
<h2 class="anchored" data-anchor-id="content">Content</h2>
<p>I was surprised that even for topics that I was sure I knew pretty well, I still ended up learning some new and interesting facts.</p>
<ul>
<li><p>Phonetics: This is split into first consonants, then vowels. For both, you learn the main features that are relevant in languages - voicing, place of articulation, and manner of articulation for consonants, and rounding, high/low, and front/back for vowels. However, I didn’t know that there is also an independent distinction (can’t be written in terms of the other three) for tense and lax vowels.</p></li>
<li><p>Sociolinguistics: You learn all about language variation, which is very interesting. It also clears up a lot of misconceptions that people who don’t know about linguistics have, such as “I speak proper English, and everyone else speaks a dialect”. One of the home labs (basically optional homework) was to watch a documentary called “Talking Black in America”, which was very interesting.</p></li>
<li><p>Morphology: You learn about the difficulty in defining makes a morpheme (is raspberry a single morpheme, or is “rasp” somehow a morpheme?) as well as different types of morphology across languages (using a decision tree to determine what type of morphology a language has is pretty cool).</p></li>
<li><p>Syntax: You write rules for what sentences are valid, and you also make syntax trees.</p></li>
<li><p>Historical Linguistics: You learn about language change, including sound changes, but also morphology changes, which I didn’t know before.</p></li>
</ul>
</section>
<section id="elicitation" class="level2">
<h2 class="anchored" data-anchor-id="elicitation">Elicitation</h2>
<p>Apart from the lectures at SLIYS, one of the most fun parts is the language eliciation sessions. Basically, you get put into a language group with some other students, most likely a language you know almost nothing about. At the end of each day, you get to ask a native speaker of that language how to translate whatever phrases you want, and then you transcribe it into the IPA, with the goal of collecting and explaining data about the language. However, you can’t ask about grammatical features directly - you can only ask for translations and figure it out yourself. Luckily, it’s really easy to ask for minimal pair sentences to see what’s going on.</p>
<p>I got placed in Thai. Transcribing it was very hard at first, because my puny English and Tamil speaking brain couldn’t handle the tones and weird vowels I’d never heard before. However, once we figured that out, the morphology and syntax were super easy, and pretty cool as well. At the end of it, I was able to speak basic sentences in Thai (technically, infinite sentences because we figured out recursion, which works the same way as it does in English).</p>
</section>
<section id="panel-discussion" class="level2">
<h2 class="anchored" data-anchor-id="panel-discussion">Panel Discussion</h2>
<p>On the last day, we were able to ask questions to PhD and research students working in linguistics academia, and it was very cool to see what linguists actually do these days.</p>
</section>
</section>
<section id="conclusion" class="level1">
<h1>Conclusion</h1>
<p>Overall, SLIYS is an extremely unique opportunity that you get in high school to learn and do linguistics, and I’d strongly recommend that you <a href="https://linguistics.osu.edu/undergrad/sliys/sliys-how-apply">participate in it</a> if you want to learn more about the field.</p>
<p>Thank you to my instructors, Lindon Dedvukaj, Kyler Laycock, Angelica Aviles Bosques, and Ellie Wren-Hardin!</p>


</section>

 ]]></description>
  <category>Linguistics</category>
  <category>Random</category>
  <guid>https://vaishnavs.net/posts/SLIYS/</guid>
  <pubDate>Thu, 09 Jul 2026 18:30:00 GMT</pubDate>
</item>
<item>
  <title>Historical Linguistics Part 2: Language Evolution, The Comparative Method and Language Families</title>
  <dc:creator>Vaishnav Sudarshan</dc:creator>
  <link>https://vaishnavs.net/posts/Historical-Linguistics-2/</link>
  <description><![CDATA[ 





<section id="introduction" class="level1">
<h1>Introduction</h1>
<p>Imagine you see the following Romanized words for “three” in a bunch of different languages:</p>
<table class="caption-top table">
<thead>
<tr class="header">
<th>Language</th>
<th>Word for “three”</th>
<th>IPA</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>English</td>
<td>three</td>
<td>[θɹiː]</td>
</tr>
<tr class="even">
<td>German</td>
<td>drei</td>
<td>[dʁaɪ]</td>
</tr>
<tr class="odd">
<td>Swedish</td>
<td>tre</td>
<td>[tɾe]</td>
</tr>
<tr class="even">
<td>Latin</td>
<td>trēs</td>
<td>[ˈtreːs]</td>
</tr>
<tr class="odd">
<td>French</td>
<td>trois</td>
<td>[tʁwa]</td>
</tr>
<tr class="even">
<td>Sanskrit</td>
<td>tráyas</td>
<td>[ˈtr̩ajəs]</td>
</tr>
<tr class="odd">
<td>Romani</td>
<td>trin</td>
<td>[tɾin]</td>
</tr>
<tr class="even">
<td>Bengali</td>
<td>tin</td>
<td>[tɪn]</td>
</tr>
<tr class="odd">
<td>Tajik</td>
<td>se</td>
<td>[se]</td>
</tr>
<tr class="even">
<td>Ancient Greek</td>
<td>treîs</td>
<td>[treːs]</td>
</tr>
<tr class="odd">
<td>Russian</td>
<td>tri</td>
<td>[trʲi]</td>
</tr>
<tr class="even">
<td>Polish</td>
<td>trzy</td>
<td>[tʂɨ]</td>
</tr>
<tr class="odd">
<td>Irish</td>
<td>trí</td>
<td>[tɾʲiː]</td>
</tr>
</tbody>
</table>
<p>Most of these look very similar. They are definitely not just loanwords, because this would also be very crazy historically - a lot of these languages never even contacted each other, or had a chain of subsequent borrowings. Additionally, loanwords would have to fit the phonology of the language borrowing them, but those aren’t the sound changes that happened. Loanwords are typically also not for core, fundamental cultural concepts like numbers, but rather some idea the speakers didn’t have access to before.</p>
<p>This means that these words must be related, which means they come from a common ancestor language that split and diverged into all of these different languages.</p>
<p>A simpler, more tangible example is the Romance languages, which most people know come from Latin. For example, the word for “three” in Spanish is “tres”, in Italian is “tre”, in French is “trois”, and in Romanian is “trei”. These are all very similar, and they all come from the Latin word “trēs”. As Latin speakers spread out, their forms and pronounciations changed over time.</p>
<p>Now, you wonder what the common ancestor word for “three” even is. However, this feels like a question that is way too open-ended just by looking at the words, because with enough creativity or weirdness, you could probably evolve any word into any other word. For example, here is “proof” that “hello” comes from “vanakkam”:</p>
<p>However, there is a certain technique that is used to reconstruct many such ancestor words to a pretty confident degree of accuracy, called the comparative method. And if you had many more words and many more languages, you could even be able to reconstruct the entire ancestor language and even understand a bit about the culture of its speakers. By the way, the answer is *tréyes.</p>
<section id="proto-languages" class="level2">
<h2 class="anchored" data-anchor-id="proto-languages">Proto-Languages</h2>
<p>So, what is this kind of language that all these words come from? It is called a proto-language, which means it has never been directly observed in speech or writing, but instead was reconstructed by linguists using the comparative method. While its grammar and vocabulary aren’t necessarily 100% correct, because no one knows its exact form, its existence is almost guaranteed since it was able to be fully reconstructed.</p>
<p>In this case, this language is called Proto-Indo-European. It is estimated to have been spoken around 6000 years ago in the Eurasian Steppe.</p>
<p>The name of a language family, which is a group of languages that are all related to each other, usually shares a name with that of the proto-language. For example, the Indo-European language family descends from Proto-Indo-European, and the Dravidian language family descends from Proto-Dravidian.</p>
<p>Proto-languages can also be the ancient, reconstructed ancestor of any group of languages, not just the whole family. For example, the ancestor of all Germanic languages, like English, German, and Swedish, is called Proto-Germanic.</p>
<p>Another strange example is of the Romance languages. Even though we know they are all descended from Latin, there is still a proto-language called Proto-Romance, which is in between the Latin spoken by the elites in the Roman Empire and the modern Romance languages. It’s obtained using the comparative method on all the living Romance languages to find the most recent common ancestor. So, proto-languages can even be spoken after a known, recorded language.</p>
</section>
</section>
<section id="the-comparative-method-and-backtracking-sound-changes" class="level1">
<h1>The Comparative Method and Backtracking Sound Changes</h1>
<p>I’ve mentioned that the comparative method is how linguists reconstruct proto-languages, but how does it work?</p>
<p>An important fact is that sound changes are regular, so typically, a certain rule like “a [k] sound turns into an [h] sound” will apply to all words in a language, and not just some of them. This is what allows us to backtrack sound changes, which is the main technique used in the comparative method. This, by the way, was one of the sound changes from Grimm’s Law, which I talked about in the previous post.</p>
<p>As a fun note, you can also find out timelines using sound changes. For example, in Arabic, there was a sound change where [p] turned into [f], and this time period is known. Nowadays, since the [p] sound doesn’t exist, speakers might borrow words with that sound but pronounce it like a [b]. So, if an Arabic loanword is pronounced as [b] while other languages pronounce that same word with a [p], then we know that this word was borrowed after the sound change, because if it was borrowed before, then it would be pronounced as an [f] instead. Since Arabic speakers have inhabited Palestine for a long time, they pronounce it as “filastin”, while newer concepts to Arabic speakers, like “pizza”, are pronounced as “bizza”.</p>
<p>Also, the Indo-European languages are usually classified into “centum” (Latin) or “satem” (Avestan), based on the first consonant in their word for “hundred”. The Indo-Iranian, Armenian, and Balto-Slavic languages underwent a sound change where the *ḱ was pronounced as [s]. The Italic, Hellenic, and Celtic languages have the first consonant in “hundred” pronounced like [k], so we know that they split off before that sound change happened (there’s not any known sound change that would have brought the [s] back to the [k], otherwise). The Germanic languages are where we have to apply multiple sound laws. The first consonant in “hundred” (or “Hundert” in German) is pronounced as [h]. There is no law changing [s] to [h] for Germanic languages (but this does exist for Iranian languages). However, Grimm’s Law does bring *k to [h]. Therefore, we can conclude that the Germanic languages split off before the sound change that shaped the satem languages.</p>
<p>Here is a diagram showing how the word for “hundred” evolved through the different Indo-European languages. This is a much smaller diagram, only showing a few selected branches and languages. It also points out some of the notable sound changes.</p>
<div class="cell" data-layout-align="default">
<div class="cell-output-display">
<div>
<p></p><figure class="figure"><p></p>
<div>
<pre class="mermaid mermaid-js">%%{init: {
  "theme": "base",
  "themeVariables": {
    "fontSize": "60px"
  }
}}%%

graph TD

PIE["PIE: *ḱm̥tóm"]

PIE --&gt; Centum["Centum Languages"]
PIE --&gt;|"*k → s"| Satem["Satem Languages"]

Satem --&gt; PBS["Proto-Balto-Slavic: *śimtas"]
Satem --&gt; PII["Proto-Indo-Iranian: *ćatám"]

PII --&gt; Iranian
Iranian --&gt; Avestan["Avestan: satem"]

PII --&gt; IndoAryan["Indo-Aryan"]
IndoAryan --&gt; Sanskrit["Sanskrit: śatam"]

PBS --&gt; Baltic
PBS --&gt; Slavic

Baltic --&gt; Lithuanian["Lithuanian: šimtas"]
Slavic --&gt; Russian["Russian: sto"]

Centum --&gt; Italic
Centum --&gt; Germanic

Italic --&gt; Latin["Latin: centum"]
Latin --&gt;|"*k → s"| Spanish["Spanish: cien"]

Germanic --&gt;|"*k → h"| PG["Proto-Germanic: *hundą"]
PG --&gt; English["English: hundred"]

%% PIE styling (green root node)
classDef pie fill:#7CFC90,stroke:#1B5E20,stroke-width:4px,color:#000,font-size:26px;

%% Centum (blue branch)
classDef centum fill:#CFE8FF,stroke:#1565C0,stroke-width:4px,color:#000,font-size:26px;

%% Satem (red branch)
classDef satem fill:#FFD6D6,stroke:#C62828,stroke-width:4px,color:#000,font-size:26px;

class PIE pie;

class Centum,Italic,Germanic,Latin,Spanish,PG,English centum;

class Satem,PBS,PII,Iranian,Avestan,IndoAryan,Sanskrit,Baltic,Slavic,Lithuanian,Russian satem;

%% thick links
linkStyle default stroke-width:5px;
</pre>
</div>
<p></p></figure><p></p>
</div>
</div>
</div>
<p>Note that the Romance languages, descended from Latin, pronounced it as [s], not [k] - it’s coincidentally the same sound change that caused the centum-satem split, but it happened much later. Additionally, the satem languages don’t necessarily pronounce the first consonant as exactly [s], but it is generally a voiceless fricative in around that area, like [ʃ] for instance.</p>
<p>Some sound changes are much more likely to occur than others. For example, it’s much more likely for a /t/ sound to turn into a /tʃ/ sound if it’s near an /i/ or a /j/ sound, than if it is near an /o/ or an /a/ sound, because of a trend called palatalization. Also, /t/ probably won’t turn into a /ɬ/ near an /i/ or a /j/. This is how the Latin word “leite” turned into the Spanish word “leche”.</p>
<p>Typically, simplifications or reductions won’t be reversed, because that information is gone. This is why the word “eau” in French won’t turn back into “aqua” in Latin, because a lot of information was lost, so if we know that either French or Latin is the ancestor of the other, we can tell that Latin is the ancestor of French. If a sound change causes a sound to be added, it’s most likely due to the language’s phonotactics changing - for example, in Latin, the beginning consonant cluster “st” (like in “studere”, meaning “to study”) was allowed, but in Spanish, it wasn’t, so an “e” was added to the beginning to make it “estudiar”.</p>
<p>Looking for corresponding phonemes cross-linguistically and across many cognates is an important step. For example, if you look across Tamil, Telugu, and Kannada to try an reconstruct Proto-South-Dravidian (a descendant of Proto-Dravidian), you might notice that wherever Telugu and Kannada end in a /u/, Tamil reduces this final vowel and turns it into the null phoneme, /∅/.</p>
<p>Then, you try to figure out which sound change is the most likely to have happened, which kind of feels like a pretty hard puzzle. With enough data, you can reconstruct common vocabulary for the ancestor language without any logical contradictions.</p>
<p>Sometimes there are multiple possible reconstructions. Since they are all valid from the data alone, you need to rely on other tools to determine which is better, like how relatively likely the sound changes are cross-linguistically, or how many exceptions your rules have.</p>
<section id="figuring-out-the-culture-of-the-speakers" class="level2">
<h2 class="anchored" data-anchor-id="figuring-out-the-culture-of-the-speakers">Figuring out the culture of the speakers</h2>
<p>Reconstructions from cognates can tell us a lot how the speakers lived. For example, across the Indo-European languages, there are cognates for “wheel”, like “cyclos” (related to “cycle”) in Greek, “chakra” in Sanskrit, and the word “wheel” itself. The reconstructed word is *kʷékʷlos in Proto-Indo-European. While it’s possible that semantic drift happened, and the original word meant something else, it’s pretty unlikely, since that would imply that the exact same drift happened in every single Indo-European language, which is nearly impossible. Also, there are reconstructed words for many other transportation technology related vocabulary as well, like “axle”. So, the Proto-Indo-European speakers, at least at some point, probably had wheels.</p>
<p>One extra detail is that Anatolian languages did NOT have a word for wheel that was related to the other Indo-European words for “wheel”. Anatolian languages were discovered after Proto-Indo-European was already reconstructed using non-Anatolian languages. Therefore, many people believe that that the Anatolian languages (like Hittite or Luwian) split off from Proto-Indo-European the earliest before Indo-European speakers had access to wheels. This is why some linguists prefer to call the language that gave rise to both Proto-Anatolian and the other Indo-European branches as Proto-Indo-Anatolian, having Proto-Indo-European refer solely to the ancestor of non-Anatolian Indo-European languages. However, it’s possible that Anatolian just obtained a different word for “wheel” from some other origin, but its ancestral speakers always had wheels.</p>
<p>This works for mythology too. The word “Zeus” is the shortened form of “Zeus Pater”, meaning “Sky Father” in Greek. The Latin word “Jupiter”, representing the same god, also means the same and is etymologically related to it. Even the Hindu sky god Indra’s father’s name was “Dyaus Pitar”, again meaning the same thing. The Norse god “Tyr” is also derived from the same root for “sky”. So, the Proto-Indo-European speakers probably had a sky father god as well, whose reconstructed name was “*Dyēus Phtḗr”.</p>
</section>
<section id="representing-sound-changes" class="level2">
<h2 class="anchored" data-anchor-id="representing-sound-changes">Representing Sound Changes</h2>
<p>We can represent sound changes by writing the original and altered pronunciation of a sound, and also including the environment where the change takes place. This looks pretty similar to representing the allophonic variation of a phoneme.</p>
<p>For example, Proto-Dravidian had a *k before unbacked vowels. In Tamil, this sometimes changed to a c (pronounced as [s]) if the consonant after the unbacked vowel wasn’t retroflex.</p>
<p>We can represent this as the following rule:</p>
<p>*k –&gt; c / _ V[-BACKED] C[-RETROFLEX]</p>
</section>
</section>
<section id="order-of-sound-changes" class="level1">
<h1>Order of sound changes</h1>
<p>If you have multiple sound changes, the order in which they take place matters a lot. For a very simple example, take these two hypothetical sound changes:</p>
<p>Suppose that in Proto-X, the word for “cat” is *zop.</p>
<p>To get that word in the modern language X (zombe), we know there are three sound changes that happened:</p>
<ol type="1">
<li>Final voiceless stops become voiced (zob).</li>
<li>Final voiced stops have an “e” added after them (zobe).</li>
<li>Vowels before voiced stops have a nasal added right after them (zombe).</li>
</ol>
<p>Now, see what happens if we put 2, then 3, then 1:</p>
<p>First, no change, because the final consonant isn’t voiced. Second, no change, because there is no vowel before a voiced stop. Third, the final consonant becomes voiced, so the word is “zob”.</p>
<p>Thus, due to the nature of conditionals in sound changes, changing the order of sound changes can lead to different outcomes. In this sense, finding the right order is heavily reliant on logic.</p>
<p>It’s not always true that the order of sound changes matters, if the sound changes are independent of each other and can only build on each other, not mutually interfering. For example, if you start with the single-sound word *ɸ, you can have these sound changes, and all 5040 rearrangements of them will lead to the same resultant word, udʱ:a.</p>
<ol type="1">
<li>fricatives become stops</li>
<li>voiceless consonants become voiced</li>
<li>unaspirated consonants become aspirated</li>
<li>ungeminated consonants become geminated</li>
<li>add an “a” after all consonants</li>
<li>add a “u” before all consonants</li>
<li>bilabial consonants become alveolar</li>
</ol>
<p>There is a really easy NACLO problem exactly like this called <a href="https://www.naclo.org/resources/problems/2007/N2007-G.pdf">Rewrite me badd</a>, except it is for a real language.</p>
</section>
<section id="pushpull-chains" class="level1">
<h1>Push/Pull Chains</h1>
<p>Sometimes, if a sound change pushes one sound into another existing sound, then that sound will turn into another sound to maintain the distinction, and so on. This is called a push chain.</p>
<p>An example of this is the Great Vowel Shift in English. /e:/ (beet) and /o:/ (boot) sounded more like /i:/ and /u:/, so /i:/ (time) and /u:/ (house) sounded more like /aɪ/ and /aʊ/.</p>
<p>The reverse may also happen. If a sound change turns into another sound that didn’t exist before, then the previous sound is unused, so another sound may turn into that, and so on, and this is called a pull chain.</p>
</section>
<section id="common-sound-changes" class="level1">
<h1>Common Sound Changes</h1>
<p>Here are the most common types of sound changes:</p>
<ul>
<li>Assimilation: A sound becomes more like its neighbors, like “octo” in Latin turning into “otto” in Italian (the /k/ became a /t/)</li>
<li>Dissimilation: A sound tries to contrast with its neighbors more (like saying “February” as “Febyuary”)</li>
<li>Insertion: A sound must be added to make the word easier to say (like “something” ocassionally having a [p] between the /m/ and /θ/)</li>
<li>Deletion: A sound disappears (the /k/ in “knight” actually used to be pronounced)</li>
<li>Metathesis: Two sounds get replaced (like how my sister once said “can we please stop having this conservation” instead of “conversation”)</li>
<li>Strengthening: A sound becomes more like a consonant (some people pronounce “this” as “dis” because stops are more consonant-like than fricatives)</li>
<li>Weakening: A sound becomes more like a vowel (Grimm’s law where stops became fricatives)</li>
</ul>
</section>
<section id="analogy-and-morphological-change" class="level1">
<h1>Analogy and Morphological Change</h1>
<p>Sometimes, analogies cause speakers to change a language’s morphology and make it more regular. I’ve seen this happening to my sister. Often, she says “drinked” and “hurted” for past tense instead of “drank” and “hurt”. In fact, relatively less common words are more likely to be regularized by analogy, because speakers are less likely to interact with all the irregularity. This is why you’ll never find my sister saying “eated” or “haved”.</p>
</section>
<section id="proving-language-relationships" class="level1">
<h1>Proving Language Relationships</h1>
<p>At first, we don’t know for sure if languages are related or not. One of the most reliable ways to prove that they are related is to try and reconstruct a proto-language including that language, and see if it can be done completely and without much of a stretch.</p>
<p>This isn’t always a simple yes or no. The Niger-Congo family is hypothesized to link the Atlantic-Congo and Mande language families. Although Proto-Niger-Congo has not been reconstructed apart from some vocabulary, the theory is still relatively strongly believed in.</p>
<p>Some people who weren’t quite linguists, such as Nicolaes Witsen and Philip Johan von Strahlenberg, believed that the Turkic, Mongolic, and Tungusic languages (Manchu, the language of the early part of the Qing Dynasty, is a Tungusic language) were all part of the same language family, a hypothetical Altaic family. The philologist Matthias Castrén even went so far as to add the Uralic languages as a separate branch too. The mainstream pro-Altaic view sometimes added Japonic and Koreanic languages (mainly Japanese and Korean respectively, but they have smaller languages too) to the proposed family as well, making it the Macro-Altaic hypothesis.</p>
<p>The basis in this theory was mainly due to similarities in grammar, like how they all had agglutinative morphology and SOV word order. They did have some shared vocabulary that appeared to be basic, like body parts. However, there was simply just not enough data to reconstruct a proto-language. Therefore, the Altaic hypothesis was not proven. Some linguists argue that technically, all languages, even English and Chinese, could be related, but we just have no way of knowing since they have diverged so much.</p>
</section>
<section id="sprachbunds" class="level1">
<h1>Sprachbunds</h1>
<p>In fact, there is a much more convincing explanation for the similarities between the Altaic languages, and this is that they form a <em>sprachbund</em> instead. A sprachbund, from the German “Sprachbund”, meaning “language alliance”, means that languages that are not necessarily related can influence each other, including both loanwords and grammatical structure, due to their geographical proximity. Sprachbunds typically get closer and closer over time, because of their continued contact, whereas language families actually tend to diverge over time because they spread out. The Altaic languages showed signs of the former, because the early forms of Mongolic, Turkic, and Tungusic languages differed more than they do now, and there is no evidence of them diverging at some point.</p>
<p>It is possible for sprachbunds to consist of related languages. For example, the Balkan sprachbund contains Greek, Bulgarian, Serbain, Albanian, Romanian, Romani, and some dialects of Turkish. Apart from Turkish (which is, and you’ll never guess this, a Turkic language), the others are all Indo-European. The similarities between them (articles as postpositions, evidentiality, shared cases, loanwords/cliques, and a lot more) cannnot be explained because they are Indo-European - that would mean the Romance, Slavic, Hellenic, Albanian, and even Indo-Iranian languages all share a pretty close common ancestor, but that contradicts how ancient the centum-satem split is, and the Balkan languages are on either side of it.</p>
</section>
<section id="loanwords" class="level1">
<h1>Loanwords</h1>
<p>If a language has loanwords from another language, this is a huge piece of evidence that they came into contact at some point. A huge part of English vocabulary is borrowed from French, mostly the fancy big words that aren’t Greek or Latin. It’s not that big of a deal if we already know the history behind this - it’s well known that these loanwords are because of the Norman conquest of England, where French was used as the language of the elite, which explains why the words associated with the elite were French (for farm animal names, the word for the living creature, which the English-speaking commoners interacted with, are Germanic, like “cow” or “lamb”, but the word for the dead creature, which the French-speaking elite ate, were French, like “beef” or “mutton”).</p>
<p>However, if we find loanwords as a result of a historical event that wasn’t well documented or known about, or even from prehistory, we can even reconstruct that event. For example, the Germanic languages have a lot of loanwords (we know these must be loanwords because they don’t have any Indo-European cognates or etymology) from Pre-Indo-European languages (with unrelated languages), especially for concepts that were new to the Indo-Europeans, because they were local to the area that they arrived to. Therefore, we can deduce that the Indo-Europeans encountered Pre-Indo-European speakers when they arrived in that region of Europe.</p>
</section>
<section id="conservative-languages" class="level1">
<h1>Conservative Languages</h1>
<p>Some people might be surprised about a famous observation in historical linguistics, that Sanskrit is more mutually intelligible with Lithuanian than it is with Hindi, even though Hindi is a direct descendant of Sanskrit, while Lithuanian isn’t even Indo-Iranian.</p>
<p>For example, look at the sentence “your gift is the fire”.</p>
<p>Sanskrit: तव दानं अग्निः अस्ति (tava dānaṃ agniḥ)</p>
<p>Lithuanian: tavo dovana ugnis</p>
<p>Hindi: तुम्हारा उपहार आग है (tumhārā upahār āg hai)</p>
<p>As you can see, the Sanskrit and Lithuanian sentences both have a similar structure, and the vocabulary appears more similar. While Hindi has cognates for “your” and “fire”, they are less recognizeable than the Lithuanian ones. Also, the copula (the word for “is”) is mandatory in Hindi, because it is more analytic. Meanwhile, since Sanskrit and Lithuanian are more synthetic, the parts of speech are built into the words themselves, so the copula is not needed and used more for emphasis (they are asti and yra, respectively). Also, Lithuanian happens to have SVO word order while Sanskrit and Hindi have SOV word order, but Sanskrit and Lithuanian both have flexible word order.</p>
<p>So why is Lithuanian so similar to Sanskrit? It’s because Lithuanian is pretty conservative, or resistant to change.</p>
<p>Sanskrit, being an ancient language, is relatively close to Proto-Indo-European, because it hasn’t had that much time to evolve compared to modern languages. While it was alive, it still was conservative, because it was heavily standardized.</p>
<p>Lithuanian, on the other hand, is still spoken natively to this day. However, the Baltic countries were relatively isolated (since the forests, wetlands, and rivers formed natural barriers) from the rest of Europe and all the conquests that happened that caused language change, so their languages (excluding Estonian, which is Uralic) have preserved many features from Proto-Indo-European, and innovated new features relatively slowly. Because of this, Lithuanian and Sanskrit are both similar to Proto-Indo-European, and therefore similar to each other.</p>
<p>Tamil is another example of a conservative language. It is relatively close to Proto-Dravidian, compared to Telugu and Kannada, which have innovated more. This is why ancient Tamil literature is still understandable to modern Tamil speakers. However, Tamil has huge diglossia, or intelligibility gap, between the formal variety learned in school and spoken on the news, and the colloquial variety spoken on the streets and at home. The formal variety is the one that is more conservative. I only understand the colloquial variety, which is why to me, ancient Tamil literature might as well be written by aliens from Jupiter. I’m going to write a future blog post about languages and dialects, but this is a small taste of that.</p>
</section>
<section id="conclusion" class="level1">
<h1>Conclusion</h1>
<p>Now, we know how proto languages are reconstructed, and how to disprove language family claims. However, some linguists didn’t get the memo that theories about language families must be realistic, so that’s what part 3 is gonna be all about.</p>
</section>
<section id="further-information" class="level1">
<h1>Further information</h1>
<p>The Arabic example is from <a href="https://www.youtube.com/shorts/ES5qpzNG1ew">this human1011 YouTube short</a>.</p>
<p>I’d recommend the book <a href="https://www.goodreads.com/en/book/show/217387741-proto">“Proto”</a> by Laura Spinney if you want a broader picture of how the Indo-European languages spread, using not just linguistics but also archaeology and genetics.</p>


</section>

 ]]></description>
  <category>Linguistics</category>
  <guid>https://vaishnavs.net/posts/Historical-Linguistics-2/</guid>
  <pubDate>Mon, 29 Jun 2026 18:30:00 GMT</pubDate>
  <media:content url="https://vaishnavs.net/posts/Historical-Linguistics-2/hundred.png" medium="image" type="image/png" height="69" width="144"/>
</item>
<item>
  <title>Syntax - Recursion, Constituent Units, and Trees</title>
  <dc:creator>Vaishnav Sudarshan</dc:creator>
  <link>https://vaishnavs.net/posts/Syntax Part 1/</link>
  <description><![CDATA[ 





<section id="introduction" class="level1">
<h1>Introduction</h1>
<p>You may have learned about syntax in English class in school, and parts of what you likely learned are pretty close to linguistics, like phrases and stuff, while others are horrendously off.</p>
<p>Syntax is basically sentence structure. However, if someone says, “this sentence has short syntax” when referring to a short or simple sentence, that statement sounds reasonable, but it’s like saying “this rock is intelligent”, as in it’s kinda nonsensical. Just say “this sentence is short” or something. To avoid confusion about what syntax actually is, it’s probably better to define syntax as the set of rules that govern how a language allows for sentences to be formed (syntax describes a language, not an individual sentence).</p>
</section>
<section id="bracketing-and-constituents" class="level1">
<h1>Bracketing and Constituents</h1>
<p>Take any complicated sentence in English. For example, take the sentence “The student who the professor whom the dean hired praised left.” This seems so confusing at first. However, we see that the basic sentence is just “the student left”. We can put brackets around the stuff in between, that just describes the student: “The student [who the professor whom the dean hired praised] left”. The “whom the dean hired” just describes the professor, so we can put brackets around that: “The student [who the professor [whom the dean hired] praised] left”.</p>
<p>Each of the bracketed parts, next to the thing it describes, is called a <em>constituent</em>. These are basically units of structure that show some syntactic role.</p>
<p>One way to tell the role that a constituent plays is to replace it with another unit whose role we know. For example, “The student [who the professor whom the dean hired praised]” can be replaced with “The student”, which we know represents the subject. Therefore, every single wrd before “left” is a constituent that represents the subject. Similarly, “left” is a constituent that represents the verb. If you want, you can replace “left” with “ate ice cream”, because this constituent represents what the student <em>did</em>.</p>
<p>Constituents help us figure out what words can be put together. In English, subjects and objects are <em>noun phrases</em>. Pronouns, plurals, and proper nouns can be their own noun phrases, while common nouns need a determiner. So, “Canada” is its own noun phrase, while “a country” is also a noun phrase that is the same syntactic unit. You can say “I go to [Canada]” or “I go to [a country]” but you can’t say “I go to country” or “I go to a Canada” .</p>
<section id="trees" class="level2">
<h2 class="anchored" data-anchor-id="trees">Trees</h2>
<p>Using brackets might sound easy at first, but once you have a LOT of brackets, it can get really confusing and tedious. Think about in programming or math when you have too many parentheses because you want to do things in a single line, so you end up saying something like “print(int(input(str(range(x, y, z)[-1]) + str(int(s[0]) + int(s[1])))) + 3)” in Python. This is really hard to read, which is why it’s considered bad programming practice by most people (not me though, hehe).</p>
<p>In programming languages, it’s hard to have a different, less confusing representation of parentheses to program nested things in an actual coding editor (unless you have something like block code in Scratch). However, in linguistics, especially when a lot of it was hand-drawn, people found it easier to use trees.</p>
<p>Let’s take the same sentence again: “The student who his professor whom the dean hired praised left.”</p>
<p>We can start the top node of the tree with S, which represents the sentence.</p>
<div class="cell" data-layout-align="default">
<div class="cell-output-display">
<div>
<p></p><figure class="figure"><p></p>
<div>
<pre class="mermaid mermaid-js">%%{init: {
  "theme": "default",
  "themeVariables": {
    "fontSize": "70px",
    "primaryTextColor": "#000000",
    "lineWidth": 3
  }
}}%%

graph TD

S ==&gt; NP 
S ==&gt; VP 
VP ==&gt; V

NP ==&gt; NP1["NP"]
NP1 ==&gt; Det
NP1 ==&gt; N1["N"]

Det ==&gt; The
N1 ==&gt; student

NP ==&gt; MP 
MP ==&gt; Rel
MP ==&gt; NP2["NP"]
MP ==&gt; VP1["VP"]

Rel ==&gt; A["who"]

VP1 ==&gt; V1["V"]

NP3 ==&gt; Pos
Pos ==&gt; his
NP3 ==&gt; N3["N"]
N3 ==&gt; professor

NP2 ==&gt; NP3["NP"]
NP2 ==&gt; MP1

MP1 ==&gt; Rel1["Rel"]
Rel1 ==&gt; B["who"]

MP1 ==&gt; NP4["NP"]
MP1 ==&gt; VP2["VP"]

VP2 ==&gt; V2["V"]

NP4 ==&gt; Det1["Det"]
Det1 ==&gt; the
NP4 ==&gt; N4["N"]
N4 ==&gt; dean

V2 ==&gt; hired
V1 ==&gt; praised
V ==&gt; left

%% -----------------------
%% STYLES
%% -----------------------

classDef sentenceGroup fill:#ffe6cc,stroke:#ff8c00,stroke-width:3px,color:#000;
classDef nounGroup fill:#d9ecff,stroke:#1f77b4,stroke-width:2px,color:#000;
classDef verbGroup fill:#ddffdd,stroke:#2ca02c,stroke-width:2px,color:#000;
classDef mpGroup fill:#fff2cc,stroke:#d4a017,stroke-width:2px,color:#000;
classDef relGroup fill:#ffd6e0,stroke:#e6005c,stroke-width:2px,color:#000;

class S sentenceGroup;

class NP,NP1,NP2,NP3,NP4,N1,N3,N4 nounGroup;

class VP,VP1,VP2,V,V1,V2 verbGroup;

class MP,MP1,Det,Det1,Pos mpGroup;

class Rel,Rel1 relGroup;
</pre>
</div>
<p></p></figure><p></p>
</div>
</div>
</div>
<p>Here, NP means noun phrase, VP means verb phrase, Det means determiner, N means noun, MP means modifier phrase, and Pos means possessive.</p>
<p>Note that these descriptions for parts of speech aren’t universal (as we’ll see in a later part), but they are convenient for English to show how constituents are related. In fact, really important takeaway in descriptive linguistics is that these terms may be useful approximations for the syntactic roles in nearby related languages, but don’t necessarily have an equivalent in every single language.</p>
<p>Additionally, note that we can stop breaking the sentence down whenever we want. This syntax tree broke down the sentence into individual words just to show how complicated it really got, but if you want, you can stop early, after you reach units of phrases, or you can go further, all the way to the units of morphemes. You get to choose the level of precise detail based on the specific task in linguistics, kind of like how you get to choose the level of precise detail when making a phonetic IPA transcription depending on what features you’re interested in examining.</p>
</section>
<section id="example-of-why-bracketing-is-helpful" class="level2">
<h2 class="anchored" data-anchor-id="example-of-why-bracketing-is-helpful">Example of why bracketing is helpful</h2>
<p>You may have heard the joke “Time flies like an arrow, but fruit flies like a banana”. It’s funny because most people can tell the syntactic difference between these two, but the words are mostly still the same. So, as any good linguist would do, let’s ruin the joke by overanalyzing it!</p>
<p>Let’s look at the first sentence. “Time flies like an arrow” can be broken down into the noun phrase, “Time”, and verb phrase, “flies like an arrow”, which can be broken down into the verb “flies” and the modifier “like an arrow”.</p>
<div class="cell" data-layout-align="default">
<div class="cell-output-display">
<div>
<p></p><figure class="figure"><p></p>
<div>
<pre class="mermaid mermaid-js">%%{init: {
  "theme": "default",
  "themeVariables": {
    "fontSize": "70px",
    "primaryTextColor": "#000000",
    "lineColor": "#000000",
    "lineWidth": 3
  },
  "flowchart": {
    "htmlLabels": true
  }
}}%%

graph TD

S ==&gt; NP
S ==&gt; VP

NP ==&gt; N
N ==&gt; Time

VP ==&gt; V
V ==&gt; flies
VP ==&gt; MP

MP ==&gt; Prep
Prep ==&gt; like
MP ==&gt; NP1["NP"]

NP1 ==&gt; Det
NP1 ==&gt; N1["N"]
Det ==&gt; an
N1 ==&gt; arrow

%% -----------------------
%% STYLES
%% -----------------------

classDef sentenceGroup fill:#ffe6cc,stroke:#ff8c00,stroke-width:3px,color:#000;
classDef nounGroup fill:#d9ecff,stroke:#1f77b4,stroke-width:2px,color:#000;
classDef verbGroup fill:#ddffdd,stroke:#2ca02c,stroke-width:2px,color:#000;
classDef mpGroup fill:#fff2cc,stroke:#d4a017,stroke-width:2px,color:#000;
classDef prepGroup fill:#e6ddff,stroke:#6f42c1,stroke-width:2px,color:#000;

%% -----------------------
%% APPLY CLASSES
%% -----------------------

class S sentenceGroup;

class NP,N,N1,NP1 nounGroup;

class VP,V verbGroup;

class MP,Det mpGroup;

class Prep prepGroup;
</pre>
</div>
<p></p></figure><p></p>
</div>
</div>
</div>
<p>Meanwhile, the second sentence can be broken down into the noun phrase, “Fruit flies”, and the verb phrase “like a banana”, which can be broken down into the verb “like” and the noun phrase “a banana”.</p>
<div class="cell" data-layout-align="default">
<div class="cell-output-display">
<div>
<p></p><figure class="figure"><p></p>
<div>
<pre class="mermaid mermaid-js">%%{init: {
  "theme": "default",
  "themeVariables": {
    "fontSize": "70px",
    "primaryTextColor": "#000000",
    "lineColor": "#000000",
    "lineWidth": 3
  },
  "flowchart": {
    "htmlLabels": true
  }
}}%%

graph TD

S ==&gt; NP
NP ==&gt; M
NP ==&gt; N
M ==&gt; Fruit
N ==&gt; flies

S ==&gt; VP
VP ==&gt; V
V ==&gt; like

VP ==&gt; NP1["NP"]
NP1 ==&gt; Det
Det ==&gt; a
NP1 ==&gt; N1["N"]
N1 ==&gt; banana

%% -----------------------
%% STYLES
%% -----------------------

classDef sentenceGroup fill:#ffe6cc,stroke:#ff8c00,stroke-width:3px,color:#000;
classDef nounGroup fill:#d9ecff,stroke:#1f77b4,stroke-width:2px,color:#000;
classDef verbGroup fill:#ddffdd,stroke:#2ca02c,stroke-width:2px,color:#000;
classDef modGroup fill:#fff2cc,stroke:#d4a017,stroke-width:2px,color:#000;

class S sentenceGroup;

class NP,N,N1,NP1 nounGroup;

class VP,V verbGroup;

class M,Det modGroup;
</pre>
</div>
<p></p></figure><p></p>
</div>
</div>
</div>
</section>
</section>
<section id="possible-sentences" class="level1">
<h1>Possible Sentences</h1>
<p>There are a finite amount of rules for how to generate a valid sentence, but an infinite amount of possible sentences (partially thanks to recursion, as you are about to see). You can represent the structure of possible sentences using trees. Note that only the last layer of a tree actually says what each word is. So, “fruit flies like a banana” and “hungry people eat that food” would have their trees looking about the same. Because a language is so complex, it’s hard to write down every specific structure of sentences, so you can only be pretty general.</p>
</section>
<section id="scope-ambiguity" class="level1">
<h1>Scope Ambiguity</h1>
<p>Obviously, in spoken language, you don’t have brackets or syntax trees. So, how would you interpret this sentence?</p>
<p>“The dog and the cat that you own fought each other”.</p>
<p>Either this means that you own both the dog and the cat (“[[The dog and the cat] that you own] fought each other”), or your cat fought another dog (“[The dog and [the cat that you own]] fought each other”).</p>
<p>Another example is “I saw the man with a telescope”, which either means the man has a telescope and you saw him, or you used a telescope to see the man.</p>
<p>In general, scope ambiguity is when you can’t tell what constituent is being modified.</p>
<p>Prescriptivists are always like, “commas save lives, people” (“Let’s eat kids” vs “Let’s eat, kids”). However, sentences like these are perfectly acceptable in standard English and the ambiguity can’t just be fixed by adding commas (because that would be considered grammatically incorrect then since prescriptivists say that you can’t put commas in those places). This is just yet another argument for descriptive linguistics - prescriptivists can’t even be consistent with their own objectives, so it’s better to just let language be.</p>
</section>
<section id="recursion-introduction" class="level1">
<h1>Recursion Introduction</h1>
<p>Let’s talk about something that is seemingly completely different, but is actually the heart of what we just did with our nested brackets.</p>
<p>Take the Fibonacci sequence, which you’ve probably heard of before. Let’s look at one of the most common representations of its defitions:</p>
<p>Let <img src="https://latex.codecogs.com/png.latex?F_0%20=%200,%20F_1%20=%201"> and <img src="https://latex.codecogs.com/png.latex?F_n%20=%20F_%7Bn-1%7D%20+%20F_%7Bn-2%7D"> for <img src="https://latex.codecogs.com/png.latex?n%20%5Cgeq%202">.</p>
<p>Given only this information, you cannot instantly figure out what <img src="https://latex.codecogs.com/png.latex?F_%7B100%7D"> is. You have to write it as <img src="https://latex.codecogs.com/png.latex?F_%7B100%7D%20=%20F_%7B99%7D%20+%20F_%7B98%7D">, and then you have to write <img src="https://latex.codecogs.com/png.latex?F_%7B99%7D"> as <img src="https://latex.codecogs.com/png.latex?F_%7B98%7D%20+%20F_%7B97%7D">, and so on, until you get down to <img src="https://latex.codecogs.com/png.latex?F_1"> and <img src="https://latex.codecogs.com/png.latex?F_0">. Without the base case, you’d be simplifying forever, because you’d never get it only in terms of numbers.</p>
<p>Now, look at this code snippet in Python:</p>
<div class="sourceCode" id="cb1" style="background: #f1f3f5;"><pre class="sourceCode python code-with-copy"><code class="sourceCode python"><span id="cb1-1"><span class="kw" style="color: #003B4F;
background-color: null;
font-weight: bold;
font-style: inherit;">def</span> reverse(s): <span class="co" style="color: #5E5E5E;
background-color: null;
font-style: inherit;"># return a String that is the reverse of s</span></span>
<span id="cb1-2">    <span class="cf" style="color: #003B4F;
background-color: null;
font-weight: bold;
font-style: inherit;">if</span> <span class="bu" style="color: null;
background-color: null;
font-style: inherit;">len</span>(s) <span class="op" style="color: #5E5E5E;
background-color: null;
font-style: inherit;">==</span> <span class="dv" style="color: #AD0000;
background-color: null;
font-style: inherit;">1</span>: <span class="co" style="color: #5E5E5E;
background-color: null;
font-style: inherit;"># base case: if the string has 1 character, </span></span>
<span id="cb1-3">        <span class="cf" style="color: #003B4F;
background-color: null;
font-weight: bold;
font-style: inherit;">return</span> s <span class="co" style="color: #5E5E5E;
background-color: null;
font-style: inherit;"># it is inherently the reverse of itself, so we can just return it</span></span>
<span id="cb1-4">    <span class="cf" style="color: #003B4F;
background-color: null;
font-weight: bold;
font-style: inherit;">return</span> s[<span class="op" style="color: #5E5E5E;
background-color: null;
font-style: inherit;">-</span><span class="dv" style="color: #AD0000;
background-color: null;
font-style: inherit;">1</span>] <span class="op" style="color: #5E5E5E;
background-color: null;
font-style: inherit;">+</span> reverse(s[:<span class="op" style="color: #5E5E5E;
background-color: null;
font-style: inherit;">-</span><span class="dv" style="color: #AD0000;
background-color: null;
font-style: inherit;">1</span>]) <span class="co" style="color: #5E5E5E;
background-color: null;
font-style: inherit;"># move the last letter to the beginning and find the reverse of the rest</span></span></code></pre></div>
<p>As you can guess from the name of this function, it reverses a string by taking the last letter, the first letter, and the reverse of the middle part in between. As a result, it calls itself. Again, there is a base case, which is that the string being called on has 0 or 1 characters eventually, but it allows us to reverse a string of any length, up to infinity.</p>
<p>Here’s another pattern: Serpenski’s Triangle. You start with an equilateral triangle, then split it into four congruent equilateral triangles, such that the middle part is cut out, and then repeat this for every single equilateral triangle inside, being able to go for an indefinite amount of layers:</p>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><a href="serpinski.png" class="lightbox" data-gallery="quarto-lightbox-gallery-1" title="A diagram of generating Serpenski’s Triangle"><img src="https://vaishnavs.net/posts/Syntax Part 1/serpinski.png" class="img-fluid figure-img" alt="A diagram of generating Serpenski’s Triangle"></a></p>
<figcaption>A diagram of generating Serpenski’s Triangle</figcaption>
</figure>
</div>
<p>The base case of this diagram is that the the triangle has finite size, because the biggest triangle isn’t inside of a bigger one, but you can make triangles as small as you want, that are all just miniature, similar versions to the bigger ones.</p>
<p>There’s one more thing I want to show, to make the pattern evident. Suppose we name the acronym LING to mean LING Is Not Good. Then, a letter of the acronym is the first letter of the acronym itself. So, we have an infinite loop trying to figure out what LING stands for, but we never get there because it keeps on referring to itself, unless we define a base case later on to what LING actually stands for.</p>
<p>This acronym is the same pattern as the Fibonacci sequence, Serpenski’s Triangle, and the reverse function, and it’s called recursion - you define a base case, and then each next step is based on the previous one(s), allowing you to go as far as you want.</p>
</section>
<section id="recursion-in-syntax" class="level1">
<h1>Recursion in Syntax</h1>
<p>In syntax, recursion is when you can put a constituent inside another constituent of the same level. For example, look at the phrase “the monkey of the friend of the neighbor of the student of the uncle”. This is a noun phrase, because the overall constituent is “the monkey”. Inside of the entire phrase, we have “the monkey of the friend of the neighbor of the student” which is also a noun phrase, and inside of that, we have “the monkey of the friend of the neighbor”, which is also a noun phrase, and so on.</p>
<p>English allows for infinite recursion like this, which is why there is no limit to how long a sentence can be - we can always just recurse one more time. For example, “the uncle” can have “of the person” added to it. We don’t need to explicitly worry about a base case - no matter how long the sentence is, we can always ultimately simplify it down to a single noun (or generally a single constituent or unit), which is the base case. You can also recurse the other direction, like adding “the toy of” before “the monkey”.</p>
</section>
<section id="more-examples-of-english-recursion" class="level1">
<h1>More Examples of English Recursion</h1>
<p>English doesn’t just need “of” (or equivalently, “’s”) to be able to recurse. Using “of” means a noun phrase is being a recursed. Here are some other examples of English being able to recurse on different constituents.</p>
<p>There can be recursion on full sentences (specifically of the structure where a noun phrase is the subject and it enacts a verb phrase). For example, “I ate food” is a complete sentence. You can also insert this into “You think that I ate food”, which itself is another complete sentence. You can further insert this into “He doesn’t believe that you think that I ate food”, and so on.</p>
<p>The very first sentence we made a tree out of, “The student who the professor whom the dean hired praised left”, is also recursive, because “whom the dean hired” is called a relative clause, and this, describing “professor”, is inside the relative clause “who the professor praised”, which in turn describes “student”.</p>
<p>Prepositional phrases can also be recursed. If you have the phrase “on the table in the house near the window”, this contains the prepositional phrase “on the table in the house”, which contains the prepositional phrase “on the table”.</p>
<p>All this goes to show that English has many mechanisms to recurse different types of constituents.</p>
</section>
<section id="embedding" class="level1">
<h1>Embedding</h1>
<p>Recursion is just one subset of a larger phenomenon called embedding. Embedding is inserting some constituent into another constituent, regardless of what type of constituent they are, and recursion is when the constituents have the same type.</p>
<p>For example, “the bird flew in the sky” has embedding in the verb phrase “flew in the sky”, because it contains “in the sky”, which is a prepositional phrase.</p>
</section>
<section id="recursion-in-other-languages" class="level1">
<h1>Recursion in Other Languages</h1>
<p>All languages that linguists had encountered up to 2005 had some means to recurse indefinitely. For example, in French, the first recursion example above would be translated as “le singe de l’ami du voisin de l’étudiant de l’oncle”. The word “de” has the same syntactic function that “of” has, which allows the same recursion to work. Note that “du” is just a contraction of “de” and “le”, so it doesn’t do anything different from “de l’”.</p>
<p>You might think that maybe that’s just because English and French are so close, both geographically and linguistically, because English is basically half French anyway (it’s actually 29%, that was an exaggeration).</p>
<p>However, it has nothing to do with proximity, beacuse even Chinese, which is not even in the same language family as English and French and is spoken in an entirely different part of the world, allows for this exact phrase to recurse as “shūshu de xuéshēng de línjū de péngyǒu de hóuzǐ”. Here, “de” (not at all related to the French “de”) is basically the Chinese equivalent of “’s”, so it’s more along the lines of “the uncle’s student’s neighbor’s friend’s monkey”. It just so happens that English allows you to recurse in both directions (because “A’s B” is the same as “the B of A”), while Chinese only allows you to use “’s” and French only allows you to use “of”. This doesn’t matter. The point is, all the languages that linguists encountered so far had some syntactic mechanism to be able to directly translate this phrase.</p>
</section>
<section id="pirahã-counterexample" class="level1">
<h1>Pirahã Counterexample</h1>
<p>However, the linguist Daniel Everett encountered an indigenous Brazilian language isolate called Pirahã. While you can embed a constituent into another constituent exactly once, to do so indefinitely, you must use multiple sentences. In 2005, Everett published his claim that Pirahã lacks syntactic recursion. For example, instead of saying “the monkey of the friend of the neighbor of the student of the uncle”, you have to say something like this:</p>
<p>The uncle has a student. This student has a neighbor. This neighbor has a friend. This friend has a monkey. This monkey [insert whatever you want to say about the monkey].</p>
<p>In a sense, Pirahã might not have the same idea of recursion as linguists view it, but it’s actually closer to the structure of recursion used in programming. Instead of having all the information in a single unit, you can use the one word (“monkey”) that is the noun phrase in question, that is referenced by a different word (“friend”), and so on, causing you to trace the overall meaning to represent every step all the way to the base case, which is “uncle” in this example. This is pretty similar to calling the a recursive function, like the reverse string function, on a smaller piece, like the middle of the string, until you get enough information, like having a string that has length 0 or 1. The only difference is that there’s not a mandatory base case in Pirahã, and you can stop whenever you want, like at “student”.</p>
<p>Noam Chomsky, the guy who basically invented modern linguistics, thought that all languages had the capacity to recurse, and that it was some universal cognitive trait to humankind as a whole. This is why Chomsky’s supporters find Everett’s claim to be controversial - perhaps Pirahã does have recursion, but it’s in a different sense than what Everett’s notion of recursion was.</p>
</section>
<section id="syntax-trees-in-programming-languages" class="level1">
<h1>Syntax Trees in Programming Languages</h1>
<p>Statements from programming languages can also be represented with smaller pieces. Syntax trees for them have to be very precise, because they allow statements to be parsed.</p>
<p>Take the following Python statement:</p>
<div class="sourceCode" id="cb2" style="background: #f1f3f5;"><pre class="sourceCode python code-with-copy"><code class="sourceCode python"><span id="cb2-1">x <span class="op" style="color: #5E5E5E;
background-color: null;
font-style: inherit;">=</span> <span class="dv" style="color: #AD0000;
background-color: null;
font-style: inherit;">3</span> <span class="op" style="color: #5E5E5E;
background-color: null;
font-style: inherit;">+</span> <span class="dv" style="color: #AD0000;
background-color: null;
font-style: inherit;">5</span> <span class="op" style="color: #5E5E5E;
background-color: null;
font-style: inherit;">*</span> <span class="dv" style="color: #AD0000;
background-color: null;
font-style: inherit;">2</span></span></code></pre></div>
<p>This can be represented with the following tree:</p>
<div class="cell" data-layout-align="default">
<div class="cell-output-display">
<div>
<p></p><figure class="figure"><p></p>
<div>
<pre class="mermaid mermaid-js">graph TD
Assignment ==&gt; x["x"]
Assignment ==&gt; Addition
Addition ==&gt; 3["3"]
Addition ==&gt; Multiplication
Multiplication ==&gt; 5["5"]
Multiplication ==&gt; 2["2"]
</pre>
</div>
<p></p></figure><p></p>
</div>
</div>
</div>
<p>There is a very similar recursive structure here, because there is an operator (multiplication) inside of another operator (addition) inside of yet another operator (assignment). If you’ve ever wondered how computers understand order of operations, recursive syntax trees are how - blindly going left to right might cause a mistake, but using a syntax tree is basically foolproof.</p>
<p>The word “syntax” for programming languages is kind of equivalent to the word “grammar” for natural languages, but this is one of the actual instances of “syntax”, the one used for natural languages as an aspect of “grammar”, in programming languages.</p>
<p>I will probably write a future blog post specifically about programming language theory later, but this is an interesting preview into how it uses linguistics tools.</p>
</section>
<section id="conclusion" class="level1">
<h1>Conclusion</h1>
<p>Now that we know how you can break apart sentences into smaller pieces, we can talk about the roles of the smaller pieces themselves! Stay tuned for morphosyntax, including one of the most confusing concepts in linguistics (good luck)!</p>


</section>

 ]]></description>
  <category>Linguistics</category>
  <category>CS</category>
  <guid>https://vaishnavs.net/posts/Syntax Part 1/</guid>
  <pubDate>Tue, 09 Jun 2026 18:30:00 GMT</pubDate>
  <media:content url="https://vaishnavs.net/posts/Syntax Part 1/caca.png" medium="image" type="image/png" height="90" width="144"/>
</item>
<item>
  <title>Why orbits have equal area in equal time</title>
  <dc:creator>Vaishnav Sudarshan</dc:creator>
  <link>https://vaishnavs.net/posts/Why-Orbits-Have-Equal-Area-In-Equal-Time/</link>
  <description><![CDATA[ 





<section id="introduction" class="level1">
<h1>Introduction</h1>
<p>Usually when you learn the laws of physics, it’s something that instantly makes sense. The first law of thermodynamics is that energy is conserved, duhhh! Newton’s second law is that <img src="https://latex.codecogs.com/png.latex?F_%7Bnet%7D%20=%20ma">, duhhh! But then Kepler’s second law is that when planets are in orbit, which are usually eliptical, the area is swept out at a constant rate. Huhhh? That sounds so random! However, there is a pretty nice reason for why this is.</p>
</section>
<section id="proof" class="level1">
<h1>Proof</h1>
<p>Basically, what we seek to prove is that <img src="https://latex.codecogs.com/png.latex?%5Cfrac%7BdA%7D%7Bdt%7D"> is constant, where <img src="https://latex.codecogs.com/png.latex?A"> is the area swept out by the planet.</p>
<p><a href="dur.png" class="lightbox" data-gallery="quarto-lightbox-gallery-1" title="Diagram of what we seek"><img src="https://vaishnavs.net/posts/Why-Orbits-Have-Equal-Area-In-Equal-Time/dur.png" class="img-fluid" alt="Diagram of what we seek"></a>.</p>
<p>First, we need to find <img src="https://latex.codecogs.com/png.latex?dA">, a tiny change in the area swept out, in relation to the other tiny changes like in position or time. The planet is moving in an ellipse, so the distance from the center keeps on changing. For a tiny change in position <img src="https://latex.codecogs.com/png.latex?%5Cvec%7Bdx%7D">, the distance from the center has barely changed, and we can call this distance <img src="https://latex.codecogs.com/png.latex?%5Cvec%7Br%7D">. The reason for this is because the new distance is <img src="https://latex.codecogs.com/png.latex?%5Cvec%7Br%7D%20+%20d%5Cvec%7Br%7D">, but since <img src="https://latex.codecogs.com/png.latex?d%5Cvec%7Br%7D">, the change in the radius, is infinitesimal, this is the same as <img src="https://latex.codecogs.com/png.latex?%5Cvec%7Br%7D">.</p>
<p><img src="https://latex.codecogs.com/png.latex?%5Cvec%7Bdx%7D"> is basically the length of the arc made by this tiny change in time, because the curve is zoomed in so much that it looks like a straight line. The area <img src="https://latex.codecogs.com/png.latex?dA"> formed by this sector, which is approximately a triangle with two of the side lengths being <img src="https://latex.codecogs.com/png.latex?%7C%5Cvec%7Br%7D%7C"> and <img src="https://latex.codecogs.com/png.latex?%7C%5Cvec%7Bdx%7D%7C">, is <img src="https://latex.codecogs.com/png.latex?%5Cfrac%7B1%7D%7B2%7D%20%7C%5Cvec%7Br%7D%7C%20%7C%5Cvec%7Bdx%7D%7C%20%5Csin(%5Ctheta)">, where <img src="https://latex.codecogs.com/png.latex?%5Ctheta"> is the angle between <img src="https://latex.codecogs.com/png.latex?%5Cvec%7Br%7D"> and <img src="https://latex.codecogs.com/png.latex?%5Cvec%7Bdx%7D">. This is just a basic formula in geometry for the area of a triangle given two sides and the angle between them. You might realize that this is the same as <img src="https://latex.codecogs.com/png.latex?%5Cfrac%7B1%7D%7B2%7D%20%7C%5Cvec%7Br%7D%20%5Ctimes%20%5Cvec%7Bdx%7D%7C">. This is because the area of the parallelogram formed by two vectors is the magnitude of their cross product, and the area of this triangle is half of that.</p>
<p>Because <img src="https://latex.codecogs.com/png.latex?%5Cvec%7Bdx%7D%20=%20%5Cvec%7Bv%7D%20dt">, where <img src="https://latex.codecogs.com/png.latex?%5Cvec%7Bv%7D"> is the velocity of the planet, and also <img src="https://latex.codecogs.com/png.latex?dt"> is a scalar (which means we can remove it from the magnitude), we can substitute this in to get <img src="https://latex.codecogs.com/png.latex?dA%20=%20%5Cfrac%7B1%7D%7B2%7D%20%7C%5Cvec%7Br%7D%7C%20%7C%5Cvec%7Bv%7D%7C%20dt%20%5Csin(%5Ctheta)">, so <img src="https://latex.codecogs.com/png.latex?%5Cfrac%7BdA%7D%7Bdt%7D%20=%20%5Cfrac%7B1%7D%7B2%7D%20%7C%5Cvec%7Br%7D%7C%20%7C%5Cvec%7Bv%7D%7C%20%5Csin(%5Ctheta)">. Similar to <img src="https://latex.codecogs.com/png.latex?%5Cvec%7Br%7D">, <img src="https://latex.codecogs.com/png.latex?%5Cvec%7Bv%7D"> doesn’t change after an infinitesimal change in time <img src="https://latex.codecogs.com/png.latex?dt">, because again, <img src="https://latex.codecogs.com/png.latex?%5Cvec%7Bv%7D%20+%20d%5Cvec%7Bv%7D"> is infinitesimally close to <img src="https://latex.codecogs.com/png.latex?%5Cvec%7Bv%7D">.</p>
<p>Remember that the angular momentum <img src="https://latex.codecogs.com/png.latex?L"> is defined as <img src="https://latex.codecogs.com/png.latex?L%20=%20m%20%5Cvec%7Br%7D%20%5Ctimes%20%5Cvec%7Bv%7D">, where <img src="https://latex.codecogs.com/png.latex?m"> is the mass of the planet. So, <img src="https://latex.codecogs.com/png.latex?%7CL%7C%20=%20m%20%7C%5Cvec%7Br%7D%7C%20%7C%5Cvec%7Bv%7D%7C%20%5Csin(%5Ctheta)"></p>
<p>We can substitute this in to get <img src="https://latex.codecogs.com/png.latex?%5Cfrac%7BdA%7D%7Bdt%7D%20=%20%5Cfrac%7B%7CL%7C%7D%7B2m%7D">.</p>
<p>Because angular momentum is conserved, and the mass is constant, <img src="https://latex.codecogs.com/png.latex?%5Cfrac%7BdA%7D%7Bdt%7D"> is constant, which is what we wanted to prove.</p>
</section>
<section id="conclusion" class="level1">
<h1>Conclusion</h1>
<p>Now we know where Kepler’s second law come from, and stay tuned for more physics and astronomy derivations!</p>


</section>

 ]]></description>
  <category>Physics</category>
  <category>Math</category>
  <guid>https://vaishnavs.net/posts/Why-Orbits-Have-Equal-Area-In-Equal-Time/</guid>
  <pubDate>Sun, 07 Jun 2026 18:30:00 GMT</pubDate>
</item>
<item>
  <title>Historical Linguistics Part 1: The Beginning of Linguistics</title>
  <dc:creator>Vaishnav Sudarshan</dc:creator>
  <link>https://vaishnavs.net/posts/Historical-Linguistics-1/</link>
  <description><![CDATA[ 





<section id="introduction" class="level1">
<h1>Introduction</h1>
<p>Right now, I’m jumping around the circle of linguistics a little. The trend has been to go from smaller units of language to bigger ones, like sounds to words to sentences. However, I think that going to one of the outermost rings, with the units of languages and language families, is helpful for more context with the inner rings too.</p>
<p>Historical linguistics is basically how the field of linguistics started - it’s not like early linguists from the 1800’s were saying “Oh, cool, a new field just appeared with barely any competition! Let’s convert tokens to vectors in semantic space using trained embedding matrices!” On the contrary, they were just observing languages at a broader scale, and realized that there actually were patterns, trends, and rules about how they could be related. That’s when they realized that languages could be analyzed scientifically, and weren’t just random gobbledegook.</p>
<section id="historical-context-of-historical-linguistics" class="level2">
<h2 class="anchored" data-anchor-id="historical-context-of-historical-linguistics">Historical context of historical linguistics</h2>
<p>This first part is probably way too much information, but for the full context, here you go.</p>
<section id="european-exploration" class="level3">
<h3 class="anchored" data-anchor-id="european-exploration">European Exploration</h3>
<p>After “la Reconquista” in Spain and Portugal in the late 1400’s, the Ummayad Caliphate was kicked out from the Iberian peninsula. So, the Spanish and Portuguese Catholics made boats and set sail, to try to become rich. This is why the year Colombus accidentally reached the Americas is the same year that “la Reconquista” finished.</p>
<p>After the Spanish and the Portuguese made sailing around the world popular, other Europeans joined in as well, like the Italians, the British, the Dutch, and the French. The thing that all these Europeans had in common is that they all spoke Indo-European languages.</p>
<p>All the Europeans mainly sought after India, as well as nearby places like Southeast Asia, to get some spices. However, there was one major problem with this: the Ottoman Empire occupied Turkiye as well as much of the area around it, and they didn’t let anyone cross; even if they did, they couldn’t cross by boat, since the Suez Canal hadn’t been invented yet. So, they had to sail all the way around Africa, which I doubt anyone these days would have the patience to do.</p>
</section>
<section id="the-discovery-of-indo-european-languages" class="level3">
<h3 class="anchored" data-anchor-id="the-discovery-of-indo-european-languages">The discovery of Indo-European languages</h3>
<p>Upon finally reaching India, many Europeans noticed similarities between the local Indian languages and their own European languages. You can also see this yourself - the Hindu god of fire’s name is “Agni”, and in English, we have the word “ignite”. “Ignite” is from Latin, which means the mostly Romance-speaking Europeans were likely able to notice this with Indian languages. This is where the concept of <em>cognates</em> came from - words in different languages that have a common ancestor.</p>
<p>Observations like these led the Europeans to hypothesize that all ancient European languages like Latin or Greek came from Sanskrit. At this point, the Europeans were very confused. They used to think that all languages were descended from Hebrew. Lots of fringe theories emerged from the discovery of Indo-European languages, like the idea that Germanic tribes were from Persia. I will probably talk about these theories in a future post, but for now, let’s just say that they would all make you want to cringe.</p>
<p>Finally, a linguist from Germany <a href="https://en.wikipedia.org/wiki/Franz_Bopp">Franz Bopp</a> figured out that Sanskrit, Latin, Greek, and many other languages were all descended from a common ancestor language, which he called “Proto-Indo-European”. To do this, he invented the comparative method, which is what we will talk about in the next part.</p>
<p>The modern Indo-European language family tree is shown below. As you can see from how complicated it is, Indo-European is the most documented and studied language family, and it’s also quite widespread, which is why other language family trees don’t have the same level of detail.</p>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><a href="ie.png" class="lightbox" data-gallery="quarto-lightbox-gallery-1" title="Indo-European language family tree"><img src="https://vaishnavs.net/posts/Historical-Linguistics-1/ie.png" class="img-fluid figure-img" alt="Indo-European language family tree"></a></p>
<figcaption>Indo-European language family tree</figcaption>
</figure>
</div>
<p>The original image is from <a href="https://www.worldhistory.org/image/1028/indo-european-language-family-tree/">here</a>.</p>
</section>
</section>
<section id="warning-about-cognates" class="level2">
<h2 class="anchored" data-anchor-id="warning-about-cognates">Warning About Cognates</h2>
<p>You have to be really careful about cognates, because it could either be that the words really are similar and semantically related, they are false friends (which means that the words just coincidentally sound similar but don’t have a common ancestor), or they are loanwords, which means that one language borrowed the word from another, but this does not imply relatedness or ancestry.</p>
<p>An example of loanwords is when Korean uses “keikeu” for “cake”, but this doesn’t mean that Korean is a Germanic language; instead, it just means that Korean had to borrow from English because they didn’t have a word for “cake” before and they were exposed to Anglophone culture.</p>
<p>False friends are also especially sneaky. If you told a German friend “Ich will dir Gift geben”, which you think means “I want to give you gifts”, they would probably stop being friends with you and even call the authorities on you, because “Gift” in German means “poison”, and has no relation to the English word “gift”.</p>
</section>
<section id="sound-changes" class="level2">
<h2 class="anchored" data-anchor-id="sound-changes">Sound Changes</h2>
<p>To understand the comparative method that will be covered in the next part, we need to first understand sound changes. For example, the word for “water” in Latin is “aqua”, but in French, which is descended from it, it’s “eau”. We know that “eau” and “aqua” are cognates, because “eau” isn’t a loanword and it isn’t gibberish. How could sound changes have caused this to happen?</p>
<p>The main idea is that the /kʷ/ in “aqua” gradually turned into a /w/, since the /k/ sound got weakened, so it sounded more like /awa/. After that, the /w/ sound got weakened as well, and it sounded more like /au/. Finally, the /au/ sound got weakened to /o/, which is how we got “eau” (French also preserves its older spelling, which means at one point it really did used to sound something like “eeyeawoo”).</p>
<p>These sound changes are pretty regular in a single language or language family, and at least have patterns cross-linguistically. For example, it’s more likely for a /tʃ/ to emerge from a /t/ that is near an /i/ or a /j/ than the other way around, because of a trend called palatalization, which is why in Portuguese, the word for “milk” is “leite”, but is pronouned “leiche” (Portuguese preserves historical spelling like French does).</p>
<p>One of the most famous sound changes is Grimm’s law. It states that in Germanic languages, the /p/ sound that is found in other Indo-European languages turned into an /f/ sound, the /t/ sound was turned into a /θ/ sound, and the /k/ sound was turned into an /h/ sound. That’s why in English, we say “father”, “three”, and “heart”, while in the Vatican, Latin speakers say “pater”, “tres”, and “cor”.</p>
<p>There are certain properties about sound changes. They have no exception (a certain rule must apply everywhere in that environment) and they ignore grammar.</p>
<p>Sound changes can also be conditioned or unconditioned. Conditioned means that a sound turns into another sound only in certain environments, while unconditioned means that the sound changes no matter what environment it is in.</p>
</section>
</section>
<section id="to-be-continued" class="level1">
<h1>To be continued</h1>
<p>So we know how people discovered that languages were related. We also know how sound changes and cognates work. How did early linguists use this to figure out Proto-Indo-European, and use this same method for other proto languages? That’s what we will talk about in the next post.</p>


</section>

 ]]></description>
  <category>Linguistics</category>
  <guid>https://vaishnavs.net/posts/Historical-Linguistics-1/</guid>
  <pubDate>Wed, 28 Jan 2026 18:30:00 GMT</pubDate>
  <media:content url="https://vaishnavs.net/posts/Historical-Linguistics-1/ie.png" medium="image" type="image/png" height="143" width="144"/>
</item>
<item>
  <title>Why Pi is not, in fact, equal to 4</title>
  <dc:creator>Vaishnav Sudarshan</dc:creator>
  <link>https://vaishnavs.net/posts/Why Pi Is Not 4/</link>
  <description><![CDATA[ 





<section id="yapping" class="level1">
<h1>Yapping</h1>
<p><img src="https://latex.codecogs.com/png.latex?2025"> is over! That was a once in a lifetime year. It was a perfect square, and the next one will come in <img src="https://latex.codecogs.com/png.latex?2116">. Yet even that is not very cool number, because who cares about the square of <img src="https://latex.codecogs.com/png.latex?46">? <img src="https://latex.codecogs.com/png.latex?45"> is a much nicer number than that. <img src="https://latex.codecogs.com/png.latex?45"> is a triangular number (sum of the first nine positive integers in this case), so <img src="https://latex.codecogs.com/png.latex?2025"> is the square of this triangular number, which you may recall also means it’s the sum of the first nine cubes.</p>
<p><img src="https://latex.codecogs.com/png.latex?%0A%5Csum_%7Bi=1%7D%5E%7Bn%7D%20i%5E3%20=%20%5Cfrac%7Bn%5E2%20(n-1)%5E2%7D%7B4%7D%20=%20%5Cleft%5B%5Cfrac%7Bn(n-1)%7D%7B2%7D%5Cright%5D%5E2%20=%20%5Cleft(%5Csum_%7Bi=1%7D%5E%7Bn%7D%20i%5Cright)%5E2.%0A"></p>
<p>Also, since <img src="https://latex.codecogs.com/png.latex?2025"> is the square of <img src="https://latex.codecogs.com/png.latex?45">, it’s the sum of the first <img src="https://latex.codecogs.com/png.latex?45"> odd numbers.</p>
<p><img src="https://latex.codecogs.com/png.latex?2026">, on the other hand, is unbelievably boring. Its prime factorization is literally just <img src="https://latex.codecogs.com/png.latex?2%5Ccdot%201013">. So, for the first CPOTM of the year, I’ll try to make <img src="https://latex.codecogs.com/png.latex?2026"> more interesting by writing a disproof instead of a proof.</p>
<p>If you’ve seen it, then sorry. If not, here it is:</p>
<p>If you take a square of side length <img src="https://latex.codecogs.com/png.latex?r"> and then keep on cutting the corners so you preserve the perimeter <img src="https://latex.codecogs.com/png.latex?8r">, but the shape approaches a circle, then why can’t you say that <img src="https://latex.codecogs.com/png.latex?%5Cpi%20=%204">, because the diameter is <img src="https://latex.codecogs.com/png.latex?2r">?</p>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><a href="img.png" class="lightbox" data-gallery="quarto-lightbox-gallery-1" title="The fake proof"><img src="https://vaishnavs.net/posts/Why Pi Is Not 4/img.png" class="img-fluid figure-img" alt="The fake proof"></a></p>
<figcaption>The fake proof</figcaption>
</figure>
</div>
</section>
<section id="solution" class="level1">
<h1>Solution</h1>
<p>It seems correct, doesn’t it? The area certainly converges, because after cutting off the corners over and over again, you get the same infinitesimal rectangles that could integrate just like a normal circle to get the same result.</p>
<p>The problem is that the perimeter doesn’t converge. The arc length of a curve from <img src="https://latex.codecogs.com/png.latex?t=a"> to <img src="https://latex.codecogs.com/png.latex?t=b"> where <img src="https://latex.codecogs.com/png.latex?x"> and <img src="https://latex.codecogs.com/png.latex?y"> are both functions of <img src="https://latex.codecogs.com/png.latex?t"> is given by <img src="https://latex.codecogs.com/png.latex?%0A%5Cint_a%5Eb%20%5Csqrt%7B(%5Cfrac%7Bdx%7D%7Bdt%7D)%5E2+(%5Cfrac%7Bdy%7D%7Bdt%7D)%5E2%7D%20dt%0A"></p>
<p>This is NOT the same as <img src="https://latex.codecogs.com/png.latex?x(b)-x(a)+y(b)-y(a)">.</p>
<p>Are you still not convinced that the perimeter doesn’t converge? Zoom in on an infinitesimal piece of the diagram, which is where the arc length of the circle is basically a line.</p>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><a href="zoom.png" class="lightbox" data-gallery="quarto-lightbox-gallery-2" title="When you zoom in to a single tiny step, ignoring nearby steps and exaggerating the nearby curvature so you can see it’s still a circle"><img src="https://vaishnavs.net/posts/Why Pi Is Not 4/zoom.png" class="img-fluid figure-img" alt="When you zoom in to a single tiny step, ignoring nearby steps and exaggerating the nearby curvature so you can see it’s still a circle"></a></p>
<figcaption>When you zoom in to a single tiny step, ignoring nearby steps and exaggerating the nearby curvature so you can see it’s still a circle</figcaption>
</figure>
</div>
<p>In an infinitesimal piece, the limiting process just turns the square into a staircase-like shape, say of <img src="https://latex.codecogs.com/png.latex?x">-length <img src="https://latex.codecogs.com/png.latex?dx"> and <img src="https://latex.codecogs.com/png.latex?y">-length <img src="https://latex.codecogs.com/png.latex?dy">. On a tiny “step”, the perimeter is just <img src="https://latex.codecogs.com/png.latex?dx+dy">. However, that tiny part of the circle is just a line that goes through the endpoints of the step, so the perimeter is <img src="https://latex.codecogs.com/png.latex?%5Csqrt%7Bdx%5E2+dy%5E2%7D">.</p>
<p>You might argue that maybe we should zoom in even more, and the snapshot we took wasn’t the true final result. However, the arc of the circle is already basically a line. By cornering in the square even more, you’re just going to get another line going through a step, and the situation won’t change, so we have, in fact, zoomed in enough. To actually make the square match the circle in its perimeter, we must directly make the horizontal and vertical lines turn into diagonal lines, which changes the perimeter. <img src="https://latex.codecogs.com/png.latex?%5Cblacksquare"></p>


</section>

 ]]></description>
  <category>Math</category>
  <guid>https://vaishnavs.net/posts/Why Pi Is Not 4/</guid>
  <pubDate>Wed, 31 Dec 2025 18:30:00 GMT</pubDate>
  <media:content url="https://vaishnavs.net/posts/Why Pi Is Not 4/img.png" medium="image" type="image/png" height="107" width="144"/>
</item>
<item>
  <title>Why would anyone in their right mind do it like this?</title>
  <dc:creator>Vaishnav Sudarshan</dc:creator>
  <link>https://vaishnavs.net/posts/Cool-Problem-of-the-Month2/</link>
  <description><![CDATA[ 





<section id="yapping" class="level1">
<h1>Yapping</h1>
<p>I recently have had the hobby of going through past AMC and AIME problems and trying to see if I could think of any goofy solution that’s not on the list of solutions on the AoPS wiki.</p>
<p>For one problem in particular, 2023 AMC 10B #7 (yeah, it’s still in the single digits), I found a diabolical solution that no one would have wanted to waste their brain cells to completely formulate. It is super easy to do just using 4th grade knowledge of geometry, but when I see rotations in geometry, I immediately think of complex bashing.</p>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><a href="Screenshot 2025-12-18 205740.png" class="lightbox" data-gallery="quarto-lightbox-gallery-1" title="The problem with answer choices"><img src="https://vaishnavs.net/posts/Cool-Problem-of-the-Month2/Screenshot 2025-12-18 205740.png" class="img-fluid figure-img" alt="The problem with answer choices"></a></p>
<figcaption>The problem with answer choices</figcaption>
</figure>
</div>
<p>I actually wrote this solution on AoPS wiki last month, but this crazy backstory deserves its own post for Cool Problem of the Month, and November was already taken. See the solution I wrote <a href="https://artofproblemsolving.com/wiki/index.php?title=2023_AMC_10B_Problems/Problem_7#Solution_7_(Overkill_complex_bash)">here</a>.</p>
<p>I tried to reword or explain some of the solution a bit more in depth, so you can rest assured that I didn’t just plainly plagiarize myself.</p>
<p>The complex and trig bashing itself isn’t even bad. If the problem was at least in the double digits, it would likely have been perfectly acceptable to complex bash and then trig bash. However, for a question #7, I’m probably going to be socially ostracized for having done so, especially when a nine year old obsessed with Tung Tung Tung Sahur can beat you to it.</p>
<p>Without further ado, here is the solution.</p>
</section>
<section id="solution" class="level1">
<h1>Solution</h1>
<p>Let the center of the square be the origin of the complex plane. Since we only care about angles, and not sides, we can assume WLOG that <img src="https://latex.codecogs.com/png.latex?A"> is at the point <img src="https://latex.codecogs.com/png.latex?-1+i">. To rotate a complex number clockwise by an angle <img src="https://latex.codecogs.com/png.latex?%5Ctheta">, just multiply the number by <img src="https://latex.codecogs.com/png.latex?e%5E%7B-i%20%5Ctheta%7D">, so then we end up decreasing the argument (angle measured counterclockwise from the x-axis) by <img src="https://latex.codecogs.com/png.latex?%5Ctheta"> while preserving the magnitude. In this case <img src="https://latex.codecogs.com/png.latex?%5Ctheta%20=%2020%5E%7B%5Ccirc%7D">.</p>
<p>So, the point <img src="https://latex.codecogs.com/png.latex?A'"> is at <img src="https://latex.codecogs.com/png.latex?%0A(-1+i)(e%5E%7B-i%2020%5E%7B%5Ccirc%7D%7D)%20=%20(-1+i)(%5Ccos(%20-%2020%5E%7B%5Ccirc%7D)%20+%20i%20%5Csin(%20-%2020%5E%7B%5Ccirc%7D))%0A"> from Euler’s formula (the exponential form is just my shorthand way of remembering how to rotate complex numbers, but you could just go straight to polar form).</p>
<p>Since cosine is an even function and sine is odd, this is the same as: <img src="https://latex.codecogs.com/png.latex?%0A(-1+i)(%5Ccos(20%5E%7B%5Ccirc%7D)%20-%20i%20%5Csin(20%5E%7B%5Ccirc%7D))%0A">.</p>
<p>This expands to <img src="https://latex.codecogs.com/png.latex?%0A(-%5Ccos(20%5E%7B%5Ccirc%7D)%20+%20%5Csin(20%5E%7B%5Ccirc%7D))%20+%20i(%5Ccos(20%5E%7B%5Ccirc%7D)%20+%20%5Csin(20%5E%7B%5Ccirc%7D)).%0A"></p>
<p>The angle we want to find is just the direction of the vector from <img src="https://latex.codecogs.com/png.latex?A"> to <img src="https://latex.codecogs.com/png.latex?A'">. So, this is just</p>
<p><img src="https://latex.codecogs.com/png.latex?%0A%5Carctan%5Cleft(%5Cfrac%7B%5CDelta%20%5CIm%7D%7B%5CDelta%20%5CRe%7D%5Cright).%0A"> <img src="https://latex.codecogs.com/png.latex?%0A%5CDelta%20%5CIm%20=%20%5Ccos(20%5E%7B%5Ccirc%7D)%20+%20%5Csin(20%5E%7B%5Ccirc%7D)%20-%201%0A">, while: <img src="https://latex.codecogs.com/png.latex?%0A%5CDelta%20%5CRe%20=%20-%5Ccos(20%5E%7B%5Ccirc%7D)%20+%20%5Csin(20%5E%7B%5Ccirc%7D)%20+%201%0A">.</p>
<p>Essentially, the problem is just boiled down to finding out how to trig bash <img src="https://latex.codecogs.com/png.latex?%0A%5Carctan%5Cleft(%5Cfrac%7B%5Ccos(20%5E%7B%5Ccirc%7D)%20+%20%5Csin(20%5E%7B%5Ccirc%7D)%20-%201%7D%7B-%5Ccos(20%5E%7B%5Ccirc%7D)%20+%20%5Csin(20%5E%7B%5Ccirc%7D)%20+%201%7D%5Cright).%0A"></p>
<p>There is an identity that: <img src="https://latex.codecogs.com/png.latex?%0A%5Ccos(A)+%5Csin(A)=%5Csqrt%7B2%7D%5Csin(A+45%5E%7B%5Ccirc%7D)%0A"> and <img src="https://latex.codecogs.com/png.latex?%0A%5Ccos(A)-%5Csin(A)=%5Csqrt%7B2%7D%5Ccos(A+45%5E%7B%5Ccirc%7D).%0A"></p>
<blockquote class="blockquote">
<p>I’ll leave it as an exercise to the reader to verify that.</p>
</blockquote>
<p>So, if we use this as well as the fact that <img src="https://latex.codecogs.com/png.latex?%5Csin(90%5E%5Ccirc%20-%20x)%20=%20%5Ccos(x)">, the fraction simplifies to</p>
<p><img src="https://latex.codecogs.com/png.latex?%0A-%20%5Cfrac%7B%5Csqrt%7B2%7D%20%5Ccos(25%5E%5Ccirc)-1%7D%7B%5Csqrt%7B2%7D%20%5Csin(25%5E%5Ccirc)-1%7D%0A">.</p>
<p>Substituting <img src="https://latex.codecogs.com/png.latex?%0A%5Csqrt%7B2%7D=%5Cfrac%7B1%7D%7B%5Ccos(45%5E%5Ccirc)%7D%0A"> , this simplifies to <img src="https://latex.codecogs.com/png.latex?%0A-%20%5Cfrac%7B%5Ccos(25%5E%5Ccirc)-%5Ccos(45%5E%5Ccirc)%7D%7B%5Csin(25%5E%5Ccirc)-%5Ccos(45%5E%5Ccirc)%7D%20=%20-%20%5Cfrac%7B%5Ccos(25%5E%5Ccirc)-%5Ccos(45%5E%5Ccirc)%7D%7B%5Csin(25%5E%5Ccirc)-%5Csin(45%5E%5Ccirc)%7D.%0A"></p>
<p>Finally, there is an identity that <img src="https://latex.codecogs.com/png.latex?%0A%5Ccos(A)-%5Ccos(B)=-2%5Csin%5Cleft(%5Cfrac%7BA+B%7D%7B2%7D%5Cright)%5Csin%5Cleft(%5Cfrac%7BA-B%7D%7B2%7D%5Cright)%0A"> and that <img src="https://latex.codecogs.com/png.latex?%0A%5Csin(A)-%5Csin(B)=2%5Ccos%5Cleft(%5Cfrac%7BA+B%7D%7B2%7D%5Cright)%5Csin%5Cleft(%5Cfrac%7BA-B%7D%7B2%7D%5Cright)%0A">.</p>
<blockquote class="blockquote">
<p>Again, verifying it is an exercise for the reader.</p>
</blockquote>
<p>We now have <img src="https://latex.codecogs.com/png.latex?%0A-%20%5Cfrac%7B2%20%5Ccdot%20%5Csin(35%5E%5Ccirc)%20%5Ccdot%20%5Csin(10%5E%5Ccirc)%7D%7B-2%20%5Ccdot%20%5Ccos(35%5E%5Ccirc)%20%5Ccdot%20%5Ccos(10%5E%5Ccirc)%7D%20=%20%5Ctan(35%5E%5Ccirc)%0A"> So <img src="https://latex.codecogs.com/png.latex?%0A%5Carctan(%5Ctan(35%5E%5Ccirc))%20=%20%5Cboxed%7B35%5E%5Ccirc%7D%0A"> or option <img src="https://latex.codecogs.com/png.latex?B">.</p>
</section>
<section id="conclusion" class="level1">
<h1>Conclusion</h1>
<p>So that’s how to NOT solve a really simple problem! Please don’t do something like this!</p>


</section>

 ]]></description>
  <category>Math</category>
  <guid>https://vaishnavs.net/posts/Cool-Problem-of-the-Month2/</guid>
  <pubDate>Mon, 15 Dec 2025 18:30:00 GMT</pubDate>
  <media:content url="https://vaishnavs.net/posts/Cool-Problem-of-the-Month2/Screenshot%202025-12-18%20205740.png" medium="image" type="image/png"/>
</item>
<item>
  <title>Abstract Derivatives Part 1 - Linear Operators</title>
  <dc:creator>Vaishnav Sudarshan</dc:creator>
  <link>https://vaishnavs.net/posts/Abstract Derivatives Part 1/</link>
  <description><![CDATA[ 





<section id="linear-operators" class="level1">
<h1>Linear Operators</h1>
<p>A linear operator <img src="https://latex.codecogs.com/png.latex?L"> is just anything that satisfies <img src="https://latex.codecogs.com/png.latex?L(ax+by)=aL(x)+bL(y)">, for constants <img src="https://latex.codecogs.com/png.latex?a"> and <img src="https://latex.codecogs.com/png.latex?b">, and where addition and multiplication are defined. In other words, it is additive, and you can pull out constants from the inside.</p>
<p>Matrices are where you probably saw this. If you transform a vector <img src="https://latex.codecogs.com/png.latex?x"> by multiplying it with <img src="https://latex.codecogs.com/png.latex?A">, do the same for a vector <img src="https://latex.codecogs.com/png.latex?y">, and add the two new vectors, it’s the same as just adding them first and then transforming them. Also, if you scale <img src="https://latex.codecogs.com/png.latex?x"> and <img src="https://latex.codecogs.com/png.latex?y"> by some constants, it doesn’t matter if you did it before or after the transformation.</p>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><a href="linoper.png" class="lightbox" data-gallery="quarto-lightbox-gallery-1" title="Diagram showing the constants rule of linear transformations"><img src="https://vaishnavs.net/posts/Abstract Derivatives Part 1/linoper.png" class="img-fluid figure-img" alt="Diagram showing the constants rule of linear transformations"></a></p>
<figcaption>Diagram showing the constants rule of linear transformations</figcaption>
</figure>
</div>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><a href="linoper1.png" class="lightbox" data-gallery="quarto-lightbox-gallery-2" title="Diagram showing additivity of linear transformations"><img src="https://vaishnavs.net/posts/Abstract Derivatives Part 1/linoper1.png" class="img-fluid figure-img" alt="Diagram showing additivity of linear transformations"></a></p>
<figcaption>Diagram showing additivity of linear transformations</figcaption>
</figure>
</div>
</section>
<section id="derivatives-as-linear-opexxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qsxwrators" class="level1">
<h1>Derivatives As Linear Opexxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qa1qsxwrators</h1>
<p>Do you remember the sum and product rules of single-variable derivatives? 1qsaxwxq <img src="https://latex.codecogs.com/png.latex?%5Cfrac%7Bd%7D%7Bdx%7D%20(af(x))%20=%20a%20%5Cfrac%7Bd%7D%7Bdx%7D%20f(x)"> <img src="https://latex.codecogs.com/png.latex?%5Cfrac%7Bd%7D%7Bdx%7D%20(f(x)%20+%20g(x))%20=%20%5Cfrac%7Bd%7D%7Bdx%7D%20f(x)%20+%20%5Cfrac%7Bd%7D%7Bdx%7D%20g(x)"></p>
<p>Wait, what??? Differentiation is also a linear operator on functions??? Now you realize how cool generalizing stuff is.</p>
<p>Hold on. Is <img src="https://latex.codecogs.com/png.latex?y=mx+b"> linear on <img src="https://latex.codecogs.com/png.latex?x">, for <img src="https://latex.codecogs.com/png.latex?b%20%5Cneq%200">? The answer, surprisingly, is no. <img src="https://latex.codecogs.com/png.latex?m(x_1+x_2)+b%20%5Cneq%20(mx_1+b)+(mx_2+b)">. Linear, in this the context of this blog post, doesn’t necessarily mean the function is a line, but rather that the function behaves like a linear operator, which are typically different things. However, don’t think this form of function isn’t useful outside of 7th grade - when generalized to matrices, these can be very useful in AI.</p>
<section id="slight-tangent-on-affine-transformations" class="level2">
<h2 class="anchored" data-anchor-id="slight-tangent-on-affine-transformations">Slight Tangent on Affine Transformations</h2>
<p>Transformations of the form <img src="https://latex.codecogs.com/png.latex?y=mx+b"> aren’t linear, but instead <em>affine</em>. Obviously not everything has to be a scalar, but instead can be about vectors and matrices where you have <img src="https://latex.codecogs.com/png.latex?f(%5Cvec%7Bv%7D)%20=%20A%20%5Cvec%7Bv%7D%20+%20%5Cvec%7Bb%7D"> for some matrix <img src="https://latex.codecogs.com/png.latex?A">. Where are affine transformations actually used?</p>
<p>A really common example is to get from one layer of a neural network to another, right before the activation function (more on that in the <a href="../Neural-Networks-Part1/">blog about neural networks</a>). You multiply the vector of inputs in one layer by the matrix of weights and add to that the vector of biases to get the next layer pre-activation.</p>
</section>
</section>
<section id="to-be-continued" class="level1">
<h1>To be continued</h1>
<p>Well, this was not very abstract… yet. In the following parts, we will actually make derivatives more abstract, but this one was just the setup. So, don’t leave just yet.</p>


</section>

 ]]></description>
  <category>Math</category>
  <guid>https://vaishnavs.net/posts/Abstract Derivatives Part 1/</guid>
  <pubDate>Sat, 22 Nov 2025 18:30:00 GMT</pubDate>
</item>
<item>
  <title>Abstract Derivatives Part 2 - Multivariable and Beyond</title>
  <dc:creator>Vaishnav Sudarshan</dc:creator>
  <link>https://vaishnavs.net/posts/Abstract Derivatives Part 2/</link>
  <description><![CDATA[ 





<section id="making-derivatives-more-abstract" class="level1">
<h1>Making Derivatives More Abstract</h1>
<p>For single variable functions, we have a scalar in and a scalar out (one input, one output). You could technically think of it as 1D vectors, as we’ll do soon, but it’s basically the same thing.</p>
<p>The main thing we want to emphasize here is that for the derivative, we write it as differentials (<img src="https://latex.codecogs.com/png.latex?df%20=%20f'(x)%20dx">) instead of <img src="https://latex.codecogs.com/png.latex?%5Cfrac%7Bdf%7D%7Bdx%7D">. In scalar functions, that works, but later on, it won’t make much sense to divide by a vector or a matrix.</p>
<p>Derivatives, however, aren’t just limited to acting on single-variables to be linear operators. Here are some other types of derivatives.</p>
<section id="multivariable-functions" class="level2">
<h2 class="anchored" data-anchor-id="multivariable-functions">Multivariable Functions</h2>
<p>For multivariable functions, we have many inputs in and one output out, where each input or output is a number. However, one interpretation of a vector is a list of numbers, so one could think of it as a vector in and a scalar out. What this means is that, for a 2D input space, <img src="https://latex.codecogs.com/png.latex?f(%5Cvec%7Bx%7D)%20=%20f(x,%20y)">. For any point, or vector, on the 2D <img src="https://latex.codecogs.com/png.latex?xy"> plane, there is a <img src="https://latex.codecogs.com/png.latex?z"> coordinate corresponding to that, to form some sort of surface.</p>
<p>Again, what we basically just mean in this case is that a vector has two or more dimensions, and a scalar has just one. If we think of a list of numbers as a vector, then we can do vector operations on it, but if we think of a single number as a vector, doing vector operations on it wouldn’t make a difference.</p>
<p>As for the derivative? It’s a vector, known as the gradient! It is the vector of partial derivatives with respect to each variable. The gradient will always have the same “shape” as the input space, because it also represents the direction of steepest ascent. It’s written as <img src="https://latex.codecogs.com/png.latex?%5Cnabla%20f%20=%20%5B...%5Cfrac%7B%5Cpartial%20f%7D%7B%5Cpartial%20x_i%7D...%5D">, where <img src="https://latex.codecogs.com/png.latex?x_i"> is each component in the input.</p>
<section id="slight-tangent-on-gradient-descent" class="level3">
<h3 class="anchored" data-anchor-id="slight-tangent-on-gradient-descent">Slight Tangent on Gradient Descent</h3>
<p>Why? Because think about this way: in differential form, we can write <img src="https://latex.codecogs.com/png.latex?df%20=%20%5CSigma%20%7B(%5Cfrac%7B%5Cpartial%20f%7D%7B%5Cpartial%20x_i%7D%20dx_i)%7D">. Oh, the sum of the corresponding products? Reminds me of dot product! We can write this as <img src="https://latex.codecogs.com/png.latex?df%20=%20%5Cnabla%20f%20%5Ccdot%20%5Cvec%7Bdx%7D">. In terms of magnitudes, it can also be written as <img src="https://latex.codecogs.com/png.latex?df%20=%20%7C%5Cnabla%20f%7C%20%7Cd%5Cvec%7Bx%7D%7C%20%5Ccos(%5Ctheta)">. We can’t really do much with the given magnitudes to maximize <img src="https://latex.codecogs.com/png.latex?df">.</p>
<p>At a particular input point <img src="https://latex.codecogs.com/png.latex?%5Cvec%7Bx%7D">, the magnitude of <img src="https://latex.codecogs.com/png.latex?%5Cnabla%20f"> is going to be some constant when we’re dealing with anything but that input point and the function. Also, the magnitude of <img src="https://latex.codecogs.com/png.latex?d%5Cvec%7Bx%7D"> can’t be dealt with because it’s an infinitesimal, not an actual number. So, the only thing we can do to maximize <img src="https://latex.codecogs.com/png.latex?df"> is the <img src="https://latex.codecogs.com/png.latex?%5Ccos(%5Ctheta)"> term. The maximum of <img src="https://latex.codecogs.com/png.latex?%5Ccos(%5Ctheta)"> is <img src="https://latex.codecogs.com/png.latex?1">, when <img src="https://latex.codecogs.com/png.latex?%5Ctheta%20=%200%5E%5Ccirc">. So, if <img src="https://latex.codecogs.com/png.latex?d%5Cvec%7Bx%7D"> is in the same direction as the gradient, the function increases the most.</p>
<p>Similarly, for <img src="https://latex.codecogs.com/png.latex?df"> to be as low as possible, we want <img src="https://latex.codecogs.com/png.latex?%5Ccos(%5Ctheta)"> to be at its minimum (<img src="https://latex.codecogs.com/png.latex?-1">), which is when <img src="https://latex.codecogs.com/png.latex?%5Ctheta%20=%20180%5E%5Ccirc">, or when we move in the opposite direction as the gradient. Now, it is guaranteed that <img src="https://latex.codecogs.com/png.latex?df%20%5Cleq%200">, because we’re dealing with just magnitudes (always nonnegative) times <img src="https://latex.codecogs.com/png.latex?-1">.</p>
<p>So, we can do some local linearization. If we have some random point <img src="https://latex.codecogs.com/png.latex?%5Cvec%7Bx%7D,%20f(%5Cvec%7Bx%7D)">, we can change <img src="https://latex.codecogs.com/png.latex?%5Cvec%7Bx%7D"> by some small vector in the opposite direction of <img src="https://latex.codecogs.com/png.latex?%5Cnabla%20f">. Where do we get that small vector? First, we normalize <img src="https://latex.codecogs.com/png.latex?-%5Cnabla%20f"> by dividing by its magnitude to get a unit vector. Then, to scale it so that our local linearization approximation isn’t horrendous, we multiply this vector by a small scalar <img src="https://latex.codecogs.com/png.latex?%5Cmu">, known as the <em>learning step</em>. We subtract add this to the original <img src="https://latex.codecogs.com/png.latex?%5Cvec%7Bx%7D">, and recalculate <img src="https://latex.codecogs.com/png.latex?f(%5Cvec%7Bx%7D)">.</p>
<p>When training neural networks, this is the best way to find a local minimum. Even though the absolute minimum is better, the computations to do that would cost way more money.</p>
</section>
</section>
<section id="vector-valued-functions" class="level2">
<h2 class="anchored" data-anchor-id="vector-valued-functions">Vector-Valued Functions</h2>
<p>What about a vector output for a scalar input? This could be represented as a parametric equation, and the derivative would also be a vector. An example of this is in physics, with velocity and acceleration, both as a function of time. See the diagram for these in circular motion.</p>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><a href="circular.png" class="lightbox" data-gallery="quarto-lightbox-gallery-1" title="Diagram showing the vector-valued functions of velocity and acceleration during circular motion"><img src="https://vaishnavs.net/posts/Abstract Derivatives Part 2/circular.png" class="img-fluid figure-img" alt="Diagram showing the vector-valued functions of velocity and acceleration during circular motion"></a></p>
<figcaption>Diagram showing the vector-valued functions of velocity and acceleration during circular motion</figcaption>
</figure>
</div>
<p>To demonstrate where more abstract derivatives can be used in this case, we can use parametric equations. Let the counterclockwise angle above the horizontal of the particle moving in a circle be <img src="https://latex.codecogs.com/png.latex?%5Ctheta">, and the radius be <img src="https://latex.codecogs.com/png.latex?r">. From components, the direction of the position of the particle from the center is <img src="https://latex.codecogs.com/png.latex?%5B%5Ccos(%5Ctheta),%20%5Csin(%5Ctheta)%5D">. Then, from geometry, since motion is perpendicular to the radius, the horizontal component of velocity (assuming constant speed <img src="https://latex.codecogs.com/png.latex?v">) is <img src="https://latex.codecogs.com/png.latex?-v%20%5Csin(%5Ctheta)">, and the vertical component is <img src="https://latex.codecogs.com/png.latex?v%20%5Ccos(%5Ctheta)">. Given that <img src="https://latex.codecogs.com/png.latex?%5Comega%20=%20d%5Ctheta/dt"> and <img src="https://latex.codecogs.com/png.latex?v=%5Comega%20r">, try to prove for yourself that the centripetal acceleration must have magnitude <img src="https://latex.codecogs.com/png.latex?%5Cfrac%7Bv%5E2%7D%7Br%7D"> and point towards the center! The full solution is in my <a href="../Circular Motion/"><em>blog post about circular motion</em></a>.</p>
</section>
<section id="vector-fields" class="level2">
<h2 class="anchored" data-anchor-id="vector-fields">Vector Fields</h2>
<p>At this point, we are exiting the more basic types of functions, and finally, matrices come into use here. You may recall that a vector field is a kind of function where for every point (vector) in space, there is an output which is a vector that moves that input somewhere else. As a result, what we can get by reiterating this process can be modeled for something like fluid flow. Maybe you’ve seen some of these diagrams before. Typically, since varying magnitudes get out of hand when drawn on paper, each point has a vector of a fixed length showing just direction, and the magnitudes are portrayed through color, where the “hotter” the color, the longer the magnitude is.</p>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><a href="vector_field.png" class="lightbox" data-gallery="quarto-lightbox-gallery-2" title="Diagram showing a vector field"><img src="https://vaishnavs.net/posts/Abstract Derivatives Part 2/vector_field.png" class="img-fluid figure-img" alt="Diagram showing a vector field"></a></p>
<figcaption>Diagram showing a vector field</figcaption>
</figure>
</div>
<p>The diagram even looks intuitive. At each point, it tells you where to go next, and by how much. Even if you had no idea about what vector fields are, that’s literally what is looks like.</p>
<p>The derivative is a matrix called the Jacobian. Each row is basically the gradient with respect to the entire input from each component of the output.</p>
<p>If you think of it as looking at each component of the input, the Jacobian is also the derivative of the entire output with respect to each input.</p>
<p>So, if the input space is a vector in <img src="https://latex.codecogs.com/png.latex?%5Cmathbb%7BR%7D%5En"> and the output space is a vector in <img src="https://latex.codecogs.com/png.latex?%5Cmathbb%7BR%7D%5Em">, the Jacobian is a matrix with dimensions <img src="https://latex.codecogs.com/png.latex?m%20%5Ctimes%20n">.</p>
<p>Now, the derivative can be written as <img src="https://latex.codecogs.com/png.latex?d%20%5Cvec%7Bf%7D%20=%20J%20d%20%5Cvec%7Bx%7D"> for the Jacobian <img src="https://latex.codecogs.com/png.latex?J">. Now, this looks like a proper matrix multiplication with no scalars involved apart from doing things component-wise.</p>
<p>One cool thing now is that if <img src="https://latex.codecogs.com/png.latex?J"> is a constant matrix, the vector field is just a normal linear transformation of <img src="https://latex.codecogs.com/png.latex?%5Cvec%7Bf%7D(%5Cvec%7Bx%7D)%20=%20J%20%5Cvec%7Bx%7D">, which is an interesting interpretation of linear transformations.</p>
</section>
</section>
<section id="conclusion" class="level1">
<h1>Conclusion</h1>
<p>So far, what we’ve seen is just seeing pretty simple derivatives with a new interpretation. Stay tuned for even more abstract derivatives, and how they relate to AI!</p>


</section>

 ]]></description>
  <category>Math</category>
  <category>AI</category>
  <guid>https://vaishnavs.net/posts/Abstract Derivatives Part 2/</guid>
  <pubDate>Sat, 22 Nov 2025 18:30:00 GMT</pubDate>
  <media:content url="https://vaishnavs.net/posts/Abstract Derivatives Part 2/circular.png" medium="image" type="image/png" height="178" width="144"/>
</item>
<item>
  <title>Nice Puzzle to Distract My Ice Skating</title>
  <dc:creator>Vaishnav Sudarshan</dc:creator>
  <link>https://vaishnavs.net/posts/Nice puzzle to distract my ice skating/</link>
  <description><![CDATA[ 





<section id="yap" class="level1">
<h1>Yap</h1>
<p><a href="aops.jpg" class="lightbox" data-gallery="quarto-lightbox-gallery-1" title="The problem I saw"><img src="https://vaishnavs.net/posts/Nice puzzle to distract my ice skating/aops.jpg" class="img-fluid" alt="The problem I saw"></a> I went ice skating today. I only go around once a year, which means I basically forget any progress I make in not looking like a monkey when I try each time. Just as I started to remotely get the hang of it for the third time in my life, I went to take a look at all the sponsors of the rink putting ads around it. One that caught my eye was, of course, from AoPS, which is what is shown on the image:</p>
<p>“Does this problem make your brain FREEZE? Combine plus signs and eight 8’s to get 1,000.”</p>
<p>While the problem was really simple just by brute forcing and intuition that even a six or seven year old (hehe) could solve it. The ad was, after all, placed to a general audience, not a bunch of orz IMO quals.</p>
<p>However, out of my annoyingness, I sought to prove rigorously that the answer I got was the only possible one. I did this in my head, closing any logic holes, while at the same time figuring out how to ice skate properly (at least I was getting better at moving continuously, but my center of mass was still all over the place, so I ended up looking like a monkey anyway, but at least I never fell in the entirety of the hour I was there). So, without further ado, here’s the solution:</p>
</section>
<section id="actual-solution" class="level1">
<h1>Actual Solution</h1>
<p>Assume there are <img src="https://latex.codecogs.com/png.latex?n"> numbers being added up. <img src="https://latex.codecogs.com/png.latex?1%20%5Cleq%20n%20%5Cleq%208">, since there are at most eight numbers, which means there is one per digit, and at least one number, which is when all the digits are in one number.</p>
<p>Now, we consider the sum mod <img src="https://latex.codecogs.com/png.latex?10">. Since all <img src="https://latex.codecogs.com/png.latex?n"> numbers have a units digit of <img src="https://latex.codecogs.com/png.latex?8"> as it’s the only possible digit, and they add up to <img src="https://latex.codecogs.com/png.latex?1000">, we get <img src="https://latex.codecogs.com/png.latex?8n%20%5Cequiv%200%20%5Cpmod%7B10%7D">. What this means is that <img src="https://latex.codecogs.com/png.latex?8n"> is a multiple of <img src="https://latex.codecogs.com/png.latex?10">, so it must also be a multiple of <img src="https://latex.codecogs.com/png.latex?5">, since <img src="https://latex.codecogs.com/png.latex?10"> is a multiple of <img src="https://latex.codecogs.com/png.latex?5">. Since <img src="https://latex.codecogs.com/png.latex?8"> is not a multiple of <img src="https://latex.codecogs.com/png.latex?5">, but <img src="https://latex.codecogs.com/png.latex?8n"> is a multiple of <img src="https://latex.codecogs.com/png.latex?5">, then <img src="https://latex.codecogs.com/png.latex?n"> must be a multiple of <img src="https://latex.codecogs.com/png.latex?5">. The only multiple of <img src="https://latex.codecogs.com/png.latex?5"> between <img src="https://latex.codecogs.com/png.latex?1"> and <img src="https://latex.codecogs.com/png.latex?8"> is <img src="https://latex.codecogs.com/png.latex?n%20=%205">. Therefore, we have five numbers being added up.</p>
<p>We know that the maximum possible number is <img src="https://latex.codecogs.com/png.latex?888">, because <img src="https://latex.codecogs.com/png.latex?8888"> is already greater than <img src="https://latex.codecogs.com/png.latex?1000">. If there are <img src="https://latex.codecogs.com/png.latex?2"> or more <img src="https://latex.codecogs.com/png.latex?888">’s being added up, then the sum is also over <img src="https://latex.codecogs.com/png.latex?1000">.</p>
<p>We wish to prove that there are not zero <img src="https://latex.codecogs.com/png.latex?888">’s either. Assume by contradiction that there actually are zero <img src="https://latex.codecogs.com/png.latex?888">’s, so the maximum possible number is just <img src="https://latex.codecogs.com/png.latex?88">. Now, the maximum possible sum is just <img src="https://latex.codecogs.com/png.latex?4%20%5Ccdot%2088"> which is far less than <img src="https://latex.codecogs.com/png.latex?1000"> (this is the maximum because every <img src="https://latex.codecogs.com/png.latex?88"> is the equivalent of adding eleven <img src="https://latex.codecogs.com/png.latex?8">’s). Also, to verify that in my head, instead of calculating, I just saw that <img src="https://latex.codecogs.com/png.latex?4%20%5Ccdot%2088%20%3C%204%20%5Ccdot%20100%20=%20400%20%3C%201000">. Therefore, there must be exactly one <img src="https://latex.codecogs.com/png.latex?888"> being added up.</p>
<p>We find the remaining four numbers must add up to <img src="https://latex.codecogs.com/png.latex?112">. We can do a similar process to find the number of <img src="https://latex.codecogs.com/png.latex?88">’s that must be present. If there are no <img src="https://latex.codecogs.com/png.latex?88">’s, then the maximum sum is <img src="https://latex.codecogs.com/png.latex?32">, not even close to <img src="https://latex.codecogs.com/png.latex?112">. However, if there are two or more <img src="https://latex.codecogs.com/png.latex?88">’s, then the sum is already over <img src="https://latex.codecogs.com/png.latex?112">. Therefore, there must be exactly one <img src="https://latex.codecogs.com/png.latex?88"> present.</p>
<p>Since there is exactly one <img src="https://latex.codecogs.com/png.latex?888"> and exactly one <img src="https://latex.codecogs.com/png.latex?88">, and there aren’t any higher possible numbers, the remaining three <img src="https://latex.codecogs.com/png.latex?8">’s are used with one <img src="https://latex.codecogs.com/png.latex?8"> per number, filling up the remaining three numbers needed.</p>
</section>
<section id="conclusion" class="level1">
<h1>Conclusion</h1>
<p>Therefore, the final sum is <img src="https://latex.codecogs.com/png.latex?%5Cfbox%7B888%20+%2088%20+%208%20+%208%20+%208%20=%201000%7D">. There are also <img src="https://latex.codecogs.com/png.latex?40"> different ways to rearrange that same equation and keep it true, because it’s <img src="https://latex.codecogs.com/png.latex?2%20%5Ccdot%20%5Cfrac%7B5!%7D%7B3!%7D"> (the <img src="https://latex.codecogs.com/png.latex?5!"> is to rearrange all the five numbers being added, the <img src="https://latex.codecogs.com/png.latex?3!"> is because we don’t care the order the individual <img src="https://latex.codecogs.com/png.latex?8">’s are in because it’s all the same, and the <img src="https://latex.codecogs.com/png.latex?2"> is to make the sum on the left hand side or the right hand side).</p>


</section>

 ]]></description>
  <category>Math</category>
  <category>Random</category>
  <guid>https://vaishnavs.net/posts/Nice puzzle to distract my ice skating/</guid>
  <pubDate>Fri, 21 Nov 2025 18:30:00 GMT</pubDate>
  <media:content url="https://vaishnavs.net/posts/Nice puzzle to distract my ice skating/aops.jpg" medium="image" type="image/jpeg"/>
</item>
<item>
  <title>Morphology</title>
  <dc:creator>Vaishnav Sudarshan</dc:creator>
  <link>https://vaishnavs.net/posts/Morphology/</link>
  <description><![CDATA[ 





<blockquote class="blockquote">
<p>This is a series of blogs on linguistics. See also: <a href="../Phonology/"><em>Phonology</em></a>, <a href="../Writing-Systems/"><em>Writing Systems</em></a>, <a href="../Phonetics/"><em>Phonetics</em></a></p>
</blockquote>
<section id="morphology" class="level1">
<h1>Morphology</h1>
<section id="confusing-introduction" class="level2">
<h2 class="anchored" data-anchor-id="confusing-introduction">Confusing Introduction</h2>
<p>Previously, in <a href="../../posts/Writing-Systems/index.html">orthographies</a>, <a href="../../posts/Phonology/index.html">phonology</a>, and <a href="../../posts/Phonetics/index.html">phonetics</a>, we’ve discussed <em>sounds</em> and their symbols. Now, we take a step further into <em>meaning</em>.</p>
<p>Now, I want to emphasize that GENERALLY, sound and meaning are two separate things. This should make sense if you think about it - the meaning of “meaning” is just the idea tied to that word, and the sound is how that word is pronounced. There is nothing about the voiced bilabial nasal /m/ or the closed front unrounded vowel /i/ that makes the word “meaning” tied to the idea of “the idea tied to that word”. Note to reader: I do not apologize for provding confusing examples like this.</p>
<p>It may appear that there are exceptions. For example, the “wh” in English commonly indicates an interrogative word, like the five that are commonly referenced - “who”, “what”, “why”, “where”, “when”. However, there’s nothing about the labiovelar approximant that is inherently tied to interrogative words. Instead, that was just an arbitrary sound that happened to evolve this way. Instead of calling the “w” and the “h” as <em>phonemes</em>, we would call “wh” a unit that evolved out of a <em>morpheme</em>.</p>
<section id="definition" class="level3">
<h3 class="anchored" data-anchor-id="definition">Definition</h3>
<p>A <em>morpheme</em> is loosely defined as a unit of meaning. You may wonder why we do not just use the term “words” to describe these. The answer is that “words” are quite hard to define - I mean, an app like Word or Google Docs might just measure the number of spaces and then add one, because that’s generally convenient in English, but what about something like Mandarin? Would every sentence in Mandarin be a single “word” because there aren’t any spaces? Such a question isn’t easy or even helpful. Therefore, we use morphemes instead.</p>
<p>Since sound and meaning are independent, if your English teacher ever uses something like alliteration or rhyme to analyze a literary text, now you know that such an analysis is completely bogus. However, another possiblity also exists - your teacher is imagining how that sound is pronounced, and the manner and difficulty could add some “insightful” meaning (by which I mean that it’s definitely not intended to be that deep, and any such annotation is surely a stretch).</p>
</section>
</section>
<section id="types-of-morphology-across-languages" class="level2">
<h2 class="anchored" data-anchor-id="types-of-morphology-across-languages">Types of Morphology Across Languages</h2>
<p>There are two continuums that determine how a language’s morphology works. The first measures how many morphemes are squished into a single word, and the second measures how clearly morphemes are separated.</p>
<p>These are usually talking about inflection, not derivation, which we will get to in part 2.</p>
<section id="spectrum-1" class="level3">
<h3 class="anchored" data-anchor-id="spectrum-1">Spectrum 1</h3>
<p>The first continuum ranges from one morpheme per word to multiple morphemes put together in a word to entire sentences fit in a word. In that order, the types of languages would be analytic, synthetic, and polysynthetic.</p>
<section id="analytic-languages" class="level4">
<h4 class="anchored" data-anchor-id="analytic-languages">Analytic languages</h4>
<p>Analytic languages would be something like Mandarin - the sentence “I don’t drink tea” would be “我不喝茶” (“Wǒ bù hē chá”). Each word is its own morpheme here. Purely analytic languages don’t rely on <em>inflection</em>, or altering the form of words - instead, they rely on <em>particles</em>, which are words that are put next to other words to c hange the grammatical meaning.</p>
<p>As a sidenote, Google Translate clearly agrees that each character is a word in this case, as shown here.</p>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><a href="translate.png" class="lightbox" data-gallery="quarto-lightbox-gallery-1" title="Shows how Google Translate separates words in Pinyin"><img src="https://vaishnavs.net/posts/Morphology/translate.png" class="img-fluid figure-img" alt="Shows how Google Translate separates words in Pinyin"></a></p>
<figcaption>Shows how Google Translate separates words in Pinyin</figcaption>
</figure>
</div>
</section>
<section id="synthetic-languages" class="level4">
<h4 class="anchored" data-anchor-id="synthetic-languages">Synthetic Languages</h4>
<p>Synthetic languages actually inflect more and rely less on particles. For example, Latin uses verb conjugations and noun declensions to reflect gender, number, case, person, and more. As a result, it doesn’t use articles, pronouns are optional, and there are less words in general. However, the entire sentence doesn’t get smushed together, and you can still tell apart subjects, verbs, and objects.</p>
</section>
<section id="polysynthetic-languages" class="level4">
<h4 class="anchored" data-anchor-id="polysynthetic-languages">Polysynthetic Languages</h4>
<p>Polysynthetic languages are like an extreme form of regular synthetic languages. A single word could contain the meaning of an entire sentence, combining morphemes of subjects, objects, and verbs. You may have seen super long words of some indigenous languages of the Eskimo-Aleut family in Greenland, Alaska, and Northern Canada (possibly on signs while playing GeoGuessr), and wondered what they were yapping. Now you know it’s not actual yap, just a normal sentence put together into a giant word.</p>
</section>
<section id="clarification-on-words" class="level4">
<h4 class="anchored" data-anchor-id="clarification-on-words">Clarification on “Words”</h4>
<p>But hold on, I thought words aren’t reliable measurements, so why do we use words here? Here, linguists use the practical working definition of a word, which is essentially something that makes sense being separated and independent. For example, morphemes like affixes would just be considered part of that word, but adjectives would be their own word (at least, that’s how English treats affixes and adjectives). So, it’s not purely based on how they’re written down, but there doesn’t necessarily need to be a clean line either. It’s just on average, how is the density of morphemes generally?</p>
</section>
</section>
<section id="spectrum-2" class="level3">
<h3 class="anchored" data-anchor-id="spectrum-2">Spectrum 2</h3>
<p>The second continuum ranges from very clear distinctions between morphemes to completely unique, unpredictable morphemes outlining certain features- agglutinative to fusional.</p>
<section id="agglutinative-languages" class="level4">
<h4 class="anchored" data-anchor-id="agglutinative-languages">Agglutinative Languages</h4>
<p>An agglutinative language like Turkish clearly separates all of its morphemes. Take the “word” (more like sentence) “Evlerimizdenmişsiniz”.</p>
<p>Breakdown:</p>
<p>Ev → “house” (root noun)</p>
<p>-ler → plural → Evler = “houses”</p>
<p>-imiz → our → Evlerimiz = “our houses”</p>
<p>-den → from → Evlerimizden = “from our houses”</p>
<p>-miş → hearsay/past tense → Evlerimizdenmiş = “it seems it was from our houses”</p>
<p>-siniz → second person plural → Evlerimizdenmişsiniz = “apparently you (all) were from our houses”</p>
</section>
<section id="fusional-languages" class="level4">
<h4 class="anchored" data-anchor-id="fusional-languages">Fusional Languages</h4>
<p>However, look at fusional languages. In Spanish, “hablamos” means “we speak”, with the ending “-amos” indicating that the pronoun is first person, and also plural (“we”). If you just knew the first person ending that’s not plural (“-o”), then you still wouldn’t be able to derive the ending “-amos” from that.</p>
</section>
</section>
<section id="consonantal-root-systems" class="level3">
<h3 class="anchored" data-anchor-id="consonantal-root-systems">Consonantal Root Systems</h3>
<p>There is a feature in languages where the root meaning is carried out through the consonants, and the vowels between them just modify the meaning. This is pretty much unseen outside of Afro-Asiatic langauges.</p>
<p>Most famously, Semitic languages (a sub-branch of Afro-Asiatic) such as Arabic and Hebrew use the triconsonantal root system. In Arabic, for example, the root “k-t-b” has to do with writing and books. The word “kitab” means “book”, the word “katib” means “writer”, and the word “maktaba” means “library”.</p>
<p>Note that the extra consonant “m” in “maktaba” is added, because Arabic itself isn’t purely consonantal, and uses affixes as well. Interestingly, the word “kitab” spread to many languages like Farsi or Hindi to mean “book”, but since those languages aren’t Semitic, they don’t think of “kitab” using the triconsonantal root system, but rather just as any other word.</p>
<p>Germanic languages like English do <em>just</em> a little. Primarily, this is shown in tense changes, like “s<em>i</em>ng” -&gt; “s<em>u</em>ng” -&gt; “s<em>a</em>ng”, or “r<em>u</em>n” -&gt; “r<em>u</em>n” -&gt; “r<em>a</em>n” as opposed to something like “reprimand” -&gt; “reprimand<em>ed</em>” -&gt; “reprimand<em>ed</em>”, where the latter is regular.</p>
</section>
</section>
</section>
<section id="free-and-bound-morphemes" class="level1">
<h1>Free and Bound Morphemes</h1>
<p>There is also a difference between free and bound morphemes. <em>Free morphemes</em> can exist on their own, while <em>bound morphemes</em> can only exist attached to other morphemes.</p>
<p>For example, look at the word “dogs”. The “s” is a plural marker, but you can’t have a plural marker on its own, so it is bound. Meanwhile, “dog” is free, because it is a word on its own.</p>
</section>
<section id="merging-morphemes-subconsciously" class="level1">
<h1>Merging Morphemes Subconsciously</h1>
<p>Sometimes, a single morpheme could etymologically be derived from two other morphemes, but our brains treat it like a single morpheme due to semantic drifting.</p>
<p>For example, take the word “forgive”. Etymologically, it was derived from “for” and “give”. However, over time, the meaning of “forgive” stopped being derived from “for” and “give” individually. So, people perceive it as a single morpheme, because those historical morphemes don’t contribute to the meaning of “forgive” anymore.</p>
</section>
<section id="affixes" class="level1">
<h1>Affixes</h1>
<p>Most languages’ morphologies involve <em>affixes</em>, or morphemes being added to words. Here are the main types:</p>
<ul>
<li>Prefixes: Go before the word, like “un” in English to mean “not” (unhappy).</li>
<li>Suffixes: Go after the word, like “s” in English to mean plural (dogs).</li>
<li>Circumfixes: Go before and after the word, but the parts going on either side don’t mean anything individually, like “ge…t” in German to form the past tense (“kaufen” -&gt; “gekauft”)</li>
<li>Infixes: Go inside a word, like swear words in some people’s English to make emphasis (abso-[bleep]ing-lutely)</li>
</ul>
</section>
<section id="note" class="level1">
<h1>Note</h1>
<p>One important thing to note is that trying to classify languages into categories like this isn’t super helpful. Early ideas from linguistics are usually western concepts, because the languages linguists were studying were mostly Eurasian. As a result, these spectrums don’t necessarily account for every single language. Arabic, for example, can’t really be plotted on the 2D grid of the two spectrums, because a consonantal root system is way more complicated. There are many more morphological spectrums (like concatenative and non-concatenative, the latter of which Arabic falls into) that could exist as well, but these are just the most commonly used references ones.</p>
</section>
<section id="conclusion" class="level1">
<h1>Conclusion</h1>
<p>So, now we know how meanings can be arranged within “words” of a language. However, how do these meanings interact? This is what we need syntax for, which will be covered next.</p>


</section>

 ]]></description>
  <category>Linguistics</category>
  <guid>https://vaishnavs.net/posts/Morphology/</guid>
  <pubDate>Sun, 12 Oct 2025 18:30:00 GMT</pubDate>
  <media:content url="https://vaishnavs.net/posts/Morphology/translate.png" medium="image" type="image/png" height="101" width="144"/>
</item>
<item>
  <title>Phonetics</title>
  <dc:creator>Vaishnav Sudarshan</dc:creator>
  <link>https://vaishnavs.net/posts/Phonetics/</link>
  <description><![CDATA[ 





<blockquote class="blockquote">
<p>This is a series of blogs about linguistics. See also: <a href="../Morphology-and-Semantics/"><em>Morphology and Semantics</em></a>, <a href="../Writing-Systems/"><em>Writing Systems</em></a>, <a href="../Phonetics-and-Phonology-Part2/"><em>Phonetics and Phonology Part 2</em></a></p>
</blockquote>
<section id="how-sounds-work" class="level1">
<h1>How Sounds Work</h1>
<p>At first, the question of “how do sounds work” may seem dumb - you just vibrate your vocal cords, right? However, it’s more complicated than that. When you were a baby, you were as educated as a linguistics major in that you were able to identify how different sounds are made from observing people’s mouths. Now, it’s more difficult to do so, and you may struggle - unless, of course, you’re a baby reading this, and in that case, you should become incredibly famous and win a world record if you haven’t already.</p>
<p>In kindergarten, you may have learned that sounds are classified as vowels and consonants, and that sounds are known as phones.</p>
<p>But what really is the difference between a vowel and a consonant? It’s basically just how much constriction your vocal cords have - vowels have entirely unobstructed airflow, while consonants have noticeable obstruction in the airflow.</p>
<section id="consonants" class="level2">
<h2 class="anchored" data-anchor-id="consonants">Consonants</h2>
<p>Right now, let’s do consonants. In short, the two main parameters that control how a consonant is made are “place of articulation” and “manner of articulation”.</p>
<section id="place-of-articulation" class="level3">
<h3 class="anchored" data-anchor-id="place-of-articulation">Place of Articulation</h3>
<p>Place of articulation is essentially where in your mouth a sound is being made, whether it is deep in the throat (I’m looking at you, certain language primarily spoken in a country that borders Belgium, Germany, Luxembourg, Spain, Andorra, Monaco, Brazil, Suriname, and Italy) or front in the lips (like at the end of “dumb”). From deepest in the throat to closest in the lips, the most commonly referred to categories include glottal, pharyngeal, uvular, velar, retroflex, palatal, alveolar, dental, labiodental, and bilabial.</p>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><a href="places_articulation .png" class="lightbox" data-gallery="quarto-lightbox-gallery-1" title="Here is a diagram showing the different body parts of the mouth for each of these places of articulation."><img src="https://vaishnavs.net/posts/Phonetics/places_articulation .png" class="img-fluid figure-img" alt="Here is a diagram showing the different body parts of the mouth for each of these places of articulation."></a></p>
<figcaption>Here is a diagram showing the different body parts of the mouth for each of these places of articulation.</figcaption>
</figure>
</div>
<p>The original diagram is from <a href="https://learnteachtravel.com/consonant-sounds-4-place-of-articulation/">here</a>.</p>
</section>
<section id="manner-of-articulation" class="level3">
<h3 class="anchored" data-anchor-id="manner-of-articulation">Manner of Articulation</h3>
<p>Manner of articulation is how the sound is actually made. For example, there is a difference between “boron” and “moron”, even though both [b] and [m] are both “bilabial” sounds (one of the places of articulation mentioned above). Such manners of articulation include:</p>
<ul>
<li><p>Fricatives (blowing air, like in the “sssss” sound in “snake”)</p></li>
<li><p>Plosives (stopping the sound, like how in “dart”, pronouncing both the [d] and [t] can’t really be continued)</p></li>
<li><p>Nasals (where air comes out of your “nnnnn-nostrils”). As an experiment, try to block your nostrils by pressing one finger on either side of your nose really hard, and then go “nnnnn” or “mmmmm” or “ŋŋŋŋŋ” (the last one is velar, like the “n” in “bank”). You’ll likely feel the air coming from your lungs but then being trapped because it can’t escape through the nose, so it might try to go through your ears instead, and you’ll feel a lot of pressure there, similar to when your ear pops on an airplane. Or maybe a much less painful demonstration would be if you put your finger right in front of your nostrils, and pronounce two voiced, continuous consonants at the same place of articulation, where one is a nasal and one is a fricative, such as [n] and [z]. You’ll feel the air going on your finger in the first case, but not the second.</p></li>
<li><p>Affricates (starts as a stop, ends as a plosive). Technically, two sounds are being produced, which is why playing the audio backwards won’t sound identical, but many languages, like English, treat them as a single sound, while the backwards version is two different sounds. Think of the English word “chop”. If you ask a native speaker to say this backwards, they might say “potsh”, because they think of the “ch” (voiceless postalveolar affricate) as a single sound. However, the real audio played backwards will sound more like “posht”, because the two sounds in this affricate should also get reversed.</p></li>
<li><p>Trills (where a sound is like a plosive but gets rolled, like the Spanish rolled r in “perro”)</p></li>
<li><p>Taps (like trills but only touches once, not multiple times)</p></li>
<li><p>Semivowels (consonants that are like vowels because they have very low constriction). For example, [j], [ɹ], and [w] sound a lot like [i], [ɚ], and [u], respectively.</p></li>
<li><p>Laterals (“l”-like sounds basically where airflow goes through either side of the tongue). This includes lateral fricatives like the Welsh “ll”, as well as the two .</p></li>
<li><p>Clicks (air is sucked in instead of pushed out because the velum is closed off, but unfortunately these cool sounds don’t exist in English, so I can’t provide an example you know how to pronounce. However, the name of the language Xhosa, (in)famous for having a lot of clicks, has a click in its name when not butchered as /kshosa/);</p></li>
<li><p>Implosives (like clicks except the glottis is closed off instead)</p></li>
<li><p>Ejectives (a stop is held shut, so the air is forced to come out from the glottis instead of the lungs)</p></li>
</ul>
<p>and more.</p>
<section id="pulmonic-and-non-pulmonic-consonants" class="level4">
<h4 class="anchored" data-anchor-id="pulmonic-and-non-pulmonic-consonants">Pulmonic and Non-Pulmonic Consonants</h4>
<p>Clicks, ejectives, and implosives are different from the others. Instead of using air from the lungs, they use different sources. These are called <em>non-pulmonic consonants</em>, while consonants that use air from the lungs are called <em>pulmonic consonants</em></p>
</section>
</section>
<section id="voicedness" class="level3">
<h3 class="anchored" data-anchor-id="voicedness">Voicedness</h3>
<p>Another important parameter is voicedness. Voicedness is just if the vocal cords are vibrating while the sound is being made. To understand this, look at [s] and [z], or [k] and [g] (as an exercise, find the voiceless version of [b]). In most languages, this has a really important distinction. For example, take “tie” and “die”. However, we usually just include this within manner of articulation, because we can’t put 3D charts on the iPad screen your face is glued to.</p>
</section>
<section id="other-parameters" class="level3">
<h3 class="anchored" data-anchor-id="other-parameters">Other Parameters</h3>
<p>Consonants are classified in other ways than just the main two or three parameters, though. For example, there are pulmonic and non-pulmonic consonants. This just means if the sound is normal or a freak that doesn’t use air coming from the lungs. The only non-pulmonic consonants are implosives, ejectives, and clicks, and the rest are generally pulmonic.</p>
<p>Another classification is continuancy. Fricatives, nasals, approximants, and trills can be pronounced for a long time, so they are continuant, but stops, affricates, and clicks are pronounced instantly. I noticed this specific feature at a young age, before I knew any linguistics, so I find it extra cool.</p>
<p>Additionally, there are more factors that can alter a consonant.</p>
<p>If you know Hindi, for example, you know how aspiration - putting extra air after a consonant - can impact a word and does matter, like in the words “पल” (pronounced like “pal”, meaning “moment”) and “फल” (pronounced like “phal”, meaning “fruit”).</p>
<p>In Russian, palatalization - making the consonant more like a palatal sound, which basically just makes it sound like “y” sound is at the end - is a very important factor too, with the words “мать” (pronounced like “maty” with the y being the sound in “yo” and not “corny”) meaning “mother” but “мат” (pronounced like “mat”) meaning a swear word.</p>
<p>Gemination - making a consonant pronounced for longer - is important in Finnish, because “tapa” means “way” or “manner”, but “tappa” means “kill”.</p>
<p>Unreleased stops are when you’re about to pronounce a stop but don’t actually produce that sound. For example, in American English, the word “bot” might end with your tongue on the alveolar ridge, but you won’t actually hear the [t] sound. These aren’t distinguished in English65</p>
</section>
<section id="sonorants-and-obstruents" class="level3">
<h3 class="anchored" data-anchor-id="sonorants-and-obstruents">Sonorants and Obstruents</h3>
<p>There is also sonorance or obstruence. Sonorance means the vocal tract is pretty open, like a vowel. As a result, most sonorants, which include nasals, approximants, and liquids, tend to be voiced. Obstruence means there is some friction or turbulence which make the sounds more easily voiceless and are noisier. Obstruents include plosives, fricatives, and affricates. Sonorants include nasals, liquids, and approximants.</p>
<p>This isn’t a clear binary, but rather a hierarchy, arranged by the degree of constricion.</p>
</section>
</section>
<section id="vowels" class="level2">
<h2 class="anchored" data-anchor-id="vowels">Vowels</h2>
<p>Even in vowels, two main parameters affect how a vowel is made. While vowels are not that interesting in my opinion, they are definitely required, because without them you’d be speaking either gibberish or Polish. Vowels tend to be voiced because they are sonorant and made by vibrating the vocal cords.</p>
<div class="callout callout-style-default callout-note callout-titled">
<div class="callout-header d-flex align-content-center">
<div class="callout-icon-container">
<i class="callout-icon"></i>
</div>
<div class="callout-title-container flex-fill">
Cool fact to bore your friends with and be called a nerd!!!
</div>
</div>
<div class="callout-body-container callout-body">
<p>The reason why whispering is quiet is because what you’re really doing is not vibrating your vocal cords at all. Since vowels are inherently voiced, by whispering, you end up not being able to project your voice very much at all, as vowels are kind of the base of speech.</p>
</div>
</div>
<p>The parameters are backness (deep in the throat or front in the mouth, like the x-axis) and height (vertical position, but described using open or close, like the y-axis). A third binary parameter is there, roundedness, which is if your mouth is shaped like a circle or not.</p>
<p>For example, the [i] sound is a closed front unrounded tense vowel.</p>
<p>Unlike consonants, backness and height are continuous and based on physical space, and when you chart the different vowels according to these features, you get essentially a diagram of your mouth (which is why it is shaped like a trapezoid, not a rectangle like the consonants - the cross-section of our faces is shaped approximately like this). This is called a <a href="https://en.wikipedia.org/wiki/Vowel_diagram"><em>vowel diagram</em></a>.</p>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><a href="vowels.png" class="lightbox" data-gallery="quarto-lightbox-gallery-2" title="Here’s what a vowel diagram diagram looks like."><img src="https://vaishnavs.net/posts/Phonetics/vowels.png" class="img-fluid figure-img" alt="Here’s what a vowel diagram diagram looks like."></a></p>
<figcaption>Here’s what a vowel diagram diagram looks like.</figcaption>
</figure>
</div>
<p>There are many more variations to vowels that can be made now, and this can influence phonology too (as you’ll see in the next part).</p>
<p>For example, tone is a big factor in Mandarin. 糖 (táng) means sugar, but 汤 (tāng) means soup. Imagine going to a cafe and accidentally asking for soup in your tea instead of sugar…</p>
<p>Nasality (how much air comes out of the nostrils) is important in Fr*nch, as “a” means “has” but “an” means “year”.</p>
<p>Rhoticity (how much the vowel sounds r-colored) makes the word “or” sound American when rhotic, but British when you only pronounce it like /oː/.</p>
<p>Vowels can also have creaky or breathy voice (basically making it sound like a sheep or a zombie).</p>
<p>Vowel length, like gemination but for vowels, is distinguished in Thai.</p>
<p>However, if you mess up some distinctions while trying to speak a language, its native speakers will most likely still understand you based on context, although they would likely notice that it sounds off.</p>
</section>
</section>
<section id="spectrograms" class="level1">
<h1>Spectrograms</h1>
<p>Basically, this is just a graph that records a word being pronounced, where the y axis is frequency and the x axis is time, and both are independent of each other (at a given time, your vocal cords produce a combination of frequencies, which are separated using Fourier analysis). We also want to encode energy as a function of these two, but instead of drawing a z axis, it’s indicated through shading instead. Darker shading means more acoustic energy (or loudness), and lighter shading means less.</p>
<p>Bands of shading are called <em>formants</em>, and they’re mainly for vowels. They are basically the three parameters that vowels take - F1 is high/low, F2 is front/back, and F3 is rounded/unrounded.</p>
<p>Here is the spectrogram for the word “things”:</p>
<p><a href="spectrogram.png" class="lightbox" data-gallery="quarto-lightbox-gallery-3" title="Spectrogram for the word “things”"><img src="https://vaishnavs.net/posts/Phonetics/spectrogram.png" class="img-fluid" alt="Spectrogram for the word “things”"></a>.</p>
<p>Note that the blank space in the first half isn’t part of the word itself - there was a gap between starting the recording and saying the word.</p>
<p>This blue line measures how fast the vocal cords are vibrating. After the “th”, everything is voiced, which is why it only starts after that first part.</p>
</section>
<section id="to-be-continued" class="level1">
<h1>To Be Continued</h1>
<p>Now that you know how sounds are produced, let’s find out how linguists <a href="https://vaishnavs.net/posts/The%20IPA/">write them</a>.</p>


</section>

 ]]></description>
  <category>Linguistics</category>
  <category>Biology</category>
  <category>Physics</category>
  <guid>https://vaishnavs.net/posts/Phonetics/</guid>
  <pubDate>Sat, 13 Sep 2025 18:30:00 GMT</pubDate>
</item>
<item>
  <title>Phonology</title>
  <dc:creator>Vaishnav Sudarshan</dc:creator>
  <link>https://vaishnavs.net/posts/Phonology/</link>
  <description><![CDATA[ 





<blockquote class="blockquote">
<p>This is a series of blogs on linguistics. See also: <a href="../Morphology-and-Semantics/"><em>Morphology</em></a>, <a href="../Writing-Systems/"><em>Writing Systems</em></a>, <a href="../Phonetics-and-Phonology-Part1/"><em>Phonetics</em></a></p>
</blockquote>
<section id="the-ipa-review" class="level1">
<h1>The IPA Review</h1>
<p>The <a href="https://vaishnavs.net/posts/The%20IPA/"><em>International Phonetic Alphabet</em></a>, or the IPA, is how sounds are represented. Each letter is consistent and makes the same sound all the time, because they are defined using the specific terms we talked about in the Phonetics blog post. To fully understand how some of the examples in this post are pronounced, you might want to check out <a href="https://www.ipachart.com/">the IPA chart</a>.</p>
<p>You may have noticed that throughout the last article I’ve used slashes and brackets to refer to sounds. That was not just something random I did because a monkey walked on my keyboard one time and then I stuck with it - this is actually the notation of referencing IPA sounds.</p>
</section>
<section id="the-difference-between-slashes-and-brackets" class="level1">
<h1>The Difference Between Slashes and Brackets</h1>
<p>Why did I use both [] and //? In short, [] is the actual scientific way of making as many distinctions as you want (phonetic transcription), so it doesn’t care about how specific languages perceive sounds. On the other hand, // is when you only care about the distinctions a specific language makes (phonemic transcription), so you’ll typically be less descriptive of how to pronounce that sound.</p>
<p>For example, Tamil doesn’t distinguish between voiced and voiceless consonants, so you could phonemically write the word for monkey as /kuɾaŋku/, even though phonetically, people actually pronounce it as something like [kuɾaŋɡʊ]. However, it doesn’t matter which of those distinctions are used, between [ʊ] and [u] or [k] and [g], since they’re perceived as being the same sound for Tamil speakers.</p>
</section>
<section id="allophonic-variation" class="level1">
<h1>Allophonic Variation</h1>
<p>Phonemes can have different forms, so a single phoneme is more of a category. In the example for “monkey” in Tamil, the phoneme /k/ can mean [k] or [g] depending on the specific word. So, we’d say that the voicing of /k/ is NOT <em>phonemic</em> in Tamil - variations aren’t distinguished in meaning. [k] and [g] are considered <em>allophones</em> - different forms of the same phoneme.</p>
<p>You can write allophones by describing when a certain phoneme varies in a certain environment. So, we get to use nerdy linguistics notation! For example, in Tamil, /k/ is pronounced as [g] after a nasal sound, so we can write /k/ → [g] / [ŋ]__. The underscore represents the position of this phoneme, and the slash indicates that the environment of this variation is about to come next.</p>
<p>A more tangible example, if you’re in the 98.94% of people who don’t speak Tamil, of allophonic variation is aspiration in English. You might notice that the “tone” in “stone” and “tone” are pronounced differently. Sure enough, in the IPA (broad transcription since we only care about aspiration), the first consonant or consonant cluster is pronounced as [t] and [tʰ] respectively. This is because aspiration is allophonic. At the beginning of a word, before a vowel, stops are aspirated, but they aren’t aspirated after a fricative. So, you could write /t/ → [tʰ] / #_V. The hashtag indicates the start of a word, and V represents a vowel.</p>
</section>
<section id="intuition-for-phonemes" class="level1">
<h1>Intuition for Phonemes</h1>
<p>Does this whole idea of languages perceiving sounds feel kind of weird? It might be, because it is mainly subconscious, and also feels more like psychology than linguistics. However, let me show you why talking about phonemes is actually necessary.</p>
<p>The concept of phonemes can be boiled down to distinguishing between sounds. From the phonetics blog, you might remember that that are a BUNCH of different features that can be present in sounds. There’s not just place and manner of articulation, but also voice, gemination, nasality, and more.</p>
<p>Imagine that there was no such notion of distinguishing between those different features. Then, you would have a BUNCH of different sounds that all sound basically the same to you, based on every single combination of these features. Even if the features are just binary, which is the smallest amount of distinction in a feature, they would still grow exponentially, so 20 binary features would already give you over a million different sounds that you have to distinguish between. Theoretically, you could even have tiny, continuous distinctions, like the amount of time pronouncing a vowel. Then, you would have to deal with an infinite amount of different sounds. Therefore, all languages have a system of distinguishing sounds into phonemes.</p>
</section>
<section id="minimal-pairs" class="level1">
<h1>Minimal Pairs</h1>
<p>So, how do you know if a language distinguishes between two sounds? The main, most reliable way is to find minimal pairs. A minimal pair is two words that mean different things whose pronounciations differ by only one sound at the same, corresponding positions. For example, in English, “bag” and “back” ([bæg] and [bæk]) are a minimal pair, since they have different meanings and the only difference in their pronounciation is the [g] and [k], which means they are two different phonemes, /k/ and /g/. Typically, even one minimal pair suffices to show that two sounds are perceived as different phonemes, but more examples could help to provide further evidence.</p>
</section>
<section id="weird-example-of-telugu-with-sanskrit-loanwords" class="level1">
<h1>Weird Example of Telugu with Sanskrit loanwords</h1>
<p>Telugu is the most widely spoken Dravidian language. It has a lot of Sanskrit loanwords. In Sanskrit, [k], [g], [kʰ], and [gʰ] are all their own phonemes, but in native Dravidian vocabulary, they are allophones of the same phoneme /k/.</p>
<p>As a result, there are two layers of phonology in Telugu. The vocabulary that is from before the Sanskrit loanwords contains no minimal pairs that distinguish across aspiration or voicing, while the Sanskrit loanwords do contain such minimal pairs.</p>
<p>Fun fact: This is one reason why the Telugu script’s letters for voicing and aspiration are so much easier than Devanagari’s. Initially, the Telugu script only had one letter for all these sounds ( క ), like the Tamil ( க ). After borrowing the Sanskrit loanwords, they just added diacritics to that letter to represent those distinctions.</p>
<p>As a bonus fun fact, the reason why representing those Sanskrit loanwords was so important is because a lot of them were words that represented concepts that weren’t present in Telugu before, like a lot of Hindu ideas, and written text typically was about religious topics, so it was important not to cause any misunderstandings.</p>
</section>
<section id="french-example-of-phonology" class="level1">
<h1>French Example of Phonology</h1>
<p>Each language has its phonology written, by placing the accurate symbols of all of its phonemes. For example, see the phonology of French. <a href="french_phonology.png" class="lightbox" data-gallery="quarto-lightbox-gallery-1" title="French phonology source"><img src="https://vaishnavs.net/posts/Phonology/french_phonology.png" class="img-fluid" alt="French phonology source"></a></p>
</section>
<section id="representation-of-features-as-vectors" class="level1">
<h1>Representation of features as vectors</h1>
<p>While you can describe the pronounciation of a phoneme using the IPA, a more helpful way is to describe that symbol with a vector of features, but only the features that are distinguished in a certain language. For example, in English, the phoneme /p/ might be represented as [+bilabial, +stop, -voice], while /b/ might be [+bilabial, +stop, +voice].</p>
</section>
<section id="example-in-korean-for-how-tones-might-develop" class="level1">
<h1>Example in Korean for how tones might develop</h1>
<p>Lots of times, losing distinguishing features causes ambiguity, and new features naturally arise to resolve that ambiguity. One can observe this happening in Korean. Korean has a three-way distinction between /k/, /kʰ/, and /k͈/ (plain, aspirated, and tense). However, the younger generations of Korean speakers nowadays have a hard time distinguishing between the plain and tense phonemes, so their pronounciations start merging, and this results in a lot of homophones, which may create confusion. Younger speakers have been observed to use differences in pitch to fill in this gap in information. Over time, this could lead to the development of tones in future dialects of Korean. This is very similar to how tones developed in most Chinese languages, since Old Chinese actually was not tonal and had consonant clusters instead that simplified and converged over time and created ambiguity. This phenomenon is called tonogenesis, and is also currently happening in Afrikaans, which is spoken about 12,500 kilometers away.</p>
</section>
<section id="weird-edge-cases" class="level1">
<h1>Weird Edge Cases</h1>
<p>Many phonological rules have strange edge cases that most people wouldn’t immediately think about. Here are some of them.</p>
<section id="neutralization" class="level2">
<h2 class="anchored" data-anchor-id="neutralization">Neutralization</h2>
<p>What if there is a phoneme /A/ and a phoneme /B/, which both turn into the allophone [X] in a certain environment? This is called neutralization, where both phonemes’ pronounciations are indistinguishable sometimes.</p>
<p>An example of this is in Korean, which distinguishes aspirated and unaspirated stops. However, at the end of a word, like American English, both of these become unreleased stops, which sound identical (because if you’re not even pronouncing a stop, you can’t pronounce it with an extra breath of air).</p>
</section>
<section id="vowel-harmony" class="level2">
<h2 class="anchored" data-anchor-id="vowel-harmony">Vowel Harmony</h2>
<p>Vowel harmony is a very cool property found in some languages.</p>
<p>Basically, all vowels in a word must be made with the same frontness, and sometimes closedness or roundedness too. This is because if you have a wide range of vowels, the vowels might jump around everywhere in your mouth and cause it to do a bunch of gymnastics. To prevent this, some languages limit the physical range of vowels a certain word can have (or in the case of roundedness vowel harmony, the shape of your lips).</p>
</section>
<section id="example" class="level2">
<h2 class="anchored" data-anchor-id="example">Example</h2>
<p>For example, in Kazakh, the plural marker is either “-лаp” or “-лер” (/lar/ or /ler/) depending on if the root of the noun is front or back.</p>
<p>“қала” (/qɑˈlɑ/), meaning “city”, uses back vowels, so “cities” is “қалалар”.</p>
<p>However, “көл” (/kœl/), meaning “lake”, uses front vowels, so “lakes” is “көлдер”.</p>
</section>
</section>
<section id="structure-of-syllables-and-phonotactics" class="level1">
<h1>Structure of Syllables and Phonotactics</h1>
<p>Each language has its own rule system for how certain phonemes can be placed together into words and syllables. Most syllables cross-linguistically have some sort of nucleus (typically a vowel, but sometimes some sonorant consonants), an optional onset (consonants before the nucleus), and an optional coda (any consonants after the nucleus). The combination of the nucleus and the coda is called the rhyme, which is why in poems, you would call rhyming words anything where the phonemes after the onset match.</p>
<p>Languages can vary in how restrictive or permissive they are with their syllable structure, and this is called phonotactics. Phonotactics also determine how syllables may stack together in words. Hawaiian, for example, is very restrictive, since the most complicated syllable structure it allows is CV (consonant + vowel), while English is very permissive, since it allows syllables like CCCVCCCC, in the word “strengths” (/strɛŋkθs/).</p>
<p>This is why some languages like Wifi Password Language (Polish) have a bunch of consonant clusters that English speakers find despicable; its most complex syllable is way, way, way longer than “strengths”. Meanwhile, Spanish’s phonotactics are pretty restrictive compared to English, which is why “student” is “estudiante” in Spanish; a consonant cluster may not begin a word, so they add a vowel at the beginning.</p>
</section>
<section id="conclusion" class="level1">
<h1>Conclusion</h1>
<p>Now we know how languages’ perceived sounds interact with each other, but how does meaning form? Stay tuned for morphology.</p>


</section>

 ]]></description>
  <category>Linguistics</category>
  <guid>https://vaishnavs.net/posts/Phonology/</guid>
  <pubDate>Sat, 13 Sep 2025 18:30:00 GMT</pubDate>
  <media:content url="https://vaishnavs.net/posts/Phonology/french_phonology.png" medium="image" type="image/png" height="123" width="144"/>
</item>
<item>
  <title>The IPA</title>
  <dc:creator>Vaishnav Sudarshan</dc:creator>
  <link>https://vaishnavs.net/posts/The IPA/</link>
  <description><![CDATA[ 





<section id="the-ipa" class="level1">
<h1>The IPA</h1>
<p>Before you learn how sounds are made, and how languages distinguish them, let’s see how 𝚗̶𝚎̶𝚛̶𝚍̶𝚜̶ linguists actually write them (since you are well accustomed to <a href="https://vaishnavs.net/posts/Writing-Systems/">writing systems</a>, right?). The <a href="https://en.wikipedia.org/wiki/International_Phonetic_Alphabet"><em>International Phonetic Alphabet</em></a> is a system where each letter is consistent and makes the same sound all the time, because they are defined using the specific terms we talked about in the Phonetics blog, like voiceless geminated bilabial trill (basically just horse noises). The IPA is kind of like the Periodic Table of linguistics.</p>
</section>
<section id="chill-ipa-characters" class="level1">
<h1>Chill IPA Characters</h1>
<p>Many letters are just like in English. For example, why don’t you take a random guess at how [p], [h], [v], [z], [m], [ɪ] and [t] are pronounced? Yes! They are pronounced like “p”, “h”, “v”, “z”, “m”, “ɪ” and “t”! BUT NOT LIKE “pea”, “aich”, “vee”, “zee”, “em”, “eye”, and “tea” - you need to hop off elementary school English if you said that.</p>
</section>
<section id="troll-ipa-characters" class="level1">
<h1>Troll IPA Characters</h1>
<p>However, there are some tricky ones too that are designed to deceive you. For example, what sounds do you think [j], [x], [ɑ], [r], [q], [c], and [ʔ] make? No, it is not “jay”, “eks”, “aey”, “ar”, “kyoo”, “see”, and “hmmm?”. Instead, they make the voiced palatal approximant, voiceless velar fricative, unrounded open back vowel, voiced alveolar trill, voiceless uvular stop, voiceless palatal stop, and the glottal stop (glottal stop doesn’t have a voiced version, because it’s just the break between “uh” and “oh” in “uh-oh”).</p>
</section>
<section id="greek-ipa-letters" class="level1">
<h1>Greek IPA Letters</h1>
<p>We’re not done. There’s even Greek letters, which somehow we can never evade, regardless of the subject. [ɸ], [θ], [ʎ], [ɤ], and [ʊ] are not phi, theta, lambda, gamma, and upside-down omega, but instead voiceless bilabial fricative, voiceless alveolar fricative, voiced palatal lateral approximant, back close-mid unrounded vowel, and then this random vowel that doesn’t know where it belongs. Phew. That torture is over. Or is it?</p>
</section>
<section id="diacritics-intro" class="level1">
<h1>Diacritics Intro</h1>
<p>We still have the diacritics to go over, but this time I won’t subject you to the pain of looking at every diacritic. Instead, I’ll just say that the diacritics can alter a sound to fit any of the variations for consonants and vowels I talked about earlier, such as nasality (so a nasalized [a] is [ã]), gemination (so a geminated [t] is [t:]), voicelessness (circle underneath), tone, and more.</p>
</section>
<section id="visualization" class="level1">
<h1>Visualization</h1>
<p>To see the visual representation of the IPA, and to actually listen to their sounds, click <a href="https://www.ipachart.com/"><em>here</em></a>.</p>
</section>
<section id="to-be-continued" class="level1">
<h1>To Be Continued</h1>
<p>Now, since having a bunch of fancy symbols is meaningless on its own, we need to learn how sounds actually <a href="https://vaishnavs.net/posts/Phonetics/">work</a> so that they have a purpose.</p>


</section>

 ]]></description>
  <category>Linguistics</category>
  <guid>https://vaishnavs.net/posts/The IPA/</guid>
  <pubDate>Sat, 13 Sep 2025 18:30:00 GMT</pubDate>
</item>
<item>
  <title>Writing Systems</title>
  <dc:creator>Vaishnav Sudarshan</dc:creator>
  <link>https://vaishnavs.net/posts/Writing-Systems/</link>
  <description><![CDATA[ 





<blockquote class="blockquote">
<p>This is a series of blogs about linguistics. See also: <a href="../Phonetics-and-Phonology-Part1/"><em>Phonetics and Phonology Part 1</em></a> <a href="../Morphology-and-Semantics/"><em>Morphology and Semantics</em></a> <a href="../Phonetics-and-Phonology-Part2/"><em>Phonetics and Phonology Part 2</em></a></p>
</blockquote>
<section id="writing-systems" class="level1">
<h1>Writing Systems</h1>
<section id="introduction" class="level2">
<h2 class="anchored" data-anchor-id="introduction">Introduction</h2>
<p>Have you ever wondered how kids sing their “abc’s” in different places? In some places, kids sing their “alpha beta gamma’s” or their “alif baa jiim’s”, which are pretty similar to our own. In some places, kids recite their “ka kha ga gha nga’s”, quite different from our own. Yet in other places, such a song about their “alphabet” would be physically impossible, with kids thinking this is a preposterous and cruel joke. All of these are tricks for remembering letters, which are part of writing systems. Writing systems are also known as <a href="https://en.wikipedia.org/wiki/Orthography"><em>orthographies</em></a>. You already know at least one - the Latin alphabet, which you’re reading right now. Here’s an overview of how all the different writing systems work.</p>
</section>
<section id="phonetic-orthographies" class="level2">
<h2 class="anchored" data-anchor-id="phonetic-orthographies">Phonetic Orthographies</h2>
<p>In phonetic writing systems, symbols are written based on sound. For example, in the Latin alphabet, the word “cat” is written with a “c” for the “c” sound, “a” for the “a” sound, and “t” for the “t” sound. Of course, it’s not always one-to-one, or even consistent, in English itself (cough cough, “<em>cough</em>”), but the main point still stands - it’s based on sound. In our language, you wouldn’t draw an image of a cat to represent a cat, you’d just write “cat” based on the sounds of the word. Here are the types of phonetic writing systems:</p>
<section id="alphabets" class="level3">
<h3 class="anchored" data-anchor-id="alphabets">Alphabets</h3>
<p>Alphabets work by having symbols for vowels and consonants, and they’re just written without really being treated as separate phonemes. These are arguably the simplest. Apart from the Latin alphabet, some others are Cyrillic, Greek, IPA, Georgian, Armenian, etc. Korean’s writing system, Hangeul, is kind of like an alphabet because it writes out its vowels and consonants, but it arranges each syllable into its own block. For example, the characters for “ba” would be 바, but the characters for “bo” would be 보. Furthermore, the characters for “bol” would be 볼. The word alphabet comes from the first to letters of Greek, alpha and beta.</p>
</section>
<section id="abjads" class="level3">
<h3 class="anchored" data-anchor-id="abjads">Abjads</h3>
<p>Most alphabets evolved from <a href="https://en.wikipedia.org/wiki/Abjad"><em>abjads</em></a>. Abjads are like alphabets, except usually, most of the vowels aren’t written, and instead inferred from context. Only long vowels are written. Sometimes, for clarity, the short vowels may be written in with diacritics. For example, in the Quran, even though the Arabic script is an abjad, all the vowels were written so that there aren’t any misinterpretations. The word “abjad” comes from the first sounds of the four letters of the Arabic script, “a”, “b”, “j”, and “d”, which is cognate with Greek’s “alpha”, “beta”, “gamma”, “delta”.</p>
<p>The most prominent example of abjads are the orthographies of Semitic languages, which it works well for due to their triconsonantal root system, where consonants carry the meaning and vowels just modify the word. Hwvr, f y d ths n nglsh, t wll b prtt mssd p nd nt t ll ntllgbl.</p>
</section>
<section id="syllabaries" class="level3">
<h3 class="anchored" data-anchor-id="syllabaries">Syllabaries</h3>
<p>In <a href="https://en.wikipedia.org/wiki/Syllabary"><em>syllabaries</em></a>, each symbol is a syllable, usually a pair of consonant and vowel. These work well for languages that don’t have crazy consonant clusters, like Japanese and Cherokee. However, if a language has a lot of possible syllables due to its large phonology, then there would be way too many symbols. <a href="Hiragana_and_Katakana.jpg" class="lightbox" data-gallery="quarto-lightbox-gallery-1" title="Chart showing the two syllabaries of Japanese source(https://cherryblossomstories.com/wp-content/uploads/2013/05/Hiragana-and-Katakana.jpg"><img src="https://vaishnavs.net/posts/Writing-Systems/Hiragana_and_Katakana.jpg" class="img-fluid" alt="Chart showing the two syllabaries of Japanese source(https://cherryblossomstories.com/wp-content/uploads/2013/05/Hiragana-and-Katakana.jpg"></a></p>
</section>
<section id="abugidas" class="level3">
<h3 class="anchored" data-anchor-id="abugidas">Abugidas</h3>
<p><a href="https://en.wikipedia.org/wiki/Abugida"><em>Abugidas</em></a>, in my opinion, are by far the coolest type of phonetic orthography. How it works is that if you write a consonant on its own, it comes with a vowel after it. For example, the /k/ sound in <a href="https://en.wikipedia.org/wiki/Devanagari"><em>Devanagari</em></a>, क, is actually pronounced /kə/ because without altering the consonant, it comes with an /ə/ sound. To make it a different vowel, you add a diacritic. So, /ke/ would be के. And, to make it just /k/ with no vowel, you make it क्. The most popular abugidas are from India, including Devanagiri, Tamil, Bengali, etc. However, the word “abugida” comes from the Ge’ez script from Ethiopia, where the first four letters are “a”, “bu”, “gi”, and “da” (and this arrangement is cognate with Greek’s “alpha”, “beta”, “gamma”, “delta”, just like with the word “Abjad”). Another notable abugida, apart from Indian scripts, Southeast Asian scripts, and the Ge’ez script, is the Cree script. For changing the vowel, Cree doesn’t actually add a diacritic, but instead modifies the consonant through rotations. Cree is actually partially inspired by Devanagiri.</p>
</section>
</section>
<section id="semantic-orthographies" class="level2">
<h2 class="anchored" data-anchor-id="semantic-orthographies">Semantic Orthographies</h2>
<p>Instead of writing symbols based on sound, some languages have orthographies where symbols are based on meaning.</p>
<section id="logographies" class="level3">
<h3 class="anchored" data-anchor-id="logographies">Logographies</h3>
<p>The most common type of semantic writing system is a logography, and the most famous type of logography is <a href="https://en.wikipedia.org/wiki/Hanzi"><em>Hanzi</em></a> from Sinitic languages, which is also what Japanese’s Kanji is based on. For example, look at the symbol for “yi” in Mandarin or “ichi” in Japanese, which means “one”: “一” Now, for “er” in Mandarin or “ni” in Japanese, which means “two”: “二” So, sometimes, the symbol looks like what it means. However, many logographic symbols have evolved so much that they don’t seem to resemble what they mean. For example, “马” means “horse” (pronounced as “ma”). This looks nothing like a horse, but the ancient form of this symbol did.</p>
<p>Sometimes, it can be more complicated than this. In Mandarin, each symbol is generally one syllable as well, and sometimes symbols are made based on their relation with other semantic meanings, so you can build up symbols from smaller symbols. For example, the symbol for “forest” is: 森 while the symbol for “tree” is: 木</p>
<p>Also, symbols whose words sound similar can also be used for clarification. This is called the <em>rebus principle</em>. In Chinese, most characters contain a semantic part, like the symbol for “tree” that we saw, and also a phonetic part, that indicates how it’s pronounced. For example, the word for “mom”, “妈”, which is pronounced as “ma”, contains the symbol for “horse” (“马”) we saw earlier, since that too is pronounced as “ma”, even though “mom” has nothing to do with “horse” in terms of meaning. Only the left half actually semantically has anything to do with “mom”. Only a small percentage of Chinese characters are actually purely logographic - the vast majority follow the rebus principle. Therefore, it’s more accurate to call Hanzi a logo-syllabary, instead of a logography.</p>
<p>Egyptian hieroglyphs were part logography, part phonetic as well. Some symbols worked just like the ancient form of Chinese, and others evolved into more of a syllabary or abjad.</p>
</section>
<section id="pictographies" class="level3">
<h3 class="anchored" data-anchor-id="pictographies">Pictographies</h3>
<p>Pictographies are kind of like logographies, except that it’s much more literal, without much evolution. Unlike Hanzi, where a lot of characters are derived from abstract connections, pictographies are literal depictions. This is likely where writing started first. An example is the Mayan script, where a lot of it was pictographic, but other symbols evolved into being logographic or syllabic. Also, even emojis are largely pictographic. However, pictographs, like logographs, still just represent words. <a href="mayan_inscription.png" class="lightbox" data-gallery="quarto-lightbox-gallery-2" title="A page showing the Mayan pictographies written down [source](https://3.bp.blogspot.com/_qTDAEasFLtU/S2bCBrxYEBI/AAAAAAAAG1A/eHIKTkXQ2gI/s1600/Tables+for+the+planet+Venus+duo.jpg"><img src="https://vaishnavs.net/posts/Writing-Systems/mayan_inscription.png" class="img-fluid" alt="A page showing the Mayan pictographies written down [source](https://3.bp.blogspot.com/_qTDAEasFLtU/S2bCBrxYEBI/AAAAAAAAG1A/eHIKTkXQ2gI/s1600/Tables+for+the+planet+Venus+duo.jpg"></a></p>
</section>
<section id="ideographies" class="level3">
<h3 class="anchored" data-anchor-id="ideographies">Ideographies</h3>
<p>Ideographies are another type of semantic orthography, where an idea or a concept is directly written, without being tied to a specific sound. For example, some street signs symbols that don’t have words but rather symbols, some of the more ancient Hanzi initially, or even some of the more abstract emojis as well are ideographies.</p>
</section>
</section>
<section id="evolution-of-writing" class="level2">
<h2 class="anchored" data-anchor-id="evolution-of-writing">Evolution of writing</h2>
<p>Many writing systems evolved from Egyptian hieroglyphs, to become primarily alphabets, abjads, or even abugidas. This is primarily in Europe, the Middle East, and North Africa, where Egypt indirectly influenced. For example, the European alphabets evolved from Ancient Greek’s alphabet (Latin through the Etruscan alphabet, which in turn came from the Ancient Greek alphabet), which evolved from Phoenecian’s abjad, which evolved from Egyptian hieroglyphs. Also, the Semitic abjads evolved from Phoenician’s abjad too. The Semitic languages are written from right to left, because it chose a direction to write from Phoenecian, which alternated. Ancient Greek also initially alternated directions line by line, but then chose to stick with only left to right, which all the European languages are written with now.</p>
<p>In India, as well as some parts of Southeast Asia, including Myanmar, Laos, and Thailand, the orthography (all abugidas) of those languages evolved from the <em>Brahmi</em> script, which was an abugida. It’s not certain where the Brahmi script is from, though it’s suggested to come from Egyptian hieroglyphs too, but it could also be an artificially created script that evolved naturally.</p>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><a href="brahmi_script_qutub_minar.jpg" class="lightbox" data-gallery="quarto-lightbox-gallery-3" title="An example of Brahmi script found on The Iron Pillar in Qutub Minar, New Delhi, source"><img src="https://vaishnavs.net/posts/Writing-Systems/brahmi_script_qutub_minar.jpg" class="img-fluid figure-img" alt="An example of Brahmi script found on The Iron Pillar in Qutub Minar, New Delhi, source"></a></p>
<figcaption>An example of Brahmi script found on The Iron Pillar in Qutub Minar, New Delhi, <a href="https://live.staticflickr.com/2869/12901396153_374f862d10_b.jpg">source</a></figcaption>
</figure>
</div>
<div class="callout callout-style-default callout-note callout-titled">
<div class="callout-header d-flex align-content-center">
<div class="callout-icon-container">
<i class="callout-icon"></i>
</div>
<div class="callout-title-container flex-fill">
Cool fact to bore your friends with and be called a nerd!!!
</div>
</div>
<div class="callout-body-container callout-body">
<p>The Brahmi script was initially all straight lines and sharp angles. In South India, Southeast Asia, and Sri Lanka, the letters look more curvy, because they were written on leaves, so sharp turns and straight lines would tear the leaves. However, in North India, the letters can be more angular and sharp, but still also some curves, because they were written on both leaves and stone.</p>
</div>
</div>
<p>In China and Japan, the characters are derived from the Ancient Chinese logographic characters. In Japan, there are three writing systems. Two are syllabaries derived from Chinese, and the other is the normal Chinese logography.</p>
<p>In both Koreas, Hangeul is used. Hangeul is an artificially created script that was made to address the high percentage of illiteracy, due to the fact that Chinese characters were way to hard for the common people to learn. However, Hangeul was designed to be very simple.</p>
<p>The Cherokee syllabary was made after one Native American looked at the European colonizers’ writing and tried to mimic the symbols to make a writing system for Cherokee. He’d seen both the Latin and Cyrillic scripts. However, the symbols in Cherokee that look similar to the European writing make completely different sounds, as he only knew the shape of the symbols, not what sound they made.</p>
</section>
<section id="to-be-continued" class="level2">
<h2 class="anchored" data-anchor-id="to-be-continued">To Be Continued</h2>
<p>OK, that phonetic writing system stuff was cool, but you need to know how sounds actually work to use the symbols that represent them. How does that work? Read the linked blogs to find out!</p>


</section>
</section>

 ]]></description>
  <category>Linguistics</category>
  <guid>https://vaishnavs.net/posts/Writing-Systems/</guid>
  <pubDate>Fri, 22 Aug 2025 18:30:00 GMT</pubDate>
  <media:content url="https://vaishnavs.net/posts/Writing-Systems/brahmi_script_qutub_minar.jpg" medium="image" type="image/jpeg"/>
</item>
<item>
  <title>Limit riLmOtOpU (Limit For Monkeys)</title>
  <dc:creator>Vaishnav Sudarshan</dc:creator>
  <link>https://vaishnavs.net/posts/Limit riLmOtOpU/</link>
  <description><![CDATA[ 





<section id="background" class="level2">
<h2 class="anchored" data-anchor-id="background">Background</h2>
<p>I first heard of <a href="https://en.wikipedia.org/wiki/Constructed_language">constructed languages</a>, or <em>conlangs</em>, when I heard of <a href="https://en.wikipedia.org/wiki/Esperanto">Esperanto</a>. I did my research and found out that Esperanto is a terrible conlang for reaching its purpose, which was to promote world peace, since it was so Eurocentric. I also heard of <a href="https://en.wikipedia.org/wiki/Toki_Pona">Toki Pona</a>, which combines many different languages, and is very simple due to its limited vocabulary. I wanted to make my own language, which is completely different from any other language, but has very simple grammar and vocabulary.</p>
<blockquote class="blockquote">
<p>Limit is my first conlang, and the majority of it was made before I knew any linguistics, so it understandably is really really awful. However, I guess it also means it’s less overcomplicated that my later conlangs.</p>
</blockquote>
</section>
<section id="pronunciation-and-alphabet" class="level2">
<h2 class="anchored" data-anchor-id="pronunciation-and-alphabet">Pronunciation and Alphabet</h2>
<p><em>Limit</em> is written in Roman characters (for now, that is; we will introduce the real writing system later), but there are some rules to how the script works.</p>
<p>Consonants are mostly lowercase, with the only exception being the letter “L”, which is always capitalized. Each consonant is a short sound. Short vowel sounds are lowercase, while long vowel sounds are uppercase. The language is almost phonetic; the pronunciation is exactly what is written, apart from a few rules. There are no silent letters.</p>
<p>Examples for how to write and pronounce vowels:<br>
1. A short “O” like in the word “dog” would be lowercase.<br>
2. A long “A” like in the word “cake” would be uppercase.</p>
<div class="callout callout-style-default callout-note callout-titled">
<div class="callout-header d-flex align-content-center">
<div class="callout-icon-container">
<i class="callout-icon"></i>
</div>
<div class="callout-title-container flex-fill">
Note
</div>
</div>
<div class="callout-body-container callout-body">
<p>A quick note: The letter “U” (capital, which means long) does not contain a “y” sound in its pronunciation. It sounds like the o’s in the word “food” rather than the u in the word “university”.<br>
There are some vowel and consonant sounds, of course, that cannot be produced with just the Roman alphabet. Therefore, the Limit alphabet contains some extra characters as well.</p>
</div>
</div>
<section id="extra-vowel-sounds" class="level3">
<h3 class="anchored" data-anchor-id="extra-vowel-sounds">Extra vowel sounds</h3>
<ul>
<li>“%” sounds like “oo” in the word “book”.<br>
</li>
<li>“@” sounds like “ow” like in the word “now”.<br>
</li>
<li>“α” sounds like “ah” like in the word “drama”<br>
</li>
<li>“&amp;” sounds like “oi” like in the word “boy”.<br>
</li>
<li>“*” sounds like “er” like in the word “singer”.<br>
</li>
<li>“^” sounds like “on” like in the word “bon” in French (used for foreign loanwords).</li>
</ul>
</section>
<section id="extra-consonant-sounds" class="level3">
<h3 class="anchored" data-anchor-id="extra-consonant-sounds">Extra consonant sounds</h3>
<ul>
<li>“#” sounds like “zh”, like in the s in “measure”.<br>
</li>
<li>“~” sounds like “th”, like in the word “think”.<br>
</li>
<li>“β” sounds like the n in “song”.<br>
</li>
<li>“!” sounds like “sh”, like in the word “shook”.</li>
</ul>
</section>
<section id="other-adjustments-to-the-alphabet" class="level3">
<h3 class="anchored" data-anchor-id="other-adjustments-to-the-alphabet">Other adjustments to the alphabet</h3>
<ul>
<li>To make the “ar” or “or” sound, take “α” or “O” and add “*”.<br>
</li>
<li>The letter “c” is removed as its sound can be made from either “k” or “s”.<br>
</li>
<li>The letter “g” only can sound like the g in “gray”, and NOT sound like a j, like in “giraffe”.<br>
</li>
<li>The letter “j” is removed as any sound with a “j” can be made from “d#”.<br>
</li>
<li>The letter “q” is removed as any “qu” sound can be made with “kw” instead. “u”, however, is still perfectly safe as it is important for various vowel sounds.<br>
</li>
<li>The letter “x” is removed as any sound with an “x” can be made from either “ks” or “z”.<br>
</li>
<li>The letter “i” is pronounced as IPA [y], like “y” in Finnish or “u” in French.</li>
<li>The letter “L” is pronounced as IPA character of the same shape, like the “L” sound in the word “pull”.</li>
<li>Slashes indicate that some specific words are grouped together.</li>
</ul>
<p>One last thing: Limit is pronounced in an Australian accent, with the modifications from these rules.</p>
</section>
</section>
<section id="orthography" class="level2">
<h2 class="anchored" data-anchor-id="orthography">Orthography</h2>
<p>Every consonant (the default form of each phoneme, ignoring the allophonic variations) is a node representing its position in the IPA when you plot places against manners of articulation. The starting node is a hollow circle for voiceless consonants and a filled in circle for voiced consonants. You draw vectors from one node to the next to represent subsequent consonants. If a word starts with a vowel, you can start with either k or f, in accordance to the sandhi and allophony. If two consecutive consonants are the same, then the vector is a circle with radius <img src="https://latex.codecogs.com/png.latex?1">, starting from that consonant and making a full loop through the <img src="https://latex.codecogs.com/png.latex?n">-th roots of unity (where this node is the local origin), where <img src="https://latex.codecogs.com/png.latex?n"> is the number of consonants you have done before doing this repeated one, and drawing an arrow at the end before getting to that node again. For vowels in between consonants, draw a grid starting from the top-left corner of a vowel diagram to show how deep the vowel is. If the vowel is rounded, shade alternating squares (starting from the top-left corner) like a checkerboard, and otherwise, none of the squares are filled in. Specifically for /i/ and /y/ (since their rectangle would just be a point), draw an X or a ✔ on that line respectively.</p>
</section>
<section id="pronouns-and-verbs" class="level2">
<h2 class="anchored" data-anchor-id="pronouns-and-verbs">Pronouns and Verbs</h2>
<p>If you have a pronoun and a verb, you have a simple sentence, so let us start here in our journey to learn real Limit words. There is no gender or verb conjugation for each pronoun in Limit, so this should be simple.</p>
<section id="pronouns" class="level3">
<h3 class="anchored" data-anchor-id="pronouns">Pronouns</h3>
<table class="caption-top table">
<thead>
<tr class="header">
<th>English</th>
<th>Limit</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>I</td>
<td>LI</td>
</tr>
<tr class="even">
<td>You</td>
<td>dI</td>
</tr>
<tr class="odd">
<td>He/She/It</td>
<td>krI</td>
</tr>
<tr class="even">
<td>We</td>
<td>LId</td>
</tr>
<tr class="odd">
<td>You (plural)</td>
<td>dId</td>
</tr>
<tr class="even">
<td>They</td>
<td>krId</td>
</tr>
</tbody>
</table>
<p>To make any of these pronouns formal, just add the prefix “yU”.<br>
To make any of these pronouns insulting, just add the prefix “yoL”. If you are talking directly to someone, add the suffix “*” or “p*” for “dId” and “dI” respectively.</p>
</section>
<section id="verbs" class="level3">
<h3 class="anchored" data-anchor-id="verbs">Verbs</h3>
<p>Present tense: Suffix “UL”<br>
Past tense: Suffix “Uz”<br>
Future tense: Suffix “Uk”<br>
To make something infinitive, remove the Uz/UL/Uk and add the suffix “Up”.<br>
To negate a verb, add the suffix “O#U” or “#U” (depending on if it ends in a vowel or consonant) at the very end of the word.</p>
<section id="example" class="level4">
<h4 class="anchored" data-anchor-id="example">Example</h4>
<ul>
<li>To eat is “brikUp”.<br>
</li>
<li>“I did not eat” would be “LI brikUzO#U”.</li>
</ul>
</section>
</section>
</section>
<section id="syntax" class="level2">
<h2 class="anchored" data-anchor-id="syntax">Syntax</h2>
<p>Here are some rules for sentence structure:</p>
<ul>
<li>The order of a declarative sentence is Subject Object Verb.<br>
</li>
<li>Adjectives always come after nouns, attached by a slash, without spaces.<br>
</li>
<li>Articles come after nouns as well, also attached by a slash without spaces.<br>
</li>
<li>If there is an article and an adjective, the adjective comes after the article, and the adjective and the article are combined with slashes as well.<br>
</li>
<li>Adverbs come before the verb or adjective that they modify, with a backslash with no spaces. If they modify an adjective, then it goes before the noun.<br>
</li>
<li>There is no distinction between proper and common nouns.<br>
</li>
<li>Prepositions work the same way as in English.<br>
</li>
<li>Objects, like in English, do not have to just be nouns but also any verb phrase that acts as a noun. Predicate adjectives and predicate nominatives also count as objects.<br>
</li>
<li>Prepositional phrases (like “in the house”) count as objects as well.<br>
</li>
<li>Indirect objects come right before direct objects.<br>
</li>
<li>Indirect objects have the suffix “b”, or “Ob” if the word ends in a consonant.<br>
</li>
<li>Predicate adjectives would actually be adverbs, as they modify the word “bLIvUp”.<br>
Examples:<br>
Write “I like to eat” in Limit syntax and spelling.<br>
I tU Et LIk<br>
Write “I give you a green box” in Limit syntax and spelling.<br>
I yUhU boks/A/grEn giv</li>
</ul>
</section>
<section id="inflections" class="level2">
<h2 class="anchored" data-anchor-id="inflections">Inflections</h2>
<p>To inflect a word ending in O, make the final consonant of the inflection thing voiceless. For example, the plural of “riLmO” (monkey) will be “riLmOt” instead of “riLmOd” (riLmOd is not a real word for that reason). And, the possessive of “riLmO” will be “riLmOf” instead of “riLmOv”. Likewise, you’d say “riLmOkE” instead of “riLmOgE”, “riLmOpU” instead of “riLmObU”, and “riLmOsA” instead of “riLmOzA”.</p>
</section>
<section id="punctuation" class="level2">
<h2 class="anchored" data-anchor-id="punctuation">Punctuation</h2>
<p>Commas are written as “~”.<br>
Periods are written as “-”.<br>
Quotation marks are written as “+” on either end of the quote.<br>
Question marks are just a word, that being “LE”.</p>
</section>
<section id="possession" class="level2">
<h2 class="anchored" data-anchor-id="possession">Possession</h2>
<section id="possessive-pronounsadjectives" class="level3">
<h3 class="anchored" data-anchor-id="possessive-pronounsadjectives">Possessive pronouns/adjectives</h3>
<table class="caption-top table">
<thead>
<tr class="header">
<th>English</th>
<th>Limit</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>My/Mine</td>
<td>“LIv”</td>
</tr>
<tr class="even">
<td>Your/Yours</td>
<td>“krIv”</td>
</tr>
<tr class="odd">
<td>His/Her/Its</td>
<td>“dIv”</td>
</tr>
<tr class="even">
<td>Our/Ours</td>
<td>“LIdOv”</td>
</tr>
<tr class="odd">
<td>Your/Yours (plural)</td>
<td>“krIdOv”</td>
</tr>
<tr class="even">
<td>Their/Theirs</td>
<td>“dIdOv”</td>
</tr>
</tbody>
</table>
<p>How to use a possessive noun for a person (for example, “That is Bob’s”):<br>
Add “Ov” to the end of their name if it ends in a consonant, otherwise add “v”.<br>
If the noun it modifies is plural, then add “Od” or “d”.<br>
Examples:<br>
My books are big = “zO*pOd/LIvOd Lib blivUL”<br>
The world is mine = “h%d/vU LIv blivUL”</p>
</section>
</section>
<section id="adjectives" class="level2">
<h2 class="anchored" data-anchor-id="adjectives">Adjectives</h2>
<section id="articles" class="level3">
<h3 class="anchored" data-anchor-id="articles">Articles</h3>
<p>The (singular): vU<br>
The (plural): vUd<br>
Indefinite articles are implied if there is no article.<br>
Remember, the articles go after the noun and before another adjective, connected with a slash.</p>
</section>
<section id="demonstratives" class="level3">
<h3 class="anchored" data-anchor-id="demonstratives">Demonstratives</h3>
<p>This: #%t<br>
That: #at<br>
Those: #atOd<br>
These: #%tOd<br>
Demonstratives go after the noun and before another adjective, connected with a slash, just like articles. If they are pronouns, then just treat them as pronouns instead.</p>
</section>
<section id="plurals" class="level3">
<h3 class="anchored" data-anchor-id="plurals">Plurals</h3>
<p>Adjectives have to agree with their noun in number. If the noun is singular, the adjectives will also be singular, and if the noun is plural, the adjectives will also be plural. To make a noun or an adjective plural, add a “d” if it ends in a vowel, and add an “Od” if it ends in a consonant.<br>
Adjective phrases also go after the noun, and just the first word of the adjective phrase will be combined with a slash to the noun.<br>
There will also be a slash after the last word, if the adjective phrase is more than a single word.</p>
</section>
</section>
<section id="adverbs" class="level2">
<h2 class="anchored" data-anchor-id="adverbs">Adverbs</h2>
<p>To turn an adjective into an adverb, add the prefix “.@”.<br>
This is analogous to adding an “ly” at the end in English.<br>
Adverbs go right before the adjective, verb, or adverb that they modify.<br>
Example:<br>
The word for “real” is “gOhO”, which means the word for “really” is “.@gOhO”.<br>
I am really good = “LI .@gOhO\LimitO#U blivUL”</p>
</section>
<section id="allophony" class="level2">
<h2 class="anchored" data-anchor-id="allophony">Allophony</h2>
<p>Apply these variations in order:</p>
<ul>
<li>Any nasal followed directly by a vowel must be turned into a voiceless trill of the same place of articulation
<ul>
<li>For example, the “m” in “Limit” is pronouned like the “pppp” in Proto-Zorbbbb.</li>
</ul></li>
<li>Any word starting with a vowel is pronounced with an “f” if the vowel is rounded and a “k” if the vowel is unrounded.</li>
<li>Any word ending with a vowel must be pronounced with the same consonants that are added if a word starts with a vowel, except rounded and unrounded are reversed.</li>
<li>Any word ending with a consonant (which is all of them, at this point) must be pronounced, after the consonant, with a monkey scream (a shriek of [ɐ] at the top of your lungs) if the consonant is voiced and a grunt (a very low-pitch, almost confused-sounding [œ]) if the consonant is voiceless. This additional noise is never written. Also, the final consonant is an ejective consonant.</li>
<li>Starting stops become fricatives, and starting fricatives become stops. This part only applies to pronunciation, not orthography.</li>
</ul>
</section>
<section id="numbers" class="level2">
<h2 class="anchored" data-anchor-id="numbers">Numbers</h2>
<p>Base 10 is used, like normal.<br>
One shorthand is implemented; whenever there is a 1 followed by a 0, it is written as θ.<br>
Numbers are written as normal Arabic numerals, but obviously they are said differently.<br>
0: “fA”<br>
1: “hα”<br>
2: “rO”<br>
3: “d#U”<br>
4: “yA”<br>
5: “.a”<br>
6: “brU”<br>
7: “,O”<br>
8: “we”<br>
9: “gI”<br>
To get more numbers, you do the following:<br>
Write each digit in the bigger number as the sum of each digit times a power of <img src="https://latex.codecogs.com/png.latex?10">. For example, <img src="https://latex.codecogs.com/png.latex?243"> would be <img src="https://latex.codecogs.com/png.latex?2%20%5Ccdot%2010%5E2+4%20%5Ccdot%2010%5E1+3%20%5Ccdot%2010%5E0">.<br>
You may know that “time ten to the power of” can also be written as “E”. In Limit, the symbol for this is ““=”, pronounced “sigmα”. Fun fact: this word also means “and”.<br>
You would write the each place value from highest exponent to lowest.<br>
Instead of saying plus, you would just combine each term with a slash.<br>
Units digits do not need to be written as a=0, just a.<br>
Back to the example of 243, in Limit you would say this as:<br>
2=2/4=1/3, and pronounce this as rO=rO/yA=hα/jU, and remember that = is pronounced as sigmα.<br>
For negative numbers, add the suffix “yO”.<br>
For ordinal numbers, add the suffix “hO”, after the “yO” if it is there.<br>
For fractions, just use the postposition for “in”, which is the suffix “krA” or “OkrA”. There will be a space after that.<br>
You can also just list each digit, but then you must indicate the decimal point when applicable, which is pronounced as “%nd” and is written as “*”.<br>
Example:<br>
You would say “31.4th” as “jU<img src="https://latex.codecogs.com/png.latex?h%CE%B1/h%CE%B1/yA">hαyOhO”.</p>
</section>
<section id="questions" class="level2">
<h2 class="anchored" data-anchor-id="questions">Questions</h2>
<p>Just say the equivalent declarative sentence, then add “LE-” (which means question mark) to the end.<br>
Phrasing Examples:<br>
“Which one do you like?” -&gt; “You one/which like LE-”<br>
“How are you?” -&gt; “You how are LE-”<br>
Here’re the interrogative words:<br>
What:</p>
</section>
<section id="commands" class="level2">
<h2 class="anchored" data-anchor-id="commands">Commands</h2>
<p>State the equivalent in a future tense declarative sentence, and speak in 2nd person. Use the word for please, “hok”, at the end of the sentence, after the verb.<br>
Phrasing Examples:<br>
“Go to bed.” -&gt; “You will to bed go hok-”<br>
Also, instead of saying “hok”, you can say “bOLOdOwO#O”, which is short for “bU LI dI wopLUkO#U”, which means something along the lines of “or I will kill you”.<br>
Fun fact: the word “hok” is actually a loanword from Proto-Zorbbbb.</p>
</section>
<section id="prepositions" class="level2">
<h2 class="anchored" data-anchor-id="prepositions">Prepositions</h2>
<p>First, be sure to note that Limit uses a suffix for prepositions (so they are actually postpositions) like “in”, “at”, “during”, “of”, etc; this means anything that gives the position or time, not something that is being headed towards. This suffix is “gE”, or “OgE”, depending on if the word ends in a vowel or consonant.<br>
There is also a suffix for something you are heading to. This includes words such as “before”, “to”, or “for”. The suffix is “bU”, or “ObU”, depending on if the word ends in a vowel or consonant.<br>
Finally, for something you are coming from, such as “from”, “after”, or “past”, the suffix will be either “zA” or “OzA”.</p>
</section>
<section id="general-rule-of-affixes" class="level2">
<h2 class="anchored" data-anchor-id="general-rule-of-affixes">General Rule of Affixes</h2>
<p>If the word ends in a consonant, and the suffix starts with a consonant, then put an “O” between them.<br>
If the word ends in a vowel and the suffix starts with a consonant, or the other way around, then there is no need for an extra “O”.<br>
This same intuition is to be applied to prefixes.</p>
</section>
<section id="conjunctions" class="level2">
<h2 class="anchored" data-anchor-id="conjunctions">Conjunctions</h2>
<p>The conjunctions (subordinating and coordinating, and also including relative pronouns) are:<br>
And: “=”<br>
Or: “bI”<br>
But: “pA”<br>
So: “skibidE”<br>
If: “*m”<br>
Note for the next two: If these account for plural antecedents, then add a “d”.<br>
Who/That/Which (as a subordinate): “Ligmα”<br>
Whose: “Ligmαv”</p>
</section>
<section id="abbreviations" class="level2">
<h2 class="anchored" data-anchor-id="abbreviations">Abbreviations</h2>
<p>Just like how there’s “ts pmo” for [censored], in Limit there are abbreviations too. Except, between consonants, you must add a “@”. For example, bU LI dI wopLUkO#U becomes bOLOdOwO#O. Also, negation affixes are important enough to count as their own word, so just put #O at the end if it is negated, like in this one.</p>
</section>
<section id="comparatives-and-superlatives" class="level2">
<h2 class="anchored" data-anchor-id="comparatives-and-superlatives">Comparatives and Superlatives</h2>
<p>How you would phrase this:<br>
[Subject] [Person, indirect form] [Attribute, locative form] [Win/Lose].<br>
The [Person, indirect form] can be removed if the sentence is superlative.<br>
Note that the indirect form and the locative form both have a postpositional ending, so it may be confusing.<br>
The attribute must be a verb. Nouns, adjectives, and adverbs must be reworded.</p>
</section>
<section id="vocabulary-in-progress" class="level2">
<h2 class="anchored" data-anchor-id="vocabulary-in-progress">VOCABULARY (in progress)</h2>
<p>Alright, now that you know all the grammar rules, let’s get into the vocabulary, so you can actually speak in Limit. There aren’t that many vocabulary words, instead you must take the basic vocabulary words and combine them. To negate a word (to make it opposite, basically) add the suffix “O#U” or “#U”, which works for verbs, adjectives, nouns, etc. The core vocabulary is mainly for neutral or negative connotation, and to get positive connotation, just negate it.</p>
<p><strong>Nouns:</strong><br>
Person: nUvak<br>
Monkey: riLmO<br>
Ignorance: zO*p<br>
World: h%d<br>
Non-primate organism: tEkU<br>
Tool: dOmα*<br>
Name: Eskα<br>
Age: derUm<br>
Evilness: Limit<br>
Time: dUrin<br>
Motion: cU<br>
Size: pLevI<br>
Color: snib<br>
Goal: wOksO<br>
X-axis: dAb<br>
Y-axis: vEb<br>
Z-axis: LUb<br>
Nature: nuk<br>
Quantity: LodO<br>
Food: gla*nE<br>
Set: rimU</p>
<p><strong>Adjectives:</strong></p>
<p>Evil: Limit<br>
Small: pLevI<br>
Slow: kU<br>
Incorrect: kIf<br>
Old: derUm<br>
Ugly: t!Untab<br>
Cold: mEkO<br>
Late: dUrin<br>
Yucky: gla*nE<br>
Black: snib<br>
Blue: mraflet<br>
Yellow: krUgnip<br>
Red: yundrask<br>
Liquid: vUgis Weird: kitU</p>
<p><strong>Verbs (infinitive):</strong><br>
Hate: netAbUp<br>
Go: drekInUp<br>
Use: gUatUp Make: wopLUp<br>
Not know: zO*pUp Steal: prIksUp<br>
Want: kutlOrUp</p>


</section>

 ]]></description>
  <category>Linguistics</category>
  <guid>https://vaishnavs.net/posts/Limit riLmOtOpU/</guid>
  <pubDate>Wed, 02 Jul 2025 18:30:00 GMT</pubDate>
  <media:content url="https://vaishnavs.net/posts/Limit riLmOtOpU/LimitFlag.png" medium="image" type="image/png" height="81" width="144"/>
</item>
</channel>
</rss>
