Earlier quoted context omitted.
I hope you are trolling. Would more women in tech be good? Of course! However there is some crazy SJW stuff going on at the moment in a lot of projects. People pushing for things like Master/Slave to be renamed to Leader/Follower. Wanting things like man (as in the man command on Linux) renamed to something non-gender-based. I mean fucking come on. I am all for a more inclusive environment but some things are just st…
Yeah the master/slave thing pisses me off. They are words in the dictionary used to describe something and that is all.
Rust 1.5
71–80 of 159 posts
Re: Rust 1.5
#72I know this seems like a trivial issue, but I've been bothered by the try!() macro for a while. I keep hoping then will adopt the "?" postfix operator to mean the same thing, because it seems to increase readability a lot. I'm open to other ideas too, but that seemed like the simplest way to get the error handling out of the way. Ordinarily I try hard not to complain about syntax, but this seems to cause people to us…
Re: Rust 1.5
#73Re: Rust 1.5
#74Earlier quoted context omitted.
No. We release every six weeks, period. Any resemblance to other releases, living or dead, is purely coincidental.
[deleted]
Re: Rust 1.5
#75Earlier quoted context omitted.
No. We release every six weeks, period. Any resemblance to other releases, living or dead, is purely coincidental.
[deleted]
Re: Rust 1.5
#76I know this seems like a trivial issue, but I've been bothered by the try!() macro for a while. I keep hoping then will adopt the "?" postfix operator to mean the same thing, because it seems to increase readability a lot. I'm open to other ideas too, but that seemed like the simplest way to get the error handling out of the way. Ordinarily I try hard not to complain about syntax, but this seems to cause people to us…
It seems really wasteful to be working on a specific macro rather than a general-purpose solution (i.e. an equivalent of do notation or scala's for/yield) that will work for things other than error handling.
If you want real do, and I do, then you need HKT, which is a massive upgrade to our type system that will take a very long time. If we can do something simpler in the meantime to ease some pain, then it's worth it.
Re: Rust 1.5
#77Re: Rust 1.5
#78I've been excited to try Rust for some time now, but I've been holding off, only because I'm primarily developing web applications and I've heard from a few people that Rust is better suited for other tasks (based on the built-ins, packages, etc.?), despite there being at least a few frameworks out there. What are your thoughts on this? Have things changed? Is the assumption just dead wrong, and Rust is in fact treme…
Re: Rust 1.5
#79Re: Rust 1.5
#80Earlier quoted context omitted.
I have historically been skeptical of Rust as an application-tier language, but my experiments with it as of late have made me reconsider a bit. The largest weakness, imho, is the lack of libraries for various standards and formats: do you really want to implement OAuth yourself? (EDIT: Apparently we do have OAuth now. ha!) The maturity of the Rails ecosystem has spoiled me. Here's a random fact that I've always foun…
I have witnessed someone implementing OAuth2 themselves: https://crates.io/crates/inth-oauth2 I hope they solved the problem permanently, since this is the third crate attempting OAuth2 and the first two are abandoned/incomplete.