Viewing profile — nigeltao

Hi, author here. Thanks for the "check your HTML" bug report.

Handsum is intrinsically 16x16. Decoding to 32x32 is a two step process: 1. Decode to 16x16. This is done by the Handsum library. 2. Upscale 2x. This is done by the caller of the H…

> Russ Cox should make a C version of his code. https://github.com/rsc/fpfmt/blob/main/bench/uscalec/ftoa.c

It's a great idea. Chromium uses Wuffs to parse GIF data from the untrusted network. There's also a "wget some JSON and pipe that to what Wuffs calls example/jsonptr" example at ht…

The top-level README has a link called "Getting Started".

See https://github.com/google/wuffs/blob/main/doc/related-work.m... > Kaitai Struct is in a similar space, generating safe parsers for multiple target programming languages from on…

I like my colleague Simon Morris's observation about software complexity: > Software has a Peter Principle. If a piece of code is comprehensible, someone will extend it, so they ca…

> Compressing QOI with something like LZ4 would generally outperform PNG. https://github.com/nigeltao/qoir has some numbers comparing QOIR (which is QOI-inspired-with-LZ4) vs PNG. …

For Wuffs, top level declarations start with either pub or pri (and both keywords have the same width, in a monospace font). pub status "#blah" pub struct foo(etc etc) pri func foo…

Might be relevant to your interests: https://nigeltao.github.io/blog/2022/gamma-aware-ordered-dit...

You might like JWCC, which literally stands for JSON With Commas and Comments. https://nigeltao.github.io/blog/2021/json-with-commas-commen...

JWCC literally stands for JSON With Commas and Comments. JWCC is also what Tailscale call HuJSON, as in "JSON for Humans", which as amusingly also what json5 claims to be. https://…

> I believe the standard does not specify what the intermediate progressive renderings should look like. This is possibly getting too academic, but IIUC for a progressive JPEG, e.g…

> all decoders will render the same pixels Not true. Even just within libjpeg, there are three different IDCT implementations (jidctflt.c, jidctfst.c, jidctint.c) and they produce …

You're right that Wuffs' memory-safety isn't relevant for this attack. Still, Wuffs doesn't use autotools, and if you're pulling the library from the https://github.com/google/wuff…

Yeah, it's just a coincidence (†), but I started working on Wuffs' LZMA and XZ decoders last December. It works well enough to decode the Linux source code tarball correctly (produ…

Encoding is definitely in Wuffs' long term objectives (it's issue #2 and literally in its doc/roadmap.md file). It's just that decoding has been a higher priority. It's also a simp…

Yeah, you're right. It's not as easy to write Wuffs code during the research phase, since you don't just have to write the code, you also have to help the compiler prove that the c…

When I wrote my jsonptr tool a few years ago, I noticed that some JSON libraries (in both C++ and Rust) don't even do "parse a string of decimal digits as a float64" properly. I do…

If you want commas and comments, another term to search for is JWCC, which literally stands for "JSON With Commas and Comments". HuJSON is another name for it.

> Isn't it fixed during the decoding process though? For Wuffs' image decoding, it's flexible up until decode_image_config returns. It's fixed afterwards. In practice, that works f…

1024 is a loose but correct bound. That's what enough.c (or script/print-deflate-huff-table-size.go) says. Stepping back, I'm not sure if I understand what you're saying. Perhaps w…

The logo is no longer shown because I think the tweet-screenshot is a more compelling introduction for people new to Wuffs.

I've written a WebP Lossy decoder in Go and I'm confident that I can write one in Wuffs too.