12 comments

[ 5.0 ms ] story [ 32.3 ms ] thread
Feels like a Wiremock for Rust.
Maybe, but it is much simpler, probably faster, starts instantly and do not eats tons of RAM.
The licence terms / variation on MIT is interesting - unless this file is part of some standard I'm unaware of I'd expect it still shows as plain MIT for most automated SBOM collection/licence checks which feels problematic.

(https://github.com/rustrum/apate/blob/main/LICENSE-TERMS)

Well the point here is that if I created it by myself I can make whatever license I want. But I do not want to write my own license. AFAIK even if you grant something for subset of users for "free" you have to define legally terms of this "free" usage.
(comment deleted)
We use httpmock [1] for lychee, and it works quite well. Haven't looked too closely at the differences yet.

[1] https://docs.rs/httpmock/latest/httpmock/

As I see httpmock is meant only for rust unit tests. In my case unit test library is a side effect. Apate main goal is to be a stand alone server. For example you are building web app that interacts with backend which is not ready yet. So you can simulate some API from this backend locally.
Why are people using rust to build web apps
First of all, this is not a web app.

Second, what should I use if I want a small binary with no dependencies and low CPU/RAM usage?

I could’ve used Go, but once you know Rust Go’s existence almost stops making sense :)

This English as second language README being not written by LLM -- despite the emojis which the LLMs had to learn from somewhere -- is refreshing.
Well plain text README is booooooring. And I just realized that adding emoji could help to make it more fun and emphasize some context.