Frame.io vs Pinta

Pinta runs two tracks at once. One is a steady stream of 3.0.x and 3.1.x patches fixing icons that stop rendering, crashes, and packaging problems — most of them traceable to the GTK4 and libadwaita port and to GNOME versions moving underneath it. The other is genuine feature work: 3.1 brought an axonometric grid, a polygon selection mode for the Lasso tool, gradient handles, a layer context menu, a Cells effect and a Windows ARM64 installer, on top of a rewritten canvas widget.

The pattern is a small team absorbing the cost of a large architectural move. Every few months a GTK or GNOME release breaks icon loading or a pixbuf path, and Pinta ships a patch; meanwhile the feature list keeps growing at a rate that suggests the port has stopped consuming all the oxygen. The dependency floor rising to GTK 4.18 and libadwaita 1.7 in 3.1 shows the project has chosen to track the toolkit closely rather than pin behind it, which is why the breakage keeps arriving and also why it keeps getting fixed quickly.

Expect the alternating rhythm to continue — a feature-carrying minor release followed by patches cleaning up toolkit and packaging fallout — with the next round of breakage most likely arriving with the following GNOME cycle.