It must be able to cache it's all content in browser.

I guess to do it it properly you need to make it PWA.

You can also just use proper HTTP cache headers. ETag and a very long Expires header.

Idea is to keep it light and accessible. PWA would be data heavy. The use case is in the article linked in the post description.

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.

Maybe, but it is much simpler, probably faster, starts instantly and do not eats tons of RAM.

I just thought that MIT for subset of users is better than "My Own License"

Well plain text README is booooooring. And I just realized that adding emoji could help to make it more fun and emphasize some context.

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 :)

It is simple. If you do not like it - do not use it. I do not care. Have no plans to conquer the world with this project :)

I mean you must care a little bit right? Why publish it and share it here otherwise? :) Maybe you're looking for people to just review and learn from the code, rather than use it in their projects?

From license terms you can see that any independent developer and small teams could use it without any issues.

And yes I do not want it to be "free stuff" for big corporations. I just do not know any existing license that can define such terms.

> From license terms you can see that any independent developer and small teams could use it without any issues

Right, until they cannot, and that choice won't be made from their own agency, and most people will try to avoid ending up there, hence not using the project in the first place.

Not saying "it's doomed to have zero users", but you'll probably find it slightly strange when people seemingly would have perfect use for your project, yet find other options anyways.

> And yes I do not want it to be "free stuff" for big corporations. I just do not know any existing license that can define such terms.

Guess BSL would fit you, but yeah, if you want any sort of restrictions, what you want is something else than Free and Open Source Software, and that's fine of course, just be aware it'll be a hard sell to developers used to FOSS. Again, a fine choice to be making and understandable.

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.