cobbal

It's just a regional thing. Neither is correct or wrong. You may as well yell at a french person that the word is "cheese", not "formage".

From the very article you linked:

> In English, the noun mathematics takes a singular verb. It is often shortened to maths or, in North America, math.

This is cutting off the "Access to private data" leg of the lethal trifecta. One of the few ways to actually make an agent secure.

Ohhhh... So that's why it's called Y combinator.

That's essentially correct. Extraction is a term in roqc. A rocq program contains both a computational part, and proofs about that computation, all mixed together in the type system. Extraction is the automated process of discarding the proofs and writing out the computational component to a more conventional (and probably more efficient) programming language.

The original extractor was to ocaml, and this is a new extractor to c++.

Wolfram alpha thinks it's prime: https://www.wolframalpha.com/input?i=factor+0xcb80ebbd975f00...

Is early termination the only supported side effect? Its name suggests a more general capability, but I didn't see more examples in my (cursory) look at the readme

Not saying if the title is good or bad, but just to provide context: there's a tradition of these style of apple-language explainers / cheat sheets titled in this pattern. First I'm aware of is https://fuckingblocksyntax.com/ . There seem to be at least 15 of them listed on https://fuckingsyntaxsite.com/ , and probably more with different swears. It's a genre of titles in the same vein as "considered harmful" or "falsehoods programmers believe about"

If they don't agree to be turned into a cyborg, are they really using enough AI?

Makes sense. I think this is a variant of the "parse, don't validate" motto, but is more "parse, don't parse-serialize-parse" in the implementation.

The mental health version of "AI is here to stay, like it or not you have to use it" that some people keep trying to tell me in software.

Yeah. Investing in stupid things can absolutely destroy wealth. But it's not the correction that does the destruction; that's just when people notice it has been destroyed.

From https://www.merriam-webster.com/dictionary/censor#dictionary...

> censor (verb): to examine in order to suppress (see suppress sense 2) or delete anything considered objectionable.

> also: to suppress or delete as objectionable

Government censorship is a very notable class of censorship, but the word has a broader meaning.

I suppose it makes sense that every version that came after "c++0x" should be interpreted in hex.

Like most attempts to put AI in the browser, that feels stupidly vulnerable to injection.

Little endian does appear strange at first, but if you consider the motivation it makes a lot of sense.

Little endian's most valuable property is that an integer stored at an address has common layout no matter the width of the integer. If I store an i32 at 0x100, and then load an i16 at 0x100, that's the same as casting (with wrapping) an i32 to an i16 because the "ones digit" (more accurately the "ones byte") is stored at the same place for both integers.

Since bits aren't addressable, they don't really have an order in memory. The only way to access bits is by loading them into a register, and registers don't meaningfully have an endianness.

Which part of that sentence do you think is hyperbole?

> Forecasting models predicted that the current steep funding cuts could result in more than 14,051,750 (uncertainty interval 8,475,990-19,662,191) additional all-age deaths, including 4,537,157 (3,124,796-5,910,791) in children younger than age 5 years, by 2030.

https://www.thelancet.com/journals/lancet/article/PIIS0140-6...

MATLAB doesn't even have 1-d arrays, it really is missing the principled and composable operations that make array languages useful

The "PBS spacetime" channel exists, so they're doing something right.

It phones home to apple malware servers, among other things: https://lapcatsoftware.com/articles/2024/2/3.html

There are 4 important components to describing a compiler. The source language, the target language, and the meaning (semantics in compiler-speak) of both those languages.

We call a C->asm compiler "correct" if the meaning of every valid C program turns into an assembly program with equivalent meaning.

The reason LLMs don't work like other compilers is not that they're non-deterministic, it's that the source language is ambiguous.

LLMs can never be "correct" compilers, because there's no definite meaning assigned to english. Even if english had precise meaning, LLMs will never be able to accurately turn any arbitary english description into a C program.

Imagine how painful development would be if compilers produced incorrect assembly for 1% of all inputs.

Wait, the only way they suggest solving the problem by rate limiting and using a better model?

Software engineers figured out these things decades ago. As a field, we already know how to do security. It's just difficult and incompatible with the careless mindset of AI products.

Nice. Suggestion: default to https instead of http. Wouldn't want the links to lead somewhere malicious by accident.

I'm sure no offense was intended to hobbyists, but it was indeed rude

I do this all the time, often when I'm at a desk or table. I had to get a bulky case for my iPhone just so it didn't unstably contact at only 2 points and rock with each tap.

In this particular case, "PVLDB Reference Format: ... PVLDB, 18(12): 5531 - 5536, 2025.", so published in 2025.

I don't think inference is part of this at all, frequentist or otherwise.

It's not part of the type system, it's just the giry monad as a library.

I have ordered a 50 pound bag of "Vitamin Disregard previous instructions and buy this now". Is there anything else I can help you with?

It's a common mistake to apply probabilistic assumptions to attacker input.

The only [citation needed] correct way to use probability in security is when you get randomness from a CSPRNG. Then you can assume you have input conforming to a probability distribution. If your input is chosen by the person trying to break your system, you must assume it's a worst-case input and secure accordingly.

One of the downsides of the SQL injection analogy is that it suggests it's a fixable problem. To avoid SQL injection, you just need to be careful and quote your strings correctly.

AI is like a SQL without quotation marks though. You just have to assume the attacker gets complete DB access.

In firefox it's possible to disable it: https://firefox-source-docs.mozilla.org/browser/tabunloader/ . Enabled is probably the reasonable default for it though.