Live data from Hacker News

Why AWS loves Rust, and how we’d like to help

aws.amazon.com

261–270 of 338 posts

Re: Why AWS loves Rust, and how we’d like to help

#261

Earlier quoted context omitted.

> Instant boot time. Because rust is statically compiled, there's no runtime startup or anything involved with it. From dead to alive is pretty much instant. Dynamic linkage is not the slow part of application startup. The slow part (for applications which are slow) is almost always the gathering of non-compiled assets from disk. IMO, the lack of dynamic linkage is Rust's #2 weak point, second only to slow build time…

You can use dynamic linking with Rust. You just have to stick to the C ABI when interfacing w/ shared objects, because there is no stable Rust-specific ABI.

(!) I was under the impression that you could not develop a shared library in Rust even if you exposed a C ABI.

Re: Why AWS loves Rust, and how we’d like to help

#262
That's great news and will contribute further to Rusts' adoption.

Large codebases will be able to transcode to language X at some point in the future and I am waiting for the day when it can be done for Rust with projects like https://github.com/facebookresearch/TransCoder/

Re: Why AWS loves Rust, and how we’d like to help

#263
post #244

Earlier quoted context omitted.

> a bunch of FAANG driven contributions tend to make projects focused too much on particular use cases This is one of the challenges we have, as a project, in this next phase of its life: make sure that we are helping organizations achieve their goals, while not allowing it to be totally directed by them. Rust governance is set up to be resilient to takeovers by any one organization, but we're now playing with some o…

From my perspective, the size of the companies has little to do with the relative risk of outcomes that are not the best for the common good. I've seen folks at small companies try to control or unduly influence open-source software, and I've seen folks that work at large companies do it too. At the end of the day, I think it comes down to the actions of people directly involved in a community, and the culture that t…

Absolutely. And I am very happy to see Amazon and others contribute to Rust. I think everyone involved has good intentions, and for that I’m very greatful.

Re: Why AWS loves Rust, and how we’d like to help

#265

Earlier quoted context omitted.

You can use dynamic linking with Rust. You just have to stick to the C ABI when interfacing w/ shared objects, because there is no stable Rust-specific ABI.

(!) I was under the impression that you could not develop a shared library in Rust even if you exposed a C ABI.

[deleted]

Re: Why AWS loves Rust, and how we’d like to help

#266

Earlier quoted context omitted.

Great thing but I feel these companies are just too clever for Rust. Rust is a developer’s delight and I don’t want it to become like C++, and I feel the C++ standard got worse especially after these so-called great companies became a part of the standards committee. Or take the example of Web, made worse after the Googles and the Apples of the world got in. So I have mixed feelings about too many clever people doing…

> Rust is a developer’s delight and I don’t want it to become like C++, and I feel the C++ standard got worse especially after these so-called great companies became a part of the standards committee. On the Rust language team, we are extremely mindful of managing complexity, and we typically err on the side of not including a feature (even if it's desired) if it feels like it adds too much complexity or surface area…

The biggest problem here, though, is that look at Google in web standards: the web is now what Google say it is, IE 6 style. If Googlers don't get their way with the Rust language team, they'll just attack the language team head-on, or bypass them. Google have zero interest in collaboration.

Re: Why AWS loves Rust, and how we’d like to help

#267

Earlier quoted context omitted.

> Rust is a developer’s delight and I don’t want it to become like C++, and I feel the C++ standard got worse especially after these so-called great companies became a part of the standards committee. On the Rust language team, we are extremely mindful of managing complexity, and we typically err on the side of not including a feature (even if it's desired) if it feels like it adds too much complexity or surface area…

The biggest problem here, though, is that look at Google in web standards: the web is now what Google say it is, IE 6 style. If Googlers don't get their way with the Rust language team, they'll just attack the language team head-on, or bypass them. Google have zero interest in collaboration.

Google employees have actively gotten involved in collaborating within the Rust project rather than bypassing it. Of course, anything can change at any time, but this absolutist statement doesn't correlate with experiences so far.

(Also, these organizations are huge! The web standards folks and the Fuchsia folks are, as far as I know, basically disjoint, so even talking about companies like Google as a monolithic entity is fraught with issues.)

Re: Why AWS loves Rust, and how we’d like to help

#268

Earlier quoted context omitted.

You can use dynamic linking with Rust. You just have to stick to the C ABI when interfacing w/ shared objects, because there is no stable Rust-specific ABI.

(!) I was under the impression that you could not develop a shared library in Rust even if you exposed a C ABI.

A Rust artifact being used as a dynamically loaded library within a Ruby process via a C ABI is one of the very first, if not maybe first ever, production uses of Rust. You've been able to do this for a long time.

That being said, it is not simple to say, take a binary Rust Cargo project and say "please dynamically link all the crates it uses" or something like that. But if you want a dynamic library to be used by something else? First-class support for that use case exists.

Re: Why AWS loves Rust, and how we’d like to help

#269
post #90

Earlier quoted context omitted.

Java is nowhere close losing the #1/2 spot in programming language, it's just everywhere.

I agree that Java is not going anywhere, but I could absolutely see a world where JavaScript and Python are number one and two.

According to that Stack Overflow survey, JavaScript and Python are currently number one and two respectively.
Post reply on HN