mb7733

> Canada has a similar opioid epidemic but a different supply chain, largely skipping over Mexico. Because Canada saw similar falls in fentanyl strength, the researchers hypothesise that the supply shock was caused by something changing in China.

FL Studio (fka Fruity Loops) uses this layout, or something very close to it.

Yeah and (1) the codegen produces massive headers that slow compilation of anything that touches them (2) the generated classes are really awkward to use. Not a big fan of the experience of protobuffer generated code in a large C++ code base.

It's lead to a huge layer of adapters and native c++ classes equivalent to the protobuffers classes to try and mitigate these issues.

> In a real-indexed vector, that notion doesn't apply. It's "infinity plus one" all the way down: whatever real value you pick to start with, x, there's no delta small enough to add to it such that there's no number between x and x+d.

Just to clarify, uncountability isn't necessary for this. It's true for the rational numbers too, which are countable.

Standard deviation of what

> If you run a Jimmy John’s, most of your customers will pay with credit cards. Everything runs through banks. You can’t launder that easily.

You don't need to launder it, it was acquired legally

Interesting! On the guitar when alternate tunings are used, the pitches are written as they sound.

I wonder if maybe the difference is due to the fact that alternate fingerings are very common for guitar (because of having more strings spaced closer together). So notating pitches assuming a specific fingering doesn't make sense.

Plus I don't think the mapping from the staff to muscle memory for guitar is nearly as strong because we have frets.

Your calculations are off unless it's assumed each employee eats an entire pizza. Not to mention bulk discount.

I don't know but you're a little behind the times. Kids these days don't have Boomer parents.

That's not a good analogy. Mostly shows you don't understand the problem being solved.

It's not "faking" an analog system within a digital system. (If anything, that's what a full digital DJ set up is.) It's an adapter between the two.

As such a purist, would you prefer that digital music is never used? Or that digital music must only be used with digital controller? In that case DJs that use both types of music have to lug around two separate controllers.

Your use of "illusion" and "pretend" seem a bit dismissive or cynical.

It's just a vinyl interface to a digital set up. The alternative (when using digital music) is a digital controller which also tries to mimic vinyl, just more poorly.

Indexes can only help narrow down to the issues for the project (more generally: matching rows for the query). Once the index narrows down the rows, Postgres still has to count them all, and Postgres isn't particularly fast at that, especially in an active table[0]. That's what the author meant by 'complete index scan of the tasks for the project'.

Of course this isn't really relevant until there are a very large number of rows to count for a given query. Much larger than what is likely for "tasks in a project". I've run into this only with queries that end up counting 10e7/8/9 rows, i.e. more like OLAP workloads

[0] https://wiki.postgresql.org/wiki/Slow_Counting

I worked as a poll clerk in a Canadian federal election once and counted ballots and the experience left me with full confidence in the system. It would be impossible to game on a large scale and incredibly difficult on a small scale.

From what I recall, our polling station, which served only a small portion of the city, was broken into several polls, each run by 2 or 3 poll workers.

At then end of the day the poll workers personally counted the ballots they collected at their poll (so every ballot was counted at least twice, and each individual only counted a fraction of the ballots at the station.) Monitors from the different political parties were free to watch the whole process.

I'm definitely getting some details wrong, but generally the whole thing, plus automatic recounts for tight races left no doubts for me.

I used to agree with this completely, but type annotations & checking have made it much more reasonable. I still wouldn't choose it for a large project, but types have made it much, much easier to work with others' python code.

Python with strict type checking and its huge stdlib is my favourite scripting language now.

I haven't used R in forever, but is your `.` placeholder actually necessary? From my recollection of pipe operator the value being pipe piped is automatically as the first argument to the next function. That may have been a different implementation of a pipe operator though.

Static analysis could only tell you which fields are never used, across all usage of the class. Not on a given instance.

Broadly speaking electric bikes don't use regenerative braking. It's not possible with a road bike drive train.

In any case, the weight of the motor is overcome by the motor itself, using the power stored in the battery.

While I don't believe they're being used to cheat in professional cycling, a motor would _definitely_ provide a massive advantage in a cycling race of any kind.

A motor easily provides enough power to overcome its weight, and they wouldn't need assistance for the entire race, just an edge at key moments.

> I was pretty young in 2005 but $15.000 would get you a decent car (though not a pickup).

A base model Ford Ranger would have done it!

... Hence the scare quotes

> One thing I haven't seen written about much is how these APIs turned into massive liabilities for privacy. If a Twitter API allows me to siphon tweets off of Twitter, you can never delete them.

Is that really a privacy concern? Tweets are public. As soon as you post them, others can just save the page. No need for an API.

Isn't that their point though? They don't have 30 years of C/C++ experience and a workplace with very strict guidelines. They are just trying to write some code, and they run into trouble on C++'s sharper edges.

> I don't really ever find myself having to do that. I guess it's been a long time since I worked in an environment which did not use an "only merge to main after passing CI" workflow, and back then we weren't using git, anyway.

You _never_ have bugs that slip through the test suite? That is extremely impressive / borderline impossible. Even highly tested gold-standard projects like SQLite see bugs in production.

And once you find a regression that wasn't covered by your test suite, the fastest way to find where it originated is often git bisect.

Right, gotcha, I just found it confusing to say "modifying a `const` value" but if course you meant modifying the underlying value [through a cast]. All good.

Sorry, misread your post.

Part of the problem is that it trickles down and affects sport at lower levels. I was an age group swimmer (ages 10-18) when those suits came out. I can't remember exactly but it at least 10x'd the minimal equipment budget for the season. The suits were not only much more expensive but they wore out after a small number of races.

Suddenly a line was draw between have- and have-nots based on whose parents could and would buy this stuff. (My club, like many, practiced in a small municipal pool and it was very budget friendly. The fancy suits would be a large fraction of the annual cost to a family.)

In my opinion banning the suits was great for the sport at the age-group level, and thus the sport in general.

> modifying a `const` value is only undefined behaviour if the underlying object is `const`.

I found this sentence confusing. You mean that modifying a value that has been const_cast is undefined behaviour only if the original variable was const right? Or something else?

The man in question can and did stand, no 'possibly' about it.

This statement a specific case is different than the probability of it working in general.

From whom was VSCode acquired?

> If the shortest proof for some theorem is several thousand pages long and beyond the ability of any biological mind to comprehend, would mathematicians not care about it?

Care or not, what are they supposed to do with it?

Sure, they can now assume the theorem to be true, but nothing stopped them from doing that before.