anvilistas / anvil-labs

MIT License
9 stars 3 forks source link

Promote, Archive or WIP #129

Open meatballs opened 1 year ago

meatballs commented 1 year ago

This project should only include work which we are currently investigating. For each of the modules, we need to decide whether it's:

s-cork commented 1 year ago

my opinions:

But I don't really have production apps - so I can't say that they're production ready or not Or how useful they are to others

meatballs commented 1 year ago

Lgtm

s-cork commented 1 year ago

any thoughts @hugetim , @jshaffstall ?

jshaffstall commented 1 year ago

Non-blocking is definitely something I'd love to use in production. I haven't played with it as it currently exists, though, so can't say whether it's ready. But I do have specific situations in my production app where it'd be useful, though not critical.

Kompot has the the multi-server call wrapping. I can't say I'd ever use the serialization features of it, but the server call wrapping would be a useful utility. It allows one to design server functions based on each having a single responsibility, but still execute a bunch in a single server interaction, which I think is very important for writing well designed apps.

I love the idea of Atomic, so definitely want to see it continue. It's such a change in structure for apps, though, that I haven't played with it.

hugetim commented 1 year ago

I'm a big fan of Kompot, at least in theory. I haven't used it yet but expect that I would use all aspects of it as part of anvil_extras.

meatballs commented 1 year ago

So, promote non-blocking and leave atomic, kompot and web worker here as WIP?

jshaffstall commented 1 year ago

Sounds good to me.

Might be worth pulling the server call batching out of Kompot and into a feature of its own.