I’ve had several hours to play with Inkscape 0.46 since it was released, and despite the minor version increment, a lot has changed.

New features

• A “fill” tool, making it trivial to turn bitmaps into vectors quickly
• 3d drawing shapes (including perspective)
• A tweaking tool, making it easy to nudge/blur/soften shapes
• Several new effects (including path effects)
• Many performance improvements, including huge improvements in blur speeds
• Better gradient tools
• Dockable tool windows (nicely done too)

I’m especially excited about the “fill” tool, as it simplifies tracing scanned sketches and logo bitmaps. The tool creates vectors using a flood-fill algorithm, based on the zoom level and configurable limits (fill method, threshold, gap-closing, etc.). In my tests so far, I’ve been able to turn pencil sketches into vectors quickly¹, as well as scans of real-world-objects.²

1. Normally tracing complex sketches takes me hours ↩
2. I created the fuji logo by scanning + fill-tracing an old, decaying T-Shirt logo ↩

CodingHorror has a brilliant article on the Danger of Naïveté in programming, showing how difficult it is to see poor algorithm selection on the surface. As our local guru says, “Always, always measure.”

Literate Programs, a wiki full of MIT-licensed, reviewed, and tested program and algorithm fragments.

A take on Yegge’s post that suggests that Google’s project management style is as distributed as most of their algorithm design.

Avalanche, vapour, and dirty tricks
First of all, I’d like to clarify that Avalanche is vaporware. It isn’t a product which you can use or test with, it’s a bunch of proposed algorithms. There isn’t even a fleshed out network protocol. The ‘experiments’ they’ve done are simulations. (Via BoingBoing)