Talinx

I don't get why we talk about using complex numbers when doing quantum physics. What's really important is that we use numbers from an algebraically closed field (complex numbers being just a simple example). This makes it clearer what's happening under the hood.

In the broadest sense Android and IOS are similar to browsers: All are platforms that execute code given in a certain format and have APIs for interacting with the device.

(The browser is different in that it doesn't need a separate download to acquire the code and makes partial code downloads easy. And from search to opening an app is a single click and very quick.)

I have never been given a probiotic while getting an antibiotic.

Seems like a good idea. Is that a common thing? Does the evidence support this?

Quantum computers deserve to be mentioned in discussions about analog computers. Under the assumption that nature is quantum at its core it follows that every analog computer could instead by replaced by a quantum computer running a suitable algorithm.

This connection opens doors for research in both directions, how to design quantum algorithms and how to built physical computing systems that make use of quantum mechanics.

Why not load the minimal required content for it to look right first (e. g. thumbnail, video controls) and load everything else once the rest of the page has been loaded (e. g. buffer the first few seconds of the video), somewhat similar to hydration?

That is a lot of text for not determining why the new solution is faster. The only relevant part:

> Before our migration, the old pipeline utilized a C library accessed through a Python service, which buffered and bundled data. This was really the critical aspect that was causing our latency.

How much speed up would there have been if they moved to a Rust wrapper around the same C library?

Using something other than Python is almost always going to be faster. This Reddit post does not give any insights into which aspects of Python lead to small/large performance hits. They show that it was the right solution for them with ample documentation which is great, but they don't provide any generalizable information.

I agree - I think it is pretty clear that there is a difference between programming languages and other languages. Figuring out the differences (instead of getting wrong ideas because they share some similarities) should lead to better words for different kinds of languages.

Maybe "Spoken languages" is a better term for languages like English? I find speaking computer code out loud just doesn't work except for some particular lines of code. "At dataclass class QueueItem magnitude colon int equals one..." is really not clear, if I have to communicate such code in words I wouldn't read it directly and instead describe it, e. g. "QueueItem is a dataclass with the attributes...").

The Minisforum V3 is a tablet that can also be used as a monitor via USB-C, so definitely possible. I wish more tablets would work that way.

Maybe stimming helps people with PTSD, too. Has anybody tried that?

Functions make assumptions all the time and there is often no way to specify them except with type information. E. g. one can specify that a function takes a float as input but not that the float has to be in [0.0, 1.0]. Hard to catch with static code analysis.

Idea for implicit parameters:

Implicit parameters are values from somewhere up the call stack. So make an object with a get function:

    Scope.get('Logger')

But then you can get anything. So add a mechanism to put things in there up the call stack:

    logger = Logger()
    Scope.put('Logger', logger)

That's a key-value store with scope levels.