5 ms·
Excellent guide, something that I'll need in near future. I wonder why the author chose hyper instead of iron though...
by Shoothe 9y ago
Excellent guide, something that I'll need in near future.
I wonder why the author chose hyper instead of iron though...
- allengeorge 9y agoOr rocket/Gotham. Personally, I preferred working with rocket far more than iron, and that despite the fact that rocket is nightly-only.
- Spartan-S63 9y agoThe plan is for Rocket to run on stable by the end of 2018. v0.4 is getting closer and the two biggest features remaining to be implemented for it are connection pooling (which I have an open PR that's being worked on) and CSRF support.
- kibwen 9y agoCan you cite this claim? I've taken a look at the list of unstable features that Rocket uses, and at times it almost seems like a deliberate ploy to use every nightly feature imaginable. And the feature that it really does actually need for its API, procedural macros, isn't guaranteed to land this year AFAIK (of course, I'd love to be wrong).
- steveklabnik 9y agoSergio has said it on IRC multiple times. Procedrual macros are not only landing this year, but in the first half of the year. See the roadmap.
- kibwen 9y agoI've seen that macros 2.0 are landing this year, but it's unclear to me whether "macros 2.0" only refers to `macro!` or also to procedural macros.
- steveklabnik 9y agoMacros 2.0 means both Macros By Example 2.0 and Procedrual Macros 2.0. :confetti_ball:
- beckler 9y agoI'm pretty sure Iron is no longer maintained.
- carlosdp 9y agoYea unfortunately Iron isn't actively maintained anymore.
- azdle 9y ago> Nevertheless, I believe taking this route and going slightly lower level with Hyper gave you some nice insights into how you can leverage Rust to write a safe and performant webservice. Using hyper directly definitely gives you a better idea how everything fits together and it is much more helpful for understanding how Futures work.
- wawf233epoiwe 9y agoRead the post; they explain the choice