My argument is purely pedantic. Pedantry is the lifeblood of programmer “humour”.

I’m not arguing that we should adopt zero-based numberingin real-life human applications. I am arguing that in zero-based numbering, the label “zeroth” refers to the same ordinal as “first” in one-based numbering. I am poking fun at the conversion between human one-based numbering and computers’ zero-based numbering. That is why I am saying it should be called zeroth(); because human language should adapt to match the zero-based numbering their tools use. Whether I actually mean what I say—well, I leave that up to you.

It does not matter why indexes start from zero in computing. The memory offset argument is only salient if you are using it as an argument for why computers should use zero-based numbering. It is not an argument against the properties of zero-based numbering itself.

Zero-based indexing redefines the meaning of the labels “first”, “second”, “third”, and so on. It adds a new label, “zeroth”, which has the same ordinal value as “first” in one-based indexing. The word “first” does not mean “the element with the lowest index” in zero-based indexing.

If you are using a zero-based numbering system, you would absolutely say that array[2] is the final element in the array, that element having the ordinal label “second”, and yet the length of the array is 3 (cardinal). There is no fundamental connection between the ordinal labels “zeroth”, “first”, “second”, and “third” and the cardinal numbers 0, 1, 2, and 3. The similarities are purely an artefact of human language, which is arbitrary anyway. You can make an equally mathematically valid ordinal numbering system that assigns “third” to the element with the smallest index, “fourth” to the next-smallest, and so on. That ordinal numbering system is mathematically coherent and valid, but you’re just causing trouble for yourself when it comes time to convert those ordinals (such as array indexes) into cardinals (such as memory locations or lengths of fencing to buy).

You can make an argument for why one-based numbering is more convenient and easier to use, but you cannot use the notion that zero-based numbering doesn’t make sense given the assumed context of one-based numbering as an argument for why zero-based numbering is invalid.

I encourage you read up what is meant by “zero based numbering” because you and everyone else who has replied to me has tried to use “but that’s not how it works in one-based numbering” as an explanation for why I’m wrong. This is as nonsensical of an argument as trying to say i (the imaginary unit) is not a number because it’s not on the number line. It’s only not a number in the domain of the real numbers. Similarly, zero-based numbering is only nonsensical in the context of one-based indexing.

It does not matter why indexes start from zero. The memory offset argument is only salient if you are using it as an argument for why computers should use zero-based numbering.

Okay, I will admit, you got me there. I did confuse indexing with numbering. From now on I will use the term “numbering” instead.

It is entirely how ordinal numbers work in zero-based numbering. There is no “right way” for ordinal numbers to work. You can create a valid ordinal numbering system starting from any integer, or just some other ordered list. You cannot assume one-based numbering is “correct” and use it as an argument against numbering beginning from any other number.

I encourage you read up what is meant by “zero based numbering” because you and everyone else who has replied to me has tried to use “but that’s not how it works in one-based numbering” as an explanation for why I’m wrong. This is as nonsensical of an argument as trying to say i (the imaginary unit) is not a number because it’s not on the number line. It’s only not a number in the domain of the real numbers. Similarly, zero-based numbering is only nonsensical in the context of one-based indexing.

Zero-based numbering would number “foo” as the zeroth element, “bar” as the first element, and “baz” as the second element. “zeroth”, “first”, and “second” are labels representing ordinals. Your list has a length of 3 (which is a cardinal quantity unrelated to ordinals).

Although, I would like to point out, it is perfectly valid to construct an ordinal labelling system that assigns “fifth” to the element with the lowest index, “sixth” to the next, and so on. That system is mathematically coherent but it is just troublesome to when it comes time to convert ordinal numbers (such as the index of the last fence-post) to cardinal numbers (such as the length of fence to buy).

But this is now getting into the weeds of pure mathematics and most people here are engineers.

That’s because the word “first” in first() uses one-based indexing. In true programmer fashion it would have been called zeroth() but that is wholly unintuitive to most humans.

I maintain that the element with the lowest index is called the “zeroth” element in zero-based indexing and “first” in one-based indexing. The element with index N is the Nth element.

Bullshit.

Every programmer knows that 'A' in ['A', 'B', 'C', 'D'] would be the 0th item; the first item is 'B'

Rulers measure cardinal quantities and not ordinal ones. There is no cardinal numbering scheme that starts at 1, all of them “start” at 0. For ordinal numbering schemes, the symbols are arbitrary anyway and you can start with whatever you want. It’s equally valid to start with 1, 0, -1, A, or “aardvark”. The only benefit to picking 1 as the start is to make it easier to count with your fingers while picking 0 lets you easily convert an ordinal quantity to a cardinal one.

Can you not realise what is and is not a joke?

Closest I can get is a statue of nativist racist beating up immigrant

What are the implications of this?

Other people have described the health effects, so I’ll describe the chemistry. Fats are made of long chains of carbon atoms surrounded by hydrogen atoms attached to a “head”, which is made of other elements or structures. Carbon atoms normally can make a total of 4 bonds. Hydrogen atoms can make 1 bond.

Carbon being able to make 4 bonds means that in the chain of carbon and hydrogen atoms in fat molecules, each carbon atom makes a bond with the carbon atom before it in the chain, a bond with the carbon atom after it in the chain, and then bonds with two hydrogen atoms separately off to the side. This makes a total of 4 bonds. If all of the carbon atoms in the chain are like this, that’s “saturated fat”, because the chain of carbon is completely “saturated” with hydrogen atoms.

(Hydrogen atoms are white, carbon atoms are black, oxygen atoms are red)

Saturated fats have the often desirable property of being able to be tightly packed together, and thus are typically solid at room temperature. Butterfat is mostly saturated fat.

However, carbon atoms can also make a double bond with other carbon atoms. If a particular carbon atom in the chain makes a double bond with the carbon atom before it, it could cause a bend in the chain of carbon atoms. In that case, it also means that those particular carbon atoms in the chain that have formed a double bond with each other only have 1 available bond left (after also forming a separate single bond with the carbon atom before or after it), so it can only bond with one hydrogen atom. These are, therefore, called “unsaturated fats”, and because they don’t pack together easily, they are typically liquid at room temperature.

If there is a single double bond in the chain, it’s a monounsaturated fat.

If there are two or more double bonds, it’s a polyunsaturated fat.

Notice how the hydrogen atoms connected to the double-bonded carbon atoms in unsaturated fats can be connected to either the same side or the opposite sides of the two hydrogen atoms. If they’re on the same side, they are called cis-unsaturated fats. If they’re on opposite sides, they are trans-unsaturated fats, or trans fats in short.

This is oleic acid, a cis monounsaturated fat commonly found in many vegetable oils:

While this is vaccenic acid, a trans-monounsaturated fat. It is found naturally in butter and human milk and is not particularly bad for you:

Note that this is NOT the same picture as the one I showed for saturated fat. The 7th and 8th carbon atoms from the left are double-bonded and, therefore, are each missing a hydrogen atom. The one remaining hydrogen atom on each is bonded on opposite sides.

Note that trans-unsaturated fats are also pretty straight. This means that they can also pack together with saturated fats to make a solid product at room temperature.

“Hydrogenation” is the process of adding hydrogen to unsaturated fats to saturate them. This means that liquid oil can be processed into a solid product. That’s how margarine and shortening are made. In previous years, partially hydrogenated oils that weren’t fully hydrogenated could leave substantial quantities of trans-unsaturated fats left in the product, but after health concerns, many countries’ food safety authorities banned these artificial trans fats. Fully hydrogenated fats consist of only saturated fats since they have been “fully” hydrogenated, and that is what food manufacturers have been doing instead.

The exact data is Figure 1, chart A. It seems the mean is around 4,000-5,000 μg/g, which is indeed 0.4-0.5%

I really had to run a fact check on this but it really does seem to be true.

Brains are 0.5% plastic by weight and with an average human brain mass of 1.3 kg, that means humans, on average, have 6.5 g of plastic in their brain

Password is necessary for two-factor authentication. The factors of authentication are something you know (like a password), something you have (like a cell phone), and something you are (like a biometric).

An example of three-factor authentication would be this—imagine a spy going into a secret bunker. They need to scan their iris, insert a key card, and then enter a passcode before the door opens. This has all three factors of authentication; the passcode is something they know, the key card is something they have, the iris scan is something they are.

If it just sends a code to your phone, that’s one-factor authentication (something you have). Anyone with your phone can get into your account. Unless, of course, your phone hides its notifications and you have a screen lock. Then that’s actually two-factor authentication because you also need to know the phone PIN or have the biometric.

If it just asks for a password, that’s one-factor authentication (something you know).

If it asks for your password and then sends a code to your phone, which you need a fingerprint or face scan to unlock, you have achieved three-factor authentication.

Edit: Interesting tidbit—in the USA, you can rent a mailbox at the post office to receive mail when you don’t want to give out your real address. Useful for privacy reasons. I’m sure they have similar things in other countries. These mailboxes come with a key. This is actually two-factor authentication, because the keys usually don’t have the mailbox number written on them! So you have to have the key and also have to know which mailbox among the hundreds at the post office it opens.

TOTP is standardised by RFC 6238 so all TOTP clients must comply with the standard and therefore work equally well. Pick the one whose UI you like the most and is otherwise good enough for your use case and personal preferences. It’s similar to arguments over CPU thermal paste—its presence or absence makes a much larger difference than the method of application.

You do, however, want to pick something that is free and open-source and also popular. Google Authenticator (closed source) definitely is a functional TOTP client but you have to trust that the Google engineers have done a good job building a secure app. Since it’s Google, they probably have, but a principle in security is that you should not have to trust more people than absolutely necessary.

Yes, but this is like replacing the front door of your house with a bank vault door. Yes, it’s more secure, but there is a point of “reasonably secure enough” for most people and at some point, you are just inconveniencing yourself for no tangible gain.

It’s not a hard concept. In almost every well-designed security system, the weakest links are invariably the humans

The passwords are stored locally. You can test this yourself by turning off your WiFi or disconnecting your Ethernet cable and then going to about:logins. All the passwords will still be there.

It would probably be some synthetic American government cheese-like product.

Which I’m sure if the Germans had come up with it and not the Americans would also be described as being nutritious

“I like Apple devices because they respect my privacy”

This is not an opinion. You have made a statement of fact. And you are wrong.

At law, something being publicly available does not mean it is allowed to be used for any purpose. Copyright law still applies. In most countries, making something publicly available does not cause all copyrights to be disclaimed on it. You are still not permitted to, for example, repost it elsewhere without the copyright holder’s permission, or, as some courts have ruled, use it to train an AI that then creates derivative works. Derivative works are not permitted without the copyright holder’s permission. Courts have ruled that this could mean everything an AI generates is a derivative work of everything in its training data and, therefore, copyright infringement.