baseplate.go VS markup.rs

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.

Even Reddit has python backends https://github.com/reddit/baseplate.py based on Pyramid. They also have a go one. https://github.com/reddit/baseplate.go

there's a multitude of services in reddit's architecture. as far as i can tell, they mostly using reddit's baseplate framework (which has implementations in both python and go).

FWIW, I believe Reddit has rewritten some Python into Go because of scaling issues. I don't know of any public write ups to confirm it, but at the least there's a public repo that contains their base template.

Gazette Inference Service is a baseplate.go (Reddit’s golang web services framework) thrift service whose single responsibility is serving ML inference requests to it’s clients. It is deployed with Reddit’s modern kubernetes infrastructure.

Baseplate is implemented in Python and Go, and although they share the same main functionality, smaller features differ between the two. One such feature that was previously on the Go implementation but not Python was deadline budget propagation, which passes on the remaining timeout available from the initial client request all the way through the server and any other requests that may follow. The lack of this feature in Baseplate.py meant that many resources were being wasted by servers doing unnecessary work, despite clients no longer awaiting their response due to timeout.

(Sailfish is fastest, but it's syntax is of the more traditional <%= msg %> flavour and Markup.rs is second-fastest with a Maud-like syntax but the author apparently doesn't have time to rewrite the syntax reference, so you have to follow a link from the open issue to an old version of the README.)

Maud or markup.rs for templating (I use the latter, and it is faster, but they're both fast and markup.rs is currently missing its full syntax documentation unless you dig through the revision history for the stale version. I'd recommend the former for you.)

For the sake of thoroughness, I should point out that Haml-like templating engines like Maud and markup.rs are even more concise.

https://maud.lambda.xyz/ or https://github.com/utkarshkukreti/markup.rs for server-side HTML templates that compile to Rust code

(eg. In Python, Genshi templates are too slow for me to feel comfortable using them, but they were the main way to get robust correctness checks for templates last time I evaluated my options. In Rust, Markup.rs or Maud are the second and third fastest templating solutions, as I remember, and they give even more well-formedness guarantees for HTML than Genshi.)

There are various templating solutions that use syntax derived from the host language, like Maud or markup.rs for Rust, the E factory API for lxml for Python, etc.

You can have similar features to Phoenix Live View by using Turbo from Hotwire with your favorite template engine in Rust. Contrary to what the video presentation on the Hotwire main page leaves you to believe, Hotwire works with any template engine from any language, not just Rails. Markup.rs and Turbo from Hotwire should compose quite nicely.