HTTP frameworks in Rust so far: On the one side there's the batteries-included, nightly only, framework that requires compiler plugins to work. On the other side there's sparse, build-your-own-framework kits. Lots of boilerplate. I'm waiting for the middleground.
-
Show this thread
-
(And no, I'm not going to build *yet another* framework. I refuse :P)
3 replies 0 retweets 3 likesShow this thread -
Replying to @yoshuawuyts
lol yes yes i feel this. you should talk to
@withoutboats and the webservices-WG, its one of our 4 key domains this year and i don't think we'll solve this issue but we're def gonna improve it a ton2 replies 0 retweets 1 like -
Replying to @ag_dubs @withoutboats
Sounds really cool! - I think between futures 1.0, the CLI WG, & H2 improvements, we're setting us up to succeed here :D
1 reply 0 retweets 1 like -
Replying to @yoshuawuyts @withoutboats
yeah it's gonna be exciting, year of Rust on Server is hopefully a reasonable close future! then also Rust in the browser with wasm... hehe i'm so amped for all of this
2 replies 0 retweets 2 likes
Hahaha, yeah! :D We might be getting a native DOM diffing API in the browser too, so if we can simply instrument that from Rust, having complete frontend frameworks in Rust should be straight forward too!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.