How I got involved in the Rust community

Re:How I got involved in the Rust community by cogman10 on Friday December 09, 2022 @04:01PM (#33926419)

Don't forget startup and distribution time. It's not terribly hard to have a scratch rust container which is about as slim and secure as you can get. That container will startup pretty much instantaneously even if it's cold.

You are looking at ~5mb container vs 200+mb if you did a jvm based container.

It's probably overkill for most applications and companies, but it's something to keep in mind if you need fast scaling for cheap.

[ Parent | on HN ]

Re:How I got involved in the Rust community by makapuf on Friday December 09, 2022 @04:22PM (#33926593)

For webdev Go scratch containers are really nice and quick to develop. Of course the language could use better error checking but that's about it. It really does that job well. Fast, secure (GC and yes you can ignore errors the same way you can unwrap() the world).

[ Parent | on HN ]

Re:How I got involved in the Rust community by brabel on Friday December 09, 2022 @04:58PM (#33926898)

Rust will be much lighter than any JVM app, but a fairly complex JVM app can be compiled to a self-contained JVM distribution on around 25MB these days... you use jlink to compile the app and parts of the JVM that you actually use.

Not to mention you can use GraalVM native-image to compile to a binary directly, in which case it'll be even smaller.

[ Parent | on HN ]

Re:How I got involved in the Rust community by zozbot234 on Friday December 09, 2022 @05:10PM (#33927052)

Startup time is a great feature for all sorts of FaaS environments as well. Especially when combined with Rust's generally low resource use.

[ Parent | on HN ]

Re:How I got involved in the Rust community by alephu5 on Saturday December 10, 2022 @02:10AM (#33930661)

Go has these same properties

[ Parent | on HN ]