Live data from Hacker News

A Fresh Look at Rust

lucumr.pocoo.org

101–110 of 157 posts

Re: A Fresh Look at Rust

#101
post #77

Earlier quoted context omitted.

> A lot of "rust xxx" searches would link to outdated articles or to stale links in the Rust official docs. Or to an old mirror of the official doc, http://web.mit.edu/rust-lang_v0.9 is the bane of my rustperience.

It doesn't help that there's a game called Rust out there!

I feared that, but overall combined with programmatic context (e.g. iter, array or whatever) I've had the game come up very rarely.

Re: A Fresh Look at Rust

#102
post #91

Earlier quoted context omitted.

Does OCaml still doesn't compile 1.0 + 2.0 or has that changed? Small stuff like this really bother some people and they fly off to Pythonland never to be seen again.

> Does OCaml still doesn't compile 1.0 + 2.0 or has that changed? I'm not quite sure what you mean? In any case, the compilation speed isn't really an issue (especially since we're talking about Rust, which last time I used it wasn't exactly fast).

I think he's talking about the fact that OCaml has separate operators for floating point (i.e. in his example, you'd use 1.0 +. 2.0).

Re: A Fresh Look at Rust

#103
Disappointing how this author's hyper-criticism of Python is not applied equally to Rust, presumably because Rust is newer and this author has other bones to pick with Python. If Rust has a problem, he will sell that it is charming (e.g. "it makes you think", "you just need to think differently", "needs more love"). The glass will be full any day now! But if any new effort in Python is not absolutely perfect or just not to his personal taste, he will sell that it's because Python is a horrible pile of shit because nobody listens to him. The glass isn't only half empty, it is also too hard, too brittle, too cold and actually also too warm and it turns out that not even its transparency is a good feature.

After several years of this routine, it has become very old. For God's sake, if your ex is so bad then just move out of her house already. Don't just keep eating the dinners she prepares and complaining about them and saying you'll move out. Actually move out and stop talking about her all the time. Yet another article about how you can't stand how she clips her nails is not helping anyone.

Re: A Fresh Look at Rust

#104
post #8

I rarely have to do anything as low-level as rust would demand. More often than not I find myself using Python, but I had the same feelings when I started looking into rust a few weeks ago. It was exciting seeing the full pattern-matching, especially. I have a desire to get some experience in the area, but the problem is what to make. Does anyone have any ideas for some smallish libraries that would benefit the commu…

I've been thinking about implementing fastcgi so that I could play with simple rust webapps. Haven't had time to start on it though, so if that sounds interesting you'd have at least one immediate user.

Instead of FastCGI just speak HTTP. And for those there are libraries already.

Re: A Fresh Look at Rust

#105
post #82

Earlier quoted context omitted.

No, it's just in this example. In idomatic rust you would write this probably: https://gist.github.com/mitsuhiko/1f37c1092bdf54ce4213 The `try!` macro unwraps the okay part of the expression and early returns the err part. The nice thing about the explicit results is that you will do the error handling. With Python you often do not know if an error might come.

Ok, much better. At the risk of looking more like a java try/catch, is it possible to wrap multiple statements in a single try! clause ? Or at least have some way of saying " if there's any error in this block of code, simply stop execution and forward it to the calling statement"

No, but that's would also defeat the purpose. The idea of results is that you know from looking at the code what can fail. If you remove that information you might as well use exceptions.

Re: A Fresh Look at Rust

#106
post #103

Disappointing how this author's hyper-criticism of Python is not applied equally to Rust, presumably because Rust is newer and this author has other bones to pick with Python. If Rust has a problem, he will sell that it is charming (e.g. "it makes you think", "you just need to think differently", "needs more love"). The glass will be full any day now! But if any new effort in Python is not absolutely perfect or just…

The criticisms of Python covers about one sentence, and they're all to the point. I don't see how you can turn a well-written post 99% about Rust into "hyper-criticism of Python".

> he will sell that it's because Python is a horrible pile of shit because nobody listens to him

I'm not sure we're talking about the same Armin here...

Re: A Fresh Look at Rust

#107
post #100

Earlier quoted context omitted.

> Does OCaml still doesn't compile 1.0 + 2.0 or has that changed? I'm not quite sure what you mean? In any case, the compilation speed isn't really an issue (especially since we're talking about Rust, which last time I used it wasn't exactly fast).

He's probably referring to the fact that you have to use different arithmetic operators for int and float in OCaml, so it would have to be 1.0 +. 2.0

Ah, that makes sense. It's still the case, but I guess it may be going away once implicits are released.

Re: A Fresh Look at Rust

#109
post #77

Earlier quoted context omitted.

It doesn't help that there's a game called Rust out there!

I feared that, but overall combined with programmatic context (e.g. iter, array or whatever) I've had the game come up very rarely.

It gets a bit annoying that a lot of Rust libraries are named something rust-themed. I was looking at which web framework I should use (between Nickel and Iron) and so searching "rust nickel vs iron" returned absolutely nothing of relevance.

I did learn something about metals, though, so there's that.

Re: A Fresh Look at Rust

#110

Earlier quoted context omitted.

I feared that, but overall combined with programmatic context (e.g. iter, array or whatever) I've had the game come up very rarely.

It gets a bit annoying that a lot of Rust libraries are named something rust-themed. I was looking at which web framework I should use (between Nickel and Iron) and so searching "rust nickel vs iron" returned absolutely nothing of relevance. I did learn something about metals, though, so there's that.

Hah yes that is definitely an annoying property of "cutesy" library names, they're cute and fairly easy to remember but finding them afterwards is a pain in the ass compared to unfun dreary names like "rust-web".
Post reply on HN