gugagore

In case your point is that using "less" instead of "fewer" for countable nouns is an example of unclear communication, let me disagree with the point.

Julia is unique in using multiple dispatch pervasively. It did not invent multiple dispatch, but it certainly popularized it.

They use both.

http://people.csail.mit.edu/mrub/VisualMic/ uses the rolling shutter to get audio from regular-framerate video of a bag of chips.

You did not have to do it every single time. There are many changes you can make that are handled correctly by Revise.jl

The factory pattern in Java exists because a type / a class is not a "first-class" concept. You can't pass around a class so that it gets constructed at some other point. Python (which I believe inherits from Smalltalk) has a different object system, which makes the factory pattern irrelevant.

I believe this is where the "Ambiguity Function" comes in. For a given waveform, it tells you the ambiguity between Doppler shift and time delay.

I think you underestimate the scale of data these models are trained on by many orders of magnitude.

There is no good syntax to specify what part of an arbitrary image should be highlighted.

I agree. Graphical animations (even to highlight text, tables, figures) is such an essential part of communicating in a slide show, and I have not found a tool that achieves both separation of content and style while allowing convenient design of these graphical elements.

IIRC, forward error: the error between the given answer and the right answer to the given question.

Backward error: the error between the given question, and the question whose right answer is the given answer.

Easier to parse like this: a small forward error means that you give an answer close to the right one.

A small backward error means that the answer you give is the right answer for a nearby question.

If x is the interval [-1, 1], the typical implementation of IA will

evaluate x-x to [-2, 2] (instead of [0, 0], and

evaluate x*x [-1, 1] instead of [0, 1].

Therefore the intervals become too conservative to be useful.

I really wish the Spintronics chain was compatible with Lego Technic chain and gears.

> For a twice larger "spin resistor", then, the equilibrium torque would be twice as large, and intuitively, the chain speed would be half as fast.

For the twice-larger resistor, the torque is the same, and the speed is half as fast. Can you explain why you think the torque is twice as large?

To move the 2x resistor at the same speed as the 1x resistor, you need twice the torque.

The only reason, in my eyes, to use CSV is to have easy interoperability with spreadsheet software.

If you want streaming: https://jsonlines.org/

Yes that is what I meant, thanks!

No, it can't be. This function has compact support, the Gaussian clearly does not.

You get a Gaussian by repeated convolution of the same function (and normalizing the width).

The equivalent question to what I asked is what's the pdf of X1 + X2/2 + X3/4 + ...

where Xi is iid unit uniform.

I'd like to know what function this converges to:

rect(x) • rect(x/2) • rect(x/4) • ...

Where • is the convolution operator.

Unlike the series in the video, 1 + 1/2 + 1/4 + ... converges. So this function has compact support, and the value at 0 does not dip.

I expect it to be a https://en.m.wikipedia.org/wiki/Bump_function

What important property of DFS is missing if you just replace a stack with a queue?

What I don't understand is how much technique assumes of the local oscillators on the recording device, which also vary.

I don't see how radians come into the discussion of torque and energy, both of which are N*m in SI.

That discussion has to do with the failure of SI to notate the directions of vectors. When it's torque, the N and the m are at a right angle. When it's work, they are both in the same direction.

Because I didn't see it mentioned yet, this is the same feature that makes the small-angle approximation of sin elegant: sin(x) ≈ x .

"to" is often reduced to something like "tuh", whereas "two" never is.

Except in deliberate word-by-word pronunciation, "one two three" and "one to three" sound different in native US English.

Here is an example: https://wesmckinney.com/blog/avoid-unsigned-integers/

Everyone should have fun all the time is not really a realistic goal, period. I don't think playing games is universally fun either. Games can be quite boring.

Games do often promote the concept of winning and losing, however.

GCC is less opaque (less of a black box) than these language models.

If I remember correctly, pressing the turbo button actually slowed down the CPU clock.

There's nothing more silent about it than any other bug that arises in a similarly dynamic language. People use Python over C++ in large part because it saves X amount of coding hours, and comes with different kinds of bugs that can "silently return wrong results".

Yes, those fixes don't inherently require the Julia language to change at all.