Anton Bachin

I think all of this should be done in separate libraries, with a few examples here in the Dream repo, as you suggest. Some of what's in the roadmap isn't...

@jsthomas, thanks for the excellent blog post. I learned a lot from it. It's a great digest of the state of the ecosystem, various alternatives, external services, and a neat...

As for the email-sending system, it looks like a pretty straightforward design internally. Each setup needs... 1. A queue. We need to exercise several options to make sure the framework...

So I think for an initial version, we can have some "core" `dream-mail` library that has a queue interface (signature) and a sender interface (signature), but does not implement them....

Also, I think that setup is not Dream-specific, so you don't need the `dream-` prefix, and feel free to come up with some creative name for this :)

(Although, if we build a Dream-friendly HTTP client library and you choose to use that for accessing APIs, the library will become vaguely Dream-related again, but by that point the...

> To be fair, I think it's also okay to have an email interface/signature, and having various library implement that signature, similar to other frameworks such as Django. That's basically...

@jsthomas, I just tried the library and was able to land an email (into my spam folder, of course) using its Mailgun example! Thanks! The library is definitely useful for...

Thanks! Posting the results link from Discord: https://web-frameworks-benchmark.netlify.app/result

As suggested by @ulrikstrid, there are also the TechEmpower benchmarks: - https://github.com/TechEmpower/FrameworkBenchmarks - https://www.techempower.com/benchmarks/