jelly-actix-web-starter VS web3.js

You can look at https://github.com/secretkeysio/jelly-actix-web-starter

My usual reminder that I have a Django-ish template for actix-web that I maintain: https://github.com/secretkeysio/jelly-actix-web-starter

Now that actix-web 4.0 is out I should be able to finally resolve one of the open issues/PRs, which I was waiting on 4.0 for.

For those interested in Django-in-Rust type approaches, I maintain an actix-web starter project that does exactly this: https://github.com/secretkeysio/jelly-actix-web-starter

I maintain a starter for all of this kind of stuff on top of actix-web, for anyone interested: https://github.com/secretkeysio/jelly-actix-web-starter/

Curious why you went with the mailbox approach - since a request is pretty much in-and-out, I found it sufficient to just write a trait for HttpRequest and have a custom render(...) method that pulls any flash messages from the session, thus clearing them. Wouldn't surprise me if I'm missing something tho.

I love Askama, but being tied to compile time changes is an absurd handicap on a web framework in the initial iteration phase. With Tera, you can implement a watcher for template changes and reload them without needing to recompile the entire framework.

If you want, I have an open source actix-web repo that does stuff like this for you already.

If you enjoy Python's web story but want something similar-ish in Rust, you can check out my actix boilerplate repo - it "mimics" Django in many ways. If nothing else, might be useful for picking apart.

Web3.js (16500 GitHub Stars) https://github.com/web3/web3.js/

- https://github.com/web3/web3.js - Web3 JavaScript

last I checked web3.js only supports EVM coins / tokens. Was there an announcement I missed?

I have attempted to increase the maxReceivedFrameSize in my truffle-config, which is a solution offered here like so:

Here is a way to do this using web3.js.

Since we will build a Web3 example, the web3 framework was installed using npm (other options can be found here):

yeah, I could see that.

web3.js is a super bloated library and will be added more frequently unless a team does a more optimal version from scratch

https://github.com/ChainSafe/web3.js/issues/1178