akx

https://github.com/pi0/clippyjs exists...

I've used https://www.mp3tag.de/en/ for this since, apparently (per my emails for donating to the project), 2008.

Not quite, AFAIK? Drive controllers may internally remap blocks to physical disk blocks (e.g. when a bad sector is detected; see the SMART attribute Reallocated Sector Count).

The blur here isn't expensive (as discussed in the article itself).

Chances are sampling a 2D height field and projecting, etc. would be more expensive.

You can of course absolutely use `"numpy~=1.12"` as a requirement.

> Using pip-installed libraries brings in the famous packaging problems, but you don't have to use it!

These days, with uv and PEP 723 inline script metadata, that's not an issue either.

    # /// script
    # dependencies = ["numpy"]
    # requires-python = ">=3.12"
    # ///
    import numpy as np

and

    uv run myscript.py

will just Do The Right Thing.

... derp, yes. It was way too early in the morning, and I misread "is part of the benchmark" as "is not part of the benchmark"...

I would imagine browsers optimize the iterator protocol away for arrays. At least on https://jsben.ch/iJFZ4 for..of is a smidge faster than an old-school loop.

The stack overflow is caused by an `arr=[...]; events.push(...arr)` in `add_events`. Replacing that with `for(const x of [...]) events.push(x)` gets rid of that issue, and the JS-backed build is then snappier to search & filter than the WASM/Rust version.

Yes. On that version, Chrome 134.0.6998.89's devtools on my Macbook (M2 Max) are indicating 100 to 250 millisecond interaction times and a 160 ms frame when entering text into the search field.

Can you point out the nonlinear/non-live features? https://mixxx.org/features/ doesn't do a good job of that.

Yes. The interesting legal question is that are you sharing the original knowledge if you've transformed it via teaching it to an AI.

https://www.reuters.com/legal/litigation/ai-companies-lose-b... reports on the ongoing case on the image generation side of the fence.

To quote the Rust book (https://doc.rust-lang.org/book/ch20-01-unsafe-rust.html):

  In addition, unsafe does not mean the code inside the
  block is necessarily dangerous or that it will definitely
  have memory safety problems: the intent is that as the
  programmer, you’ll ensure the code inside an unsafe block
  will access memory in a valid way.

Since you say you already know that much Rust, you can be that programmer!

The researcher-or-tinkerer who wants to play with these commands can just not upgrade to the newer ESP-IDF. Or update to a newer ESP-IDF, and revert the patch. It's open source. https://github.com/espressif/esp-idf

You left out the important part of that sentence.

> Espressif will provide a fix that removes access to these HCI debug commands through a software patch for currently supported ESP-IDF versions

ESP-IDF is the "SDK" for these chips – I read that as "you'll get a new function that you call to disable these commands until you reset the chip, to limit attack surface for the rest of your app".

They can be useful. I just recently used Claude to make a query 10x faster, though I did have to back-and-forth a bit, so you do still need to know what you're doing.

Heh, the more you know! OpenDAW didn't make that obvious.

We've had https://www.audiotool.com/ for 15 years...

That's my issue! <3

EDIT: It's gotten even worse in the last 6 years!

Breakable by `clickLoop = null`.

... and inevitably, a virtual machine

Neat!

Couple of observations:

- https://zetaoffice.net/demos/simple-examples/rainbow_writer.... hangs with an `unreachable` in the console if I try Tools -> Options.

- Things don't seem to be hiDPI aware, so everything looks a bit unfortunate on e.g. my MacBook's retina screen.

https://duckdb.org/ begs to differ.

No filesystem is great in the lots-of-small-files case, partly simply due to syscall overhead.

There's a reason https://www.sqlite.org/fasterthanfs.html , SquashFS, etc. are a thing, or why even Europe's fastestest supercomputer's admins admonish against lots of small files. https://docs.lumi-supercomputer.eu/storage/#about-the-number...

> now I'm trying to wrap my head around the fact that there's such a thing as "Docker Hub" in the first place

Unless you build all of your images `FROM scratch` by default (or use in-house registries or quay or whatnot for all of your base images), you've used Docker Hub too...

Mostly figuring out the details of the old formats enough to be able to render them without having an actual Windows rasterizer... https://github.com/akx/winfont/tree/dev is half of it, the web `<canvas>` frontend is currently still private :)

I do hope they don't use brined white cheese as a symbol.

Sure, but I refuse to call this a faithful recreation of the aesthetic until the fonts look correct. :D

On a related note, I did start working on some tools to work with legacy .FONs for this exact purpose earlier this year, but the project is iceboxed for now...

By eye alone, I'm pretty sure that is not MS Sans Serif as rendered in Windows 95 and Windows 98.

So it would seem. Thanks for digging those up.

With vector fonts containing copyrightable code, are you referring to e.g. TrueType hinting, or OpenType shaping (or very avant-gardely, WASM shaping)? I should hope the glyph-drawing instructions don't fall under this definition of code, because that'd maybe mean SVG `path`s are copyrightable...