Discussing why @rustlang's tiny memory footprint (compared to Node, PHP, Python) is important when developing web services. Cloud CPUs are more expensive than memory. If you've run out of Memory and your CPU is underutilised, you're wasting money.
-
Show this thread
-
Note: You're going to be using less CPU with Rust than Node, PHP, Python too so even in the cases where CPU time is more important than memory (eg, burst instances) you're still quids in.
2 replies 0 retweets 6 likesShow this thread -
Additional Note: Humans are significanlty more expensive than CPUs. Don't force them to use languages they don't want to use.
Node, PHP, Python are all fine, this wasn't a slight against them, just a point of encouragement for anyone thinking of picking @rustlang up.2 replies 11 retweets 60 likesShow this thread -
This Tweet is unavailable.
-
Not sure I would agree. I think there are some small things that cause more confussion than they should (we say "references" which badly explains the borrowing behaviour, what a string slice / array slice actually is). If you've a good teacher on hand that can be smoothed out.
1 reply 0 retweets 0 likes -
I'm also explicitly not saying "drop everything, use Rust instead". I'm just saying I noticed this benefit.
1 reply 0 retweets 0 likes -
This Tweet is unavailable.
Education is not a long term cost. If you think rust is a less productive language to use, that's another discussion -- but saying it has a steep learning curve (which should be fixed!) has very little to do with Dev cost vs cpu cost
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.