Rust has definitely made me a better systems engineer overall. But, its not a language I can use for web dev. I hope, it gets easier to integrate rust into python in future.
How so?
Rust can be difficult to learn and frustrating, but it's also very exciting
41–50 of 282 posts
Re: Rust can be difficult to learn and frustrating, but it's also very exciting
#42Earlier quoted context omitted.
Any reason you didn't scale up horizontally with more python instances?
We have seen production users choose to make this port to save on server costs. You can always scale horizontally, but it comes with a price tag.
Also complexity - managing an order of magnitude more instances is more hassle.
Re: Rust can be difficult to learn and frustrating, but it's also very exciting
#43Earlier quoted context omitted.
Oof, I got burned by the tokio/futures ecosystem too. It's definitely a frustrating experience. Thank god it was only a pet project with no deadline pressure, cause it's been 6months now and I'm still waiting for stabilization.
Which stabilization?
async/await is the big one :)
Re: Rust can be difficult to learn and frustrating, but it's also very exciting
#44Earlier quoted context omitted.
Rocket requires the nightly Rust compiler, which isn't something I find acceptable for production applications, and it's synchronous, so it's really slow. I have been rather disappointed by what I perceive as the author's unwillingness to work towards stable Rust. They have a GitHub issue where they track all of their dependencies on nightly, and kind of just say they aren't going to do anything about it -- it's up t…
It's not that he's unwilling to make it run on stable, it's that he has to sacrifice ergonomics to make it run on stable. Despite it not being async, yet, Rocket is my go-to because it has the best ergonomics. Something like actix-web may be more performant, but it's ergonomics are poor in comparison. Regardless, Rust is stabilizing procedural macros which just leaves the never type as the last stabilization required…
Is Rocket still on track to run on stable by the end of 2018, as per your comment here?
https://news.ycombinator.com/item?id=16543914
Anecdotally, I've been hearing claims that Rocket will run on stable "real soon now" for quite a while now. It just doesn't look like it's going to happen.
Re: Rust can be difficult to learn and frustrating, but it's also very exciting
#45Earlier quoted context omitted.
It depends, my biggest struggle right now is with the tokio/futures ecosystem, so I'm on gitter::tokio quite a bit, and have posted once on /r/rust. With patience, I eventually solve many problems, but the lead-time is costly. Plus when I'm doing something wrong in my code, rustc could take over 5 minutes compiling, and then come back complaining. Even when I find someone willing to help me debug, the process takes a…
I think the tokio/async ecosystem just isn't ready for prime time. Hopefully this (and compile times!) get much better.
While compile times can be slow, the rust system is checking so much for you, so that you can have a predictable @scale runtime. What was the issue with tokio?
Plus, with async/await Futures coming in soon, already on nightly right, this should become good if not already?
Rust went down the Kotlin route of not including coroutines/async/await initially and allowed Lib devs to build, but now have included as we all know. But anyways, keep at it, I have found Rust to be very helpful, using it at the startup I am at, and will keep using it deeper and in more complex scenarios.
Re: Rust can be difficult to learn and frustrating, but it's also very exciting
#46Earlier quoted context omitted.
We have seen production users choose to make this port to save on server costs. You can always scale horizontally, but it comes with a price tag.
Also complexity - managing an order of magnitude more instances is more hassle.
But "more hassle" by an order of magnitude that gradualy reduces when growing the number of instances.
Re: Rust can be difficult to learn and frustrating, but it's also very exciting
#47Earlier quoted context omitted.
Which stabilization?
async/await is the big one :)
I guessed, it’s huge for sure :) since everything does work on stable, I wasn’t sure if there was something else I was missing, or if you meant the libraries, which still have some churn to go.
I can’t wait myself.
Re: Rust can be difficult to learn and frustrating, but it's also very exciting
#48Earlier quoted context omitted.
It's not that he's unwilling to make it run on stable, it's that he has to sacrifice ergonomics to make it run on stable. Despite it not being async, yet, Rocket is my go-to because it has the best ergonomics. Something like actix-web may be more performant, but it's ergonomics are poor in comparison. Regardless, Rust is stabilizing procedural macros which just leaves the never type as the last stabilization required…
Is Rocket still on track to run on stable by the end of 2018, as per your comment here? https://news.ycombinator.com/item?id=16543914 Anecdotally, I've been hearing claims that Rocket will run on stable "real soon now" for quite a while now. It just doesn't look like it's going to happen.
Looks like not quite: https://github.com/SergioBenitez/Rocket/issues/19
Never type can use a crate. The hygiene and error APIs aren’t going to be stable soon.
In theory it looks like rocket could use that package and accept worse error messages and build on stable. Sergio would have to weigh in on that, though, I could be wrong.
Re: Rust can be difficult to learn and frustrating, but it's also very exciting
#49Can anyone recommend exercises for learning a new language. For example, something like "implement a class with these methods", or implement a function that does this. Something that is realistic, should only take an hour or two to implement for a competent programmer, requires you to learn more complicated features of a language, yet I can finish before getting bored or frustrated?
[deleted]
Re: Rust can be difficult to learn and frustrating, but it's also very exciting
#50Earlier quoted context omitted.
It depends, my biggest struggle right now is with the tokio/futures ecosystem, so I'm on gitter::tokio quite a bit, and have posted once on /r/rust. With patience, I eventually solve many problems, but the lead-time is costly. Plus when I'm doing something wrong in my code, rustc could take over 5 minutes compiling, and then come back complaining. Even when I find someone willing to help me debug, the process takes a…
Oof, I got burned by the tokio/futures ecosystem too. It's definitely a frustrating experience. Thank god it was only a pet project with no deadline pressure, cause it's been 6months now and I'm still waiting for stabilization.
I spent two years of my professional career with Rust doing async web services and most of it with tokio/futurrs. First you finally get comfortable with Rust and then you do the learning again with futures... I did it. It paid off. Wrote some fast and stable services with it and it is not that hard when you get to the other side.
But for newcomers, be careful with references when using futures and be smart how you use the combinators. The errors can be tough and this is the only place in Rust ecosystem where they don't really help at all sometimes.