backtalk icon indicating copy to clipboard operation
backtalk copied to clipboard

What is the future for Backtalk?

Open dragostis opened this issue 6 years ago • 7 comments

I feel like this particular approach to web development has a lot of potential. What are your plans for the project?

dragostis avatar Sep 11 '17 14:09 dragostis

Last time I checked in on this, I wanted to both let some of the async usability mature a little bit (like RFC 1522 and the new async macro syntax) and also wait for websocket libraries to work with Hyper 0.11 so that we don't have to host websockets on a separate port. As far as I can tell, we're still waiting on both of these? So the current plan is to continue to let things mature a bit, and then build out websocket functionality and database bindings.

Thoughts on the above? Glad to hear you think this approach has potential!

lord avatar Sep 11 '17 22:09 lord

I think that's a good approach. I would definitely do the same. The current API can be a bit discouraging for newcomers, but I'm pretty sold on the idea provided it gets a little bit simplified. (Could probably say the same about Futures/Tokio)

dragostis avatar Sep 12 '17 15:09 dragostis

Do you have any particular points you'd simplify about the API?

I think my biggest frustration so far is the need for Arcs in places that might not be obvious, but that seems unsolvable for now.

lord avatar Sep 12 '17 15:09 lord

That's my main gripe as well. I guess having await/async instead of composing futures would also be nice.

dragostis avatar Sep 12 '17 16:09 dragostis

I am also watching the space of RESTful API server frameworks in Rust. The main feature I am, actually, looking for is OpenAPI (f.k.a. Swagger) integration since there are Swagger UI and Swagger Codegen projects, which make the development much easier and fun (you write your API server, which can automatically generate swagger.json config, which can be used to generate interactive documentation and API clients in 18+ programming languages). In fact, I have implemented such a thing in Python (example), but implementing such a thing in Rust will make it safer and much more efficient...

Have you considered integrating OpenAPI support?

frol avatar Sep 12 '17 17:09 frol

I've considered it, but it'd be probably be a feature we add much further down the line, once we've solidified how the project will be structured long-term.

lord avatar Sep 12 '17 19:09 lord

I think Backtalk could get some nice attention once it stabilizes a bit and some benchmarks come out. The simplicity coupled with the performance in this case (at least in theory) sound extremely good.

dragostis avatar Sep 12 '17 20:09 dragostis