Meet rustox! Rust community in Bangalore

1st June 2017

/ 4min

Another rust-lang community got added to the Users group. This time in Bangalore. It's a great opportunity for people interested in learning more about the language and also for Rustaceans like us to spread awareness about the benefits of adopting Rust to their toolbelt as a systems language.

This is a blog post on the experience of attending the first Rust meetup in Bangalore.

The meetup began with celebrating 1.0 (May 15) stable release of Rust by cutting the cake. Then we got delivered an awesome pitch by Saifi introducing what Rust has to offer, what improvements it brings over other languages, what redundancies it resolves and why one should invest time in learning it. After the slides we got a hands on coding session which got initiated by installing and setting up Rust in their machines.

Here's the slide by Saifi for interested ones.

The audience of the meetup were people coming from imperative programming background (mostly Python and Java and C). We also discussed planning details of the next Rust meetups and folks there seemed really interested which is really encouraging.

As I come from a Python background and got started into Rust 2 years back, I was asked to share experiences as a newbie moving from a dynamic, managed language Python; to a statically typed, granular control oriented language that is Rust. Key points to mention would be:

  • It takes time to learn Rust (6 months on average to be really comfortable, for someone coming from dynamically typed and imperative background), because you will be facing topics that you didn't had to care about and also some functional programming concepts which you'll have to grok along the way.

  • If you have functional programming background then it would take around 2 weeks to get comfortable with syntax. I realized this when I started reading more on haskell, type theory and category theory. So having a FP background will definitely help.

  • Newcomers to Rust are often scared by the verbose syntax, lifetime symbols and traits sprinkled over in function signatures and elsewhere but fear not my friend; they are there for a good reason because Rust puts emphasis on encoding lots of guarantees and assumptions about the correctness of your program in the source code itself and not rely on runtime checks (some exceptions to this being "bounds checking" which has to be done at runtime).

  • One of the best things you get from the rustc compiler is the error messages which is unlike other compilers I have experienced. I got to know more about this by working on an error issue and its great to see how articulate the compiler can be on pointing out mistakes in your code. Another thing is if you mistyped a method name or a module import it would give you hints towards that method name or the variable name which is sleek.

  • You will get to know a lot of things from the Rust compiler about the control flow of your program and how resources are managed at syntactic and semantic level.

  • All I have to say is I have benefited a lot and learned some finer details about programming in general by adopting Rust.

I really look forward for our rustox community on organizing amazing content and guides for people who are curious to learn and build stuff with Rust. I would like to thank Saifi Ragini and Jeeva the efforts of whom made this meetup possible. I probably missed few sessions by other folks as I came half hour late so apologies if I missed anything to mention here. Anyways Checkout photos below.

rustox community The group pic!

rustox community

IMAGE Me sharing experience of moving from Python to Rust.

If you are in Bangalore and someone interested in Rust, make sure you do follow us on twitter @rustox and refer to rustox community page, for frequent updates to talks and hackathons that we will cooking for our coming meetups.

Want to share feedback, or discuss further ideas? Feel free to leave a comment here! Please follow Rust's code of conduct. This comment thread directly maps to a discussion on GitHub, so you can also comment there if you prefer.