Rocket – Simple, Fast, Type-Safe Web Framework for Rust
1–10 of 49 posts
Re: Rocket – Simple, Fast, Type-Safe Web Framework for Rust
#2Never thought I would see the release of v0.5. Congrats to all the maintainers!
Can’t wait to play with this!
Re: Rocket – Simple, Fast, Type-Safe Web Framework for Rust
#3And here are the changes for the recently released v0.5: https://rocket.rs/v0.5/news/2023-11-17-version-0.5/
Re: Rocket – Simple, Fast, Type-Safe Web Framework for Rust
#4The recent 0.5 release was discussed 5 days ago here: https://news.ycombinator.com/item?id=38306540
Re: Rocket – Simple, Fast, Type-Safe Web Framework for Rust
#5introducing a new term when an established term exists seem to add another overhead. "but bro, you'll get used to it in no time." i hear you, buddy. it just leaves a bit bad taste.
anyway, i can't believe i say this, i think dhh's words on tradeoff between squeezing performance out of an ecosystem and "just throw more hardware on it" is a tradeoff that i can clearly choose.
Re: Rocket – Simple, Fast, Type-Safe Web Framework for Rust
#6introducing a new term when an established term exists seem to add another overhead. "but bro, you'll get used to it in no time." i hear you, buddy. it just leaves a bit bad taste. anyway, i can't believe i say this, i think dhh's words on tradeoff between squeezing performance out of an ecosystem and "just throw more hardware on it" is a tradeoff that i can clearly choose.
What term are you referring to?
Also, speed and performance aren’t the only reasons to use Rust. Rust also helps ensure correctness in significant ways, and make stable applications.
Re: Rocket – Simple, Fast, Type-Safe Web Framework for Rust
#7Rocket's documentation and overall 'dev experience' are very pleasant. In the past, I felt like I was making a significant tradeoff when using Rocket over more actively developed frameworks (Axum and Actix Web). With v0.5 (finally) coming out, and the Rocket Web Framework Foundation, that feels like much less of a concern.
A great example of Rocket in use is the official Rust website, which is open source.
Re: Rocket – Simple, Fast, Type-Safe Web Framework for Rust
#8introducing a new term when an established term exists seem to add another overhead. "but bro, you'll get used to it in no time." i hear you, buddy. it just leaves a bit bad taste. anyway, i can't believe i say this, i think dhh's words on tradeoff between squeezing performance out of an ecosystem and "just throw more hardware on it" is a tradeoff that i can clearly choose.
What term are you referring to? Also, speed and performance aren’t the only reasons to use Rust. Rust also helps ensure correctness in significant ways, and make stable applications.
I would guess "fairings", at least that's the only one I don't know on this page: https://rocket.rs/v0.5/guide/
Re: Rocket – Simple, Fast, Type-Safe Web Framework for Rust
#9From a quick glance it seems still vulnerable to trivial slowloris’ing D:
Is anybody actually exposing their rust-based websites to the internet? I want to, but it seems that for some reason every rust web framework keeps TCP connections open _forever_, meaning that even with file descriptors bumped to 64000, my web server runs out of FDs and needs to be killed and restarted every 3 hours or so. The standard advice seems to be “don’t do that, put your rust app behind a reverse-proxy written in C or Go, and let the proxy handle the complexities of TCP”, but it seems so sad to add an extra layer of latency and complexity just to close idle connections ;(
Re: Rocket – Simple, Fast, Type-Safe Web Framework for Rust
#10From a quick glance it seems still vulnerable to trivial slowloris’ing D: Is anybody actually exposing their rust-based websites to the internet? I want to, but it seems that for some reason every rust web framework keeps TCP connections open _forever_, meaning that even with file descriptors bumped to 64000, my web server runs out of FDs and needs to be killed and restarted every 3 hours or so. The standard advice s…
How do you handle https if you don't? Do you use certs directly in code? Also, do you use LetsEncrypt or do you actually pay for certs?
I have been developing websites all my grown life and I always put them behind a reverse-proxy. That has never been the culprit of any slowdowns in my experience and nginx is very, very fast and supports everything you may want to have.
I usually nowadays reach for caddy just because it's so much simpler and fast enough.