You don't need to know the bottom left axis number. We do have to assume the graph is linear, and not some kind of negative exponent log graph. But given the rest of the content, I think that is safe to assume.

Any company that experiences significantly more growth than they were planning for will have capacity issues.

The priorities are most inline with that. The are way beyond the point that they can just add more hardware. They need to make the backend more efficient, and all the stated goals are about helping there.

You're correct, with MIT there are a lot less restrictions. I can make GPL or pretty much any other license. Including one that I sell and never have to release the source of.

The latter option means if you make a product off of it, you have no obligation to share or even fund upstream development. This kind of situation has strangled other products.

Consider if Linux was released under MIT. Then companies like Oracle and RedHat (now owned by IBM) who have strong incentives to keep improvements to themselves and fund a lot of development would never share those improvements. Linux is the most used operating system in the world because of _everyone_ contributing back. But a MBA would want to privitize the profits.

If you care about the long term openness of a product, then GPL is hard to beat.

You don't understand the argument of why people might want to install their own OS on a device they own. And then say you won't buy another iPhone because you don't like their software... It sounds like you _do_ understand the argument.

I greatly dislike Apple software, but I think their hardware is quite nice. I would buy apple hardware if it wasn't handy-caped by their OS.

It used to be said that Apple was a hardware company that happens to make an OS. This argument never made sense to me, because while they make good hardware they very clearly don't want people to use it.

It seems apple has a service, with an easily rotated key and an agreement with providers. If the key _Apple_ uses is compromised, they can rotate it.

BUT, apple knows _EXACTLY_ who I am. I attest to them using my hardware, they know _EXACTLY_ which hardware I'm using. They can ban me or my hardware. They then their centralized service gives me a blind token. But apple, may, still know exactly who owns which blind tokens.

However, I cannot generate blind tokens on my own. I _MUST_ talk to some centralized service that can I identify me. If that is not the case, then any single compromised device can generate infinite blind tokens rending all the tokens useless.

There is now a memory buffer that the user space and the kernel is reading, and with that buffer you can _always_ do any syscall that io_uring supports. And things like strace, eBPF, and seccomp cannot see the actual syscalls that are being called in that memory buffer.

And, having something like seccomp or eBPF inspect the stream might slow it down enough to eat the performance gain.

It was over 10 years later that any of us heard of this much older resistor. It's kinda it funny how similar we are to them, nearly shared a name, and completely unaware of each other.

The world needs more places where people can explore their curiosity of how things work.

It's hard to know what exactly your security concerns are here, but if you look at the current ecosystem of using containers and package registries, Nix is pretty clearly a solid contender, security-wise.

Both the Gmail web interface and the Gmail API allow the ability to set all the labels for a message. This can effectively enable your desired functionality. But IMAP can only deal with "folders", and cannot correctly decide when to remove a single label or remove all other labels when it sees a move action.

IMAP also only deals in messages and not threads. Gmail labels also technically only apply to messages, but the web interface shows the union of all labels of a thread. This is another decision I agree with. It means that when someone explicitly adds me to a thread, the whole thread gets highlighted in my feed.

I personally really enjoy the Gmail/fastmail/proton behavior so please don't make another political campaign to make things worse again. We have enough of those.

But fundamentally the "folder" view of email does not work. A single message often needs to be in several different folders simultaneously. And when the thread is spread across many folders, there needs to be a way to see the whole thread.

The only way to accomplish this is with email tags or labels. These are implemented by nearly all successful email companies. Gmail, Fastmail, and Proton are examples. Labels are a fundamental feature in this day and age, and neither IMAP nor POP can handle them gracefully.

Gmail is so big that when Outlook, Apple Mail, and even Thunderbird connect to it, they do an OAuth exchange and then talk over a proprietary protocol.

JMAP may have poor adoption, but it's the only open protocol that understands labels well. The lack of adoption is mostly due to email providers not implementing it. There is not a lot of incentive for clients to implement it for the few providers. And providers would prefer you use their web clients anyway, as then they control access to your email.

But even beyond that, most file formats have a bit of a header at the start of the file that declares the actual format of the file. Browsers already can understand that and use the correct render for a file without an extension.

I dare say that developers like environment variables more than before. Consider that Docker images, and hence Helm charts, are entirely controlled via environment variables. These very popular dev tools suffer from the same problem of having near-zero easy discoverability of what those environment variables might be. Yet they are very popular.

But I don't think Make usually uses all that many environment variables. You're usually specifying build targets as the command line arguments. Automake and autogen usually generate these makefiles with everything hard-coded.

Also, it makes it very easy to get started with, and it is universally available. Makes it very easy to like.

(I know there is nothing wrong with it, but some teachers really dislike it)

Cars driving around create a lot of noise. Driving on a rough surface like concert, let alone a bumpy surface like brick or cobblestone, creates a ton of additional noise. Another hint is that gravel driveways are cheap, but they also make it very very easy to hear when someone is pulling up to your house.

Anyone living next to these roads _might_ have some cars go a bit slower, but at the cost of not being able to sleep at night.

Then there is the fact that America loves big cars with big off roading wheels. I think the assumption here is that most speeders would be discouraged by the uncomfortable ride, however I think reality is that the people in that hummer going 90mph on a city street just won't care about a rougher ride.

I didn't think plastics are used because they are considered the only submittable suitable material, but they are definitely the cheapest and easiest to use. You cannot injection mold wood to be the exact shape and size with a snug fit for something you are packaging.

The next time something tries to use whatever memory or function it overroad, it would pick up your version instead.

Today I use CLIs like usql to interact with MySQL and SQLite so I can continue to use those commands.

At first glance they may be less obvious, but they are significantly more discoverable. \? Just shows you all of them. In MySQL it always feels like I need to Google it.