govips VS Primitive Pictures

We chose to use govips which is a cgo wrapper around the libvips image manipulation library. The majority of new development for services in our backend is written using baseplate.go. But Go is not an ideal choice for media processing as it cannot keep up with the performance of native code. The most widely used image-processing libraries like libmagick are primarily written in C or C++. Speed was a major factor in selecting libvips in order to keep latency low on CDN cache misses for images. In our tests, libvips was 3–4 times faster than libmagick on basic image processing operations. Content-aware smart cropping was implemented by porting smartcrop.js to Go. This is the only operation implemented in pure Go.

Hi! You are willing to dive into some cgo we have a couple of feature requests :) https://github.com/davidbyttow/govips

TIL about https://github.com/fogleman/primitive from https://en.m.wikipedia.org/wiki/Comparison_of_raster-to-vect...

Looks great! I've been thinking of having my own attempt at something like this ever since I saw a similar idea at primitive.lol

Looks like it's made with https://github.com/fogleman/primitive

If you're looking for a more artistic arrangement of coloured blocks, and you've got some skills (or a Mac), there is this one application that's fun to play with. But I'm sure there are other ways.

Some examples off the top of my head (not game-dev specific) are https://www.michaelfogleman.com/ (creator of https://primitive.lol/), Marco Arment (https://marco.org/ - Overcast), or Pieter Levels (sadly as I write this I found that his blog seems to have been taken down and just redirects to his twitter https://twitter.com/levelsio?ref=levels.io - but still has a laundry list of projects old and new in his twitter bio)

Any ideas on how I could simply cross-compile a non-module GitHub repository to three different architectures with predictable filenames? I wouldn't mind setting up a go.mod file, the problem is I would like to compile the executable in the github.com/fogleman/primitive repository, not my own code.

Consider an SVG from [Primitive](https://github.com/fogleman/primitive) and a mostly-transparent overlay containing the diff against the original image. Tuning Primitive is not entirely deterministic (like your algorithm) and I think a human interface for the front-end would allow a few knobs to erase parts of the diff in order to shrink the detail imperceptively. Seems like a good opportunity for a contest :)

I think stroke-based painting methods like these are neat: https://github.com/jiupinjia/stylized-neural-painting https://github.com/fogleman/primitive