bitmap

They're stay red for bitmap fonts even with AA toggled on to signal that they cannot be anti-aliased.

There was a brief era when the Mac came out in 1984 when bitmap fonts were the thing.

For example, ProFont is my favorite bitmap programming font and the renderer used makes it look bad.

What about drawing in bitmap with low latency and building the vector drawing from buffered user input in the background?

The licence of the jpeg encoder doesn't affect the licence of your bitmap generating code.

There was an effort to build bitmap indexes for Postgres a few years ago.

They really want a non-AA display, and Terminus being bitmap forces the issue.

It keeps a bitmap of modified memory pages with ephemeral objects in RAM.

It was a shareware font that was the best ImageWriter bitmap font ever.

If a parity error occurs, set the corresponding bit on in the bitmap.

I've always felt like Bitmap Indexes were a killer feature, and never understood why they weren't used more in databases.

Now here's a crazy idea: Stenography via rearranging executable code within a binary file so that the binary file looks most like a particular bitmap.

The idea is to have "library of various gradient shapes" to pick from, not full 8x8 DCT matrix capable of reconstituting 8x8 bitmap approximations.

You "run the program" when exporting to a bitmap format.

That is, given the "bitmap data" the eyes take in, the brain attempts to "parse" the scene, and adjusts colors for light sources.

The idea of two-layer index actually reminds me of the very similar compression technique adapted by Roaring Bitmap.