Live data from Hacker News

Iggy.rs – building message streaming in Rust

blog.iggy.rs

11–20 of 63 posts

Re: Iggy.rs – building message streaming in Rust

#11
post #6

How fast can one realistically expect to be able to build decent quality system-level rust code, provided the person is already familiar with C-style programming languages and has 0 rust experience ?

The closest thing I have to a non-anecdotal answer to this question is from Google: https://opensource.googleblog.com/2023/06/rust-fact-vs-ficti...

> All survey participants are professional software developers (or a related field), employed at Google. While some of them had prior Rust experience (about 13%), most of them are coming from C/C++, Python, Java, Go, or Dart.

> Based on our studies, more than 2/3 of respondents are confident in contributing to a Rust codebase within two months or less when learning Rust. Further, a third of respondents become as productive using Rust as other languages in two months or less. Within four months, that number increased to over 50%. Anecdotally, these ramp-up numbers are in line with the time we’ve seen for developers to adopt other languages, both inside and outside of Google.

> Overall, we’ve seen no data to indicate that there is any productivity penalty for Rust relative to any other language these developers previously used at Google.

Re: Iggy.rs – building message streaming in Rust

#15
It seems like such a sharp, smart move to start with QUIC.

It provides really useful SCTP-like multi-streaming, which is a great base to start from. There's already so many good libraries the project or others can work from, and it'll just keep getting better (and better optimized, likely). https://github.com/xileteam/awesome-quic?tab=readme-ov-file#...

This seems like such a natural place where of course having a somewhat better transport protocol than we've had is a huge win. Looking forward to the next decade of QUIC.

Re: Iggy.rs – building message streaming in Rust

#16
These types of stories are what drove me to software in the first place. The ideal of a group of people working towards the same goal, for sometimes different reasons, but not for the sole purpose of monetary reward.

Good luck with the project!

I also echo some of the others, it would be great to see a sort of comparison with the alternatives so that we can better understand how the project fits in.

Re: Iggy.rs – building message streaming in Rust

#17

I'm surprised about the selection of monoio. AFAIK it requires the usage of the nightly compiler which I've found to not be a great choice when maintaining a project.

It does require nightly, but it only uses five features, one of which could be removed by adding an external crate, and the others are like, not anything super wild, for the most part. I haven't looked too deeply into the code but they all make sense to me, for example one of them is a standard library API for creating uninitialized containers, which allows you to eliminate a copy.

I have not compared monoio with glommio, which does run on stable. Would be interesting!

Re: Iggy.rs – building message streaming in Rust

#18
post #16

These types of stories are what drove me to software in the first place. The ideal of a group of people working towards the same goal, for sometimes different reasons, but not for the sole purpose of monetary reward. Good luck with the project! I also echo some of the others, it would be great to see a sort of comparison with the alternatives so that we can better understand how the project fits in.

Thank you, that's exactly how it all started! :) At some point, we will try to incorporate some benchmarks and comparisons with the other tools.

Re: Iggy.rs – building message streaming in Rust

#19

I'm not quite sure how this compares to Kafka and fluvio [1], a Kafka competitor also written in Rust? Is it more of a message queue like rabbitmq? [1] https://www.fluvio.io/

It's a message stream, so more like Kafka, Redpanda or RabbitMQ Streams (plugin). Fluvio is more mature (it's an actual product & company behind it), but we have our own ideas how to make Iggy a competitive message streaming solution :)
Post reply on HN