Is this a completely new runtime, or was it built on top of the existing tokio runtime?
HN user
fransiscoli
This is awesome! It would also be really nice if the scraper would organize the ideas based on keywords in a given tweet.
Also, not everything is trying to solve a problem.
True. I'm not "opposed" to anyone doing this, it looks like a really cool project. My issue is people rewriting things in Rust and presenting it as way better simply because of the language it was written it. I understand that rust brings strong compile-time guarantees, but I would use a mature and battle-tested C program over a new, hobbyist rust rewrite any day of the week.
What's up with this whole "Rust rewrite" craze? The coreutils are battle tested and mature as they are, and I don't see how rewriting thousands of lines of code in Rust will change anything. Isn't this solving a non-existent problem?
Is this a new release? I seem to remember hearing about this a while ago...
I really love the Porsche Taycan, but Tesla's expansive charging network ties me to the Model S.
I think lifetimes are the part of Rust that people see as ugly. I recently wrote the following lines of code:
struct Parser<'a, 'b, T> {
value: &'a [T],
inner: InnerParser<'a, 'b>
}
impl<'a, 'b, T> for Parser<'a, 'b, T> {
fn parse<T: Into<String>>(value: T) -> &'static str {
...
}
}
and the equivalent code in Scala: class Parser[T] {
var value: List[A] = Nil
var inner: InnerParser = Nil
def parse(value: String): String = ...
}
of course, those programs are not semantically equivalent, but you can clearly see that the Scala version is the more elegant of the two. I can't think of any other way that you could syntactically express lifetimes, but I can see why people would see Rust as ugly.I was wondering that too..
I wonder what the rust core team's stance is on projects like this?