dropshot
rust-rdom
dropshot | rust-rdom | |
---|---|---|
11 | 4 | |
745 | 41 | |
1.9% | - | |
9.4 | 7.8 | |
7 days ago | over 2 years ago | |
Rust | Rust | |
Apache License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dropshot
- Dropshot β expose REST APIs from a Rust program
- Expose REST APIs from a Rust Program
-
Tips on Creating a Design-First API Using Rust
Try dropshot by the Oxide Computer team. It generates an open api spec from your rust code directly.
-
Warp or Rocket.rs or Actix Web?
What about dropshot. Not much features but very simple and auto generates swagger https://github.com/oxidecomputer/dropshot
-
What made you choose the rust web framework you're currently using?
I have used dropshot mostly because of its simplicity.
- Seed β A Rust front-end framework for creating fast and reliable web apps
-
New Tokio blog post: Announcing Axum - Web framework that focuses on ergonomics and modularity
i haven't tried it yet, but https://github.com/oxidecomputer/dropshot apparently offers automated OpenAPI generation: https://docs.rs/dropshot/0.5.1/dropshot/struct.ApiDescription.html
-
Rust for backend development?
At Oxide we are doing backend development in Rust, with our own framework: https://github.com/oxidecomputer/dropshot/#dropshot
- Dropshot a general-purpose Rust crate for exposing REST APIs
-
A web framework I desperately wish there was a Rust equivalent for: FastAPI
Dropshot from Oxide Computer includes openapi generation from code.
rust-rdom
-
Seed β A Rust front-end framework for creating fast and reliable web apps
There are two steps there: (1) rust-rdom working enough to be used by Yew, and (2) SSR support built out in Yew utilizing rust-rdom. Part (2) is pretty far away, but (1) is probably about halfway there. I think a more realistic use-case for the library is Sycamore which is much earlier and simpler than Yew. Sycamore support has a tracking issue here: https://github.com/rust-rdom/rust-rdom/issues/15
-
Call for collaborators - rdom (DOM in pure Rust)
Hey, thanks for the suggestion. It already is largely generated - if you look at https://github.com/philip-peterson/rust-rdom/blob/a805f9439c380b3bf8b02572197a6b81eb425516/src/node/raw/mod.rs#L145 everything up to line 145 is basically defining the templates and then afterward is just instantiating that template for the different node types, with a few one-off customizations like for Document. The same is done in a few other places.
What are some alternatives?
axum - Ergonomic and modular web framework built with Tokio, Tower, and Hyper
rust-dominator - Zero-cost ultra-high-performance declarative DOM library using FRP signals for Rust!
juniper - GraphQL server library for Rust
daisyui - πΌ πΌ πΌ πΌ πΌ βThe most popular, free and open-source Tailwind CSS component library
svgbobrus - Convert your ascii diagram scribbles into happy little SVG
tonic - A native gRPC client & server implementation with async/await support.
Seed - A Rust framework for creating web apps
prae - prae is a crate that aims to provide a better way to define types that require validation.
sauron - A versatile web framework and library for building client-side and server-side web applications
substrate-open-working-groups - The Susbstrate Open Working Groups (SOWG) are community-based mechanisms to develop standards, specifications, implementations, guidelines or general initiatives in regards to the Substrate framework. It could, but not restricted to, lead to new Polkadot Standards Proposals. SOWG is meant as a place to find and track ongoing efforts and enable everybody with similar interests to join and contribute.
symbolicator - Native Symbolication as a Service