In languages with genders you need fewer unique words for gender-related concepts. For example English (genderless) has "boy" and "girl", while Spanish (male and female) has "niño" and "niña".
Not sure about spanish, but in portuguese, as a general rule, you decide the gender of an object by the last caracther. For instance “cadeira” (chair) is feminine while “livro” (book) is masculine.
Basically, most feminine words end with an “a” while masculine words end with an “o”, although there are some words that end with other letters whose genders is not that easy to identify. For instance “árvore” (tree) ends with an “e” and is feminine (“a árvore”), while “peixe” (fish) also ends with an “e” but is masculine (“o peixe“).
Er, that sounds backwards to me. I thought you put the a on the word because it is feminine. You're saying the word is feminine because there's an a on it?
Strictly speaking there's no causality in either direction. A word's gender determines what it takes for other words to agree with it, while the form of the word itself can be anything. A word can always be irregular.
But not every word can be irregular. Mostly the words that belong to a gender will match a set of patterns, and the words belonging to another gender will match a different set of patterns. If you're lucky, you can learn a word from some usage that makes its gender explicit (and for irregular words, this is the only way you can learn about their irregularity). But often all you have to go on is the word, and in that case, when you want to use it, you have to make a choice. You'll do that based on the form of the word.
-----
If you want some examples of how gender irregularity in nouns works, here are a few different phenomena in Latin:
- An adjective in the first/second declensions has masculine (singular) endings -us, -ī, -ō, -um, -ō, -e and feminine endings -a, -ae, -ae, -am, -ā, -a. If you see one of these endings, and you know the adjective is first/second declension¹, then you've fully specified the gender of the adjective. There are no exceptions.
- First and second declension nouns mostly follow this pattern. Lana means wool and, as the -a suffix would lead you to expect, it's feminine. Campus means field as, as the -us suffix would lead you to expect, it's masculine. What this means is that "white wool" is lana alba and "a white field" is campus albus.
- Trees are weird. They are second declension (or sometimes fourth; pretend that's not true), appearing to be masculine, but instead they're feminine. So you'd have pinus alba, a white pine tree, or quercus alba, a white oak tree.
- There's a short list of profession terms that are first declension, appearing to be feminine, but that are nevertheless masculine. So it'd be agricola albus, a white farmer, or nauta albus, a white sailor.
- What about corpus? Well, it's neuter. Corpus album, a white body. Corpus is a third declension noun, and the third declension works completely differently. The apparent -us ending is misleading; the root of this noun is actually corpor- and the suffixes, of course, belong to the third declension.
- What do you do if you run into a word you don't know how to deal with? Pretend it's normal. Manus is a Latin word that means "hand"; it appears to be masculine, but it's feminine. It turns out that referring to hands is common enough that Spanish speakers today still remember that this masculine-looking word, now mano, is actually feminine. But we may compare Biblia, which is feminine in Spanish today despite the fact that in Latin it was neuter. It's feminine now because of that -a ending.
¹ That isn't actually true; the neuter suffixes are mostly just masculine suffixes except for one that is feminine. There are no distinctive second-declension neuter suffixes. But the suffixes by themselves are sufficient to distinguish masculine gender from feminine.
I'm glad that Portuguese doesn't try to trip up foreigners on purpose here, like Spanish does with "el agua" (which is still a feminine word, but takes the masculine article because "la agua" is too hard to pronounce).
French does this too: "mon" is masculine, "ma" is feminine, "ami" is masculine (so "mon ami" is correct), "amie" is feminine, but you have to say "mon amie". Some things contract (like "n'est", "c'est", "l'homme"), but not "ma."
Except words ending in "ma" that came from Greek (o problema, o estigma) which are masculine, while those from Latin (a alma) are feminine as expected. In Spanish it's basically the same. A Spanish teacher gave me a nice mnemonic: "-ma is masculine, like your mother." I've never forgotten that.
This is often apparent from the sound or spelling of a word, rather than any genderedness in its concept. A chair is une chaise (feminine), and it would be weird for chaise to be masculine. It’s not because the chair is feminine, it’s because the word is. There are some rules that help you figure out the gender based on the word (often what sound the word ends with), but there are exceptions to those rules.
Livre (book) is actually an example of where the gender creates a different meaning: un livre is a book, while une livre is a pound (the unit of weight).
If you ever feel inclined to learn Hindi there is more to grapple with. The verb gender is sometimes set by the gender of the object, sometimes by the gender of the object. Which way this will go loosely depends on tense.
On one hand I agree genders are pointless for chair and book. On the other hand, many nouns are the female or augmentative version of the base word. From your examples: "silla" (f, chair) vs "sillón" (m, sofa), and "libro" (m, book) vs "libreta" (f, notebook).
It wasn't about diving in particular, but rather post-match revisions and sanctions becoming more common to punish unsportsmanship. Add VAR in recent years, and the newest "1 minute out" rule for fake injury, and today players don't gain anything from diving.
Doesn't this new law overlap with the existing system? A manufacturer within the EU is already paying taxes, which in part should be used for managing waste. If they buy the packaging materials from another EU company, well that company is also paying taxes already. If they are importing from outside the EU, the packaging material pays taxes.
The language also takes backwards compatibility very seriously, anything that goes into std "must be maintained forever". It is also argued that a large stdlib means the maintainers have less time to work on the language itself.
I understand not every language can have Go's amazing stdlib, but I would much prefer Pyhton's approach where every now and then some package/function from the stdlib gets deprecated/removed. Rust's 3rd party ecosystem is the worst thing from the language, worse than the compile times.
I think a good metric for "boring" technology, at least for languages/frameworks, is how painful the process of updating an abandoned/unmaintained project after 9-12 months is. NodeJS itself qualifies as boring, but the entire ecosystem around it is still a mess.
The same UEFA that added redundant matches and teams to the Champions League for money, and that came up with the Nations League because they wanted to extract more money from the national teams?
While I agree the extra CL games are not a great idea, they are not a very bad one either.
The Nations League is a good idea, for a number of reasons:
1. It gives smaller teams, like Gibraltar, Malta etc, a chance to play competitive football against teams their level and a chance to actually get better. In the old system, the only way for Gibraltar to play a competitive game, was to play in the Euro or WC qualifications, against the likes of Germany, Spain, England etc and get trashed. They can't get better if they have no chance to win.
2. Nations League brings money to the various FAs, a google search suggests anything between €750,000 to €10.5 million, as opposed to extracting money from the FAs.
3. The Nations League games replaced a bunch of friendlies. Now those games matter.
The Super League was decidedly not UEFA's - UEFA even announced sanctions against the organisers (though I think those were repealed by a court), because it was going to compete with UEFA's leagues.
For public services you can tell people to use another device, or provide a way to schedule an appointment in-person that is accessible using old browsers.
Seems like you’re getting hate but this is how the world works. Uber just has to support the devices that their market uses. And especially for visas the government is free to make the public bend to whatever arbitrary requirements they develop for using their byzantine systems.
You you can make a law that requires such businesses to use perfectly good technology standards that are widely supported instead of whatever EEE crap the latest Chrome comes with.
I remember years ago when websites would have buttons "best viewed in Internet explorer 4.0". We're past those days, but only because it's implied "use chrome, maybe webkit, we didn't test on Firefox"
I agree, but one thing is to demand all your users to be on the latest Chrome, and another one is to support browsers that are no longer maintained and contain security issues (IE). If we discourage people from driving old insecure cars, we can also discourage people from using old insecure browsers.
Ideally we could section off some minimal baseline functionality that could be implemented more securely than the whole modern stack. Just HTML and a little CSS or something. Then mandate that, at least, services provided by the state should be accessible in this baseline functionality mode.
reply