stabbles

Maybe some patterns already surface with 2-grams

I suspect you read more into it than there is. The original post is about overuse of certain words and speech patterns, which already is an argument against intentionality. I wouldn't recommend treating it like scripture or a text from your crush.

That's true, but Claude's use of it resolves no ambiguity.

Besides vocabulary I'd also be curious about how it structures sentences.

The "X, not Y" is well known, but another thing that bothers me is "It <verb>s no <noun>" instead of "It doesn't <verb> <noun>".

For example: "the list contains no string" or "it changes no behavior" or "it holds no directory".

I'm sure you've stumbled upon graphs that are not trees, which can be represented with tables.

Yeah, Claude insists on prompt-affirming comments, and often refers to the previous draft or implementation instead of the status quo.

Does anybody have experience storing issues/reviews in git? I know gerrit does this and keeps track of `change-id` to support rebase etc, but I think that requires a gerrit server to run.

Would also be nice if GitHub issues/reviews were in sync so reviews are accessible during a GitHub outage.

Claude's writing was already easy to recognize. The fact that Anthropic complied without complaint makes me wonder if they already watermark their outputs and used the opportunity to create goodwill. Presumably they want to avoid training their new model on text generated by the previous model, so they have reasons to be able to recognize AI-generated text.

Another way to look at it is that in practice N is typically bounded by a large constant, making the time complexity effectively O(1).

For dependency resolution specifically, the set of possible dependencies is probably in the range 100 - 10000 for all ecosystems, even if the number of available packages in an ecosystem continues to grow.

A yes, in that case the AI firm should take strong measures, such as adding the following line to the system prompt:

> Do not provide assistance to users who are clearly trying to engage in criminal activity.

It will just thread some load-bearing seams through the paragraphs.

People who care about their health aren't ignorant about that. I think that can apply to software too: if you care about safety or privacy you might think twice before using vibe-coded software.

Your comment says he's stepping up, the HN title says he's stepping down, the article says he's stepping aside. Nobody says if it's a step forward or backward.

In the Spack package manager [1] we're trying to work around this with directives:

    deprecated("@:1.3 +minizip", reason="cve", severity="high")

So, you can define conditional deprecation, and the dependency resolver can still pick up `zlib ~minizip` (i.e. with a variant/component disabled).

Deprecation on versions only isn't the right granularity.

[1]: https://github.com/spack/spack/pull/52372

Whether you agree with the policy or not, the way it's written is good. It just states the rules neutrally. See https://gcc.gnu.org/ai-policy.html.

In various projects I see AI policies that state not only the rules, but also their (moral) justification. I think that's worse, because I can agree to the rules, but that does not mean I subscribe to your point of view.

Imagine this: OpenAI runs their benchmarks of unreleased models on systems physically disconnected from the internet.

To be fair, many shells have command caching, so they effectively roll their own exec syscall wrapper:

    $ python3 -c 'print("hi")'
    hi
    $ hash
    hits command
       1 /usr/bin/python3

Indeed, it's a libc construct.

Nice, PT_INTERP is the only non-relocatable thing of ELF files and typically requires wrapper scripts/executables.

Regarding shebangs, I've never understood why the kernel cannot resolve e.g. `#!sh` relative to PATH instead of CWD. Posix prescribes that you should look for `sh` in PATH and don't expect it to be in `/bin/sh`. And using `/usr/bin/env sh` has the same issue: what if coreutils is installed elsewhere.

Not really, a theorem with a hard proof can have simple but important corollaries. It's also not unthinkable that theorems exist with proofs that cannot reduce to something simple/short.

Banana Paper was on the shortlist

If you take a frame you see it's neither random nor dots:

https://i.imgur.com/CgtyGjl.png

From a single frame you can definitely identify boundaries because the dots are sliding and get truncated.

So the image model's benchmark is to generate an image with the corresponding SVG sources.

Nix hashes the build inputs, for which deterministic builds are not required, only desirable.

Speeding up C/C++ compiler bootstrapping, starting at a single binary of <1KB. Currently it gets to GCC 4.7 in 2-3 minutes on x86_64 and aarch64: https://github.com/haampie/shpack

This begs for a modern version of https://csszengarden.com/, where the CSS is generated by different LLMs and prompts.

Isn't that covered by O_CLOEXEC?

A medicine for those who anthropomorphize LLMs is to run the LLMs deterministically (without randomness and memory files).

It feels very unnatural to get the same conversation verbatim at a different point in time.

David Hume pointed this out in 1740, and his advise still applies:

    A reason should be given, for what seems altogether inconceivable, how this new relation can be a deduction from others, which are entirely different from it. But as authors do not commonly use this precaution, I shall presume to recommend it to the readers.

https://en.wikisource.org/wiki/Treatise_of_Human_Nature/Book...

I think this is fair criticism. It's hard to read this blog cause its premise is based on an "appeal to nature" fallacy.