21–30 of 31 posts
What web framework is this on?
Iron, apparently: https://github.com/dirk/metrics_distributor/blob/d29c897d156...
I had better luck with nickel.rs because it has an examples/ folder with quick recipes of most things you'd want to do.
Why not Go? Checks the boxes of "performant" and "safe" while remaining developer friendly compared to Rust
Why not Go? Checks the boxes of "performant" and "safe" while remaining developer friendly compared to Rust
Oh connection pooling is handled automatically by the standard library ...jk not really, it leaks sometimes ... and ...down ...goes ...my ...production database. 2 weeks ago.
Earlier quoted context omitted.
Iron, apparently: https://github.com/dirk/metrics_distributor/blob/d29c897d156...
I'm surprised people can use Iron at all. I tried really really hard to use it and found the complete lack of documentation (or, worse, outdated blog posts) made it impossible. Is there some magic necronomicon I'm missing? I had better luck with nickel.rs because it has an examples/ folder with quick recipes of most things you'd want to do.
Unfortunately it seems to be a common trend that Rust projects only provide API docs. While that can be useful I find more 'high level' docs much more helpful especially when you're new to the language and/or framework.
Earlier quoted context omitted.
I'm surprised people can use Iron at all. I tried really really hard to use it and found the complete lack of documentation (or, worse, outdated blog posts) made it impossible. Is there some magic necronomicon I'm missing? I had better luck with nickel.rs because it has an examples/ folder with quick recipes of most things you'd want to do.
My experience exactly. Nickel.rs has a fairly good set of clear examples on its website and then some more on Github. Unfortunately it seems to be a common trend that Rust projects only provide API docs. While that can be useful I find more 'high level' docs much more helpful especially when you're new to the language and/or framework.
EDIT: Oh, and I've wanted a good way for Cargo to produce additional, non-API docs through a top-level "docs" directory, but haven't found the time to properly implement it yet :/
I don't think I have enough context to understand this article. What exactly does "response time" measure, here? The diagram of the system makes it look like this program is essentially just a scan over a data stream, so each iteration should be minimally computationally intensive--certainly not in the tens of milliseconds. Is this counting time to query the left-hand-side? Or is it time from receiving a message from…
40 requests/second does sound somewhat low, but that may just be the average rate at which whatever they're aggregating generates log entries, rather than a limit enforced by resource exhaustion.
Why not Go? Checks the boxes of "performant" and "safe" while remaining developer friendly compared to Rust
The article helpfully answers that question for you. It's entirely about features unique to Rust.
Why not Go? Checks the boxes of "performant" and "safe" while remaining developer friendly compared to Rust
You can just as easily ask, why not any other language, for the exact same reason. But since you asked about Go, here are the 3 reasons that I would not pick Go: 1) no generics means less code reuse, which mean more testing of more code (potential runtime issues) 2) allowance of Null, means potential NPE/seg-faults (runtime issue) 3) non-type safe, inconsistent error handling (another runtime issue) Go is a fine lang…
Thanks for your mention of additional runtime safety, it isn't something I had considered
Earlier quoted context omitted.
My experience exactly. Nickel.rs has a fairly good set of clear examples on its website and then some more on Github. Unfortunately it seems to be a common trend that Rust projects only provide API docs. While that can be useful I find more 'high level' docs much more helpful especially when you're new to the language and/or framework.
We are in the early stages of having an official docs team; one of the things we want to do is figure out how to encourage better ecosystem docs. Towards that end, right now is the first "doc days": https://facility9.com/2016/06/announcing-rust-doc-days/ we'll be focusing on the rust-lang-nursery crates this time, but will focus on the ecosystem ones in the future! EDIT: Oh, and I've wanted a good way for Cargo to pr…
Some packages like Serde for example do provide higher level docs located with the API docs which can work fine.
Earlier quoted context omitted.
The article helpfully answers that question for you. It's entirely about features unique to Rust.
I actually saw very few unique features of Rust mentioned in the article which is why I was looking to contrast it at a high level to another language which met the criteria the author laid out while avoiding a mentioned drawback...I would hardly consider "it compiles to native" and "measured and thoughtful standard library" to be features unique to the language, though no doubt important!