The Rustvolution: How Rust Is the Future of Cloud Native - Flynn, Buoyant

Don't miss out! Join us at our next Flagship Conference: KubeCon + CloudNativeCon North America in Salt Lake City from November 12 - 15, 2024. Connect with our current graduated, incubating, and sandbox projects as the community gathers to further the education and advancement of cloud native computing. Learn more at kubecon.io
The Rustvolution: How Rust Is the Future of Cloud Native - Flynn, Buoyant
For the last several years, Go and Kubernetes have been all but inseparable. This monoculture approach has brought some tremendous benefits to the cloud-native ecosystem, fueling the growth of companies moving to cloud native through Go's extensive set of widely-available common tools, and the wide base of talent it provided. Today, the maturing ecosystem also recognizes some of Go's limitations and looks to languages like Rust for memory safety, fearless concurrency, and zero-cost abstractions - capabilities that address critical challenges faced by developers in modern distributed systems. With the rise of excellent Rust-native approaches to Kubernetes development, Rust promises us a world without null pointers, memory leaks, and garbage collection. Join this session to learn why (and how) to look to Rust for the future of the cloud native ecosystem.

[@nikolaramcevic]

ok, here, take my money

[@David-bh2xb]

11:00 tuples don't allocate; the code you showed does, but that's hardly c++s fault ;)

[@steveoc64]

All well and good, if Rust’s claims to safety and security were legit.
Problem is - they are not. You can still get buffer over reads and memory safety and lifetime issues using only safe rust.
So using Rust means taking a hit in performance, readability, developer velocity, a culture of deep deep dependencies, refactoring pain etc etc .. in exchange for limited safety guarantees.
In the subject of safety - Rust focuses on memory safety whilst ignoring other equally important aspects of safety.
That would be almost acceptable if the memory safety guarantees were valid. But they are not. They are marketing hype.
Perhaps the worst aspect is that Rust is mostly popular with junior and web developers moving across from node/python. Start building your next business critical application in Rust, and good luck finding any experienced devs that want to get involved.

[@ncubica]

if they are that experienced devs then why they would care about the stack, once you get proficient in a specific area switching is just a matter of willingness rather than skills, so I bet many "experienced devs" would happily switched if good $$$$ is involved. It is strange that you mention switching when our industry pretty much has switched and experienced changes all the time for at least the past ~30 years?

[@platch23]

Are the issues you mention fundamental to the language design or can they be fixed?

[@xav_624]

I'm not sure Google, Microsoft or Cloudflare have entire teams of junior Node devs that decided to rewrite and invest in Rust...

[@steveoc64]

@@xav_624 ah … the good old appeal to authority argument, wins every time doesn’t it.
Grease filled cheeseburgers on a preservative filled bun must be much better for you than a country cooked steak, because McDonalds makes a lot more money than the local bar and grill.
Got it …
Lucky for you, Joe Biden himself wants you to use Rust now, so you have the ultimate appeal to authority argument to convince anyone that Rust is the only choice going forward.

[@steveoc64]

@@ncubica a rather odd choice of argument you use there … that experienced devs would agree to waste a few years of their career using Rust, because the $$$ is good ?
Statistically - the money is with Zig, Elixir, C/C++, Erlang, Java, Go, Python / ML
Rust jobs are in the commodity minimum wage web dev basement