I think if you know Rust then I think Rust + async is going to perform better and consume less resources than NodeJS by a LOT. It should also work more reliably on embedded devices, or even docker containers because memory isn’t going up and down like a yoyo because of GC.

That said NodeJS is more immediate and might lend itself to better prototyping / RAD and you might not care enough about performance to justify using a compiled language. A lot of web servers aren’t doing enough that you would even notice a difference in performance.

Another reason for Rust might also be because it’s more energy efficient. I wish Amazon and other cloud services would put a heavier cost penalty on efficiency. I wonder how many cloud web apps are running bloated stacks to serve up content which could be done with a fraction of the energy.

Use Mastadon or some other social media platform. Not always a choice and if you’re stuck with Twitter you might as well ensure you’re not enriching the platform.

My solution works fine on Android

1. Delete the Twitter app.
2. Open the site in Firefox Mobile
3. Open the Firefox menu and choose Install
4. Install uBlock Origin into Firefox

Now you have a launcher icon for Twitter that opens in Firefox and has all the ads stripped out. I believe there is even a “Twitter Control Panel” add on that will remove a lot of the remaining clickbait from the page too - what’s trending etc.

I do front and backend work. Biggest issue I see is people not thinking through interfaces properly (e.g. efficiencies & atomicity of operations), sanitizing inputs on both sides, error handling, and putting in the appropriate validation, authorization & testing.