Rust for Professionals • Hacker News Board

Re: Rust for Professionals

#101

Post by alltheworlds » Thu, Jan 05, 2023, 10:21 AM UTC

Gigachad wrote: post #34

rr808 wrote: post #33

Earlier quoted context omitted.

Yeah I wish there was a strong jobs market for Rust developers then I'd feel like I wasn't wasting my time.

There aren't many full Rust jobs but there are a whole lot of companies with ever expanding bits of Rust in production. Probably the best way at this point is to push it internally and put together a convincing case for using Rust for new projects.

This is our company. Frankly, I don't agree with this approach. We're a hedge fund that uses Java for low latency trading systems. Someone pushed for Rust to be used for a new project, because they wanted to use it, and now we have a split codebase. We have duplicate code (eg. connections to external APIs) written in Java and Rust, and now we have two sets of code to maintain whenever one of those APIs change.

I always get annoyed when I hear about people suggesting to push for a language in a company because they feel it would be a good fit. Sure, maybe it would be, but now the company will always require experts not in one language but two, and developers are no longer as fungible between teams.

Having said that, from a selfish perspective, I will use it to write some production Rust code in the future.

Re: Rust for Professionals

#102

Post by aussiesnack » Thu, Jan 05, 2023, 10:32 PM UTC

alltheworlds wrote: post #100

aussiesnack wrote: post #92

Earlier quoted context omitted.

> I suspect the cause is a whole bunch of people saying that Rust is too hard, Perhaps, though I haven't myself witnessed anyone saying it's 'too hard'. Just that people (like me and everyone I know who's tried to learn) find it 'hard'. Then we're informed it's not. My thought about the underlying reasons was more along the lines of the Rust community's inclusion ethic. I find that entirely laudable in general. But l…

I write low latency Java for a living (usual finance type stuff). Our fund has started to use some Rust but I've not yet delved. I'm still trying to resolve whether it will be worth my time to do so. I'm one of those unusual people who really enjoys Java programming for the most part because it both allows you to be very productive but also offers enough sophistication to achieve really high performance.

I wouldn't let descriptions[1] of Rust as difficult to learn put you off. I'm long out of date with it so can't make confident comparisons with the Java of 2022 (2023!), but you might enjoy exploring what Rust brings to the table. It's certainly very capable, and those who become fluent with it claim the early productivity hit is eventually overweighted by the correctness/longevity of what you produce. I haven't reached that stage but have no reason to doubt the claims.

If you do interact with the Rust community, I suggest doing so in Shiny Happy Person guise.

[1] only the Rust community considers these 'complaints'

Re: Rust for Professionals

#103

Post by joaquincabezas » Fri, Jan 06, 2023, 11:24 PM UTC

kika wrote: post #12

tmtvl wrote: post #5

Earlier quoted context omitted.

I saved up Common Lisp resources for a few years and in 2022 I finally decided to sit down and learn it. It was entirely worth it, so I recommend you sit down to learn Rust one weekend. In fact, do it next weekend. Getting started on anything is always better done sooner than later.

joaquincabezas, don't listen to this person. It's a trap. In February I found myself in AirBnB alone with nothing to do, because my wife had to stay back home for an extra week and I waited for her to join me. AirBnB had a decent work desk, decent(-ish) monitor and barely ok keyboard so I decided to learn Rust. Now it's January, I'm at 3000+ LoC of Rust and about 4000 in Dart/Flutter and trying to make the project to…

fn main() { println!("Too late I guess!"); }