snapbox
wgpu
snapbox | wgpu | |
---|---|---|
6 | 197 | |
111 | 11,164 | |
2.7% | 4.7% | |
9.4 | 9.9 | |
7 days ago | 1 day ago | |
Rust | Rust | |
Apache License 2.0 | 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.
snapbox
-
Announcing diff.rs!
If needed, here is an example of per-word diffing and highlighting of trailing newline differences.
-
Trycmd just ignores my tests
I see. I would try writing the same name as in your Cargo.toml. For example, if yours was toml [package] name = "caesor_cipher" I would try bin.name = "caesor_cipher" It seems that trycmd might ignore a test if the bin.name field is incorrect: https://github.com/assert-rs/trycmd/issues/105
-
Rust: A Critical Retrospective
I find rustdoc lacking for clap. rustdoc does a good job with API reference documentation and is improving in its handling of examples but derive reference and tutorial documentation are a weak point.
For examples, its improving with the example scraping work (e.g. https://docs.rs/clap/latest/clap/struct.ArgMatches.html#meth...) but testing of example is still lacking. I've written trycmd to help (https://github.com/assert-rs/trycmd).
For derive reference and tutorial documentation, your choices are
- A very long, hard to navigate top-level documentation, see https://docs.rs/structopt/latest/structopt/
- External documentation, see https://serde.rs/
- Dummy modules to store your documentation (I've seen this used but can't remember one off the top of my head)
For clap, my documentation examples are best served as programs and we've had a problem with these being broken. The Rust CLI book has a decent strategy for this by pulling in code from external files (https://rust-cli.github.io/book/index.html). I was tempted to do that for clap where example code and output (all verified via trycmd) are pulled into an mdbook site but I've stopped short and just have a README that links out to everything (https://github.com/clap-rs/clap/blob/master/examples/tutoria...). Its not great.
-
Great thanks to the rust community for having a book (sort of like the rust book) for some crates as well. Makes everything infinitely approachable
Another problem we found in clap was it was easy for our examples to build but harder to make sure they worked. This is why I wrote trycmd (example "tests").
-
ANN: `trycmd` v0.7.0 released!
Would love feedback on on some of the known questions or whatever else is on your mind!
-
trycmd: Snapshot testing for a herd of CLI tests
The design is inspired by trybuild with thought given to how mdBook books could pull in content so you can verify a code sample, the command for running it, and the output. In considering how to keep clap's website up-to-date, I had this idea and threw it together to see how well it works. Overall, seems good with room for improvement. I'll have to give this a try on a real world program soon.
wgpu
-
Zed Decoded: Linux When? – Zed Blog
Wgpu seems very very well loved & supported, is one of the most successful comings together of the graphics world in ages. I'd love to hear some actual critique of it, hear what people think are shortcomings, because it feels to an outsider like this is the fantasy land, that we're living in the better place now. https://github.com/gfx-rs/wgpu
-
GPU Compute in the Browser at the Speed of Native: WebGPU Marching Cubes
Oh look it's subgroup support landing last week: https://github.com/gfx-rs/wgpu/pull/5301
- 3D and 2D: Testing out my cross-platform graphics engine
- Warp Terminal is now available for Linux
- Linux version of Warp terminal is here
-
Building the DirectX shader compiler better than Microsoft?
And wgpu has been doing this for years. Things like descriptor indexing are not exposed to the web but used by Rust (mostly) engines on native.
https://wgpu.rs/
-
New Renderers for GTK
If they used https://wgpu.rs/ they would get directx and metal for free (:
-
Show HN: WebGPU Particles Simulation
IIRC it was delayed multiple times. I think the first intent to ship from chrome was before 100 but they kept pushing it off. Firefox still does not support it. There are projects like wgpu[0] that wrap provide a higher level API and I have used some projects using it with no issues. WFIW I didn't see any issue with OP's demo either.
[0] https://github.com/gfx-rs/wgpu
- Deno 1.39: The Return of WebGPU
-
How do I become a graphics programmer? – A guide from AMD Game Engineering team
wgpu, the Rust WebGPU implementation is the bee's knees. https://wgpu.rs/ You can use it beyond the web.
What are some alternatives?
clap-rs - A full featured, fast Command Line Argument Parser for Rust
vulkano - Safe and rich Rust wrapper around the Vulkan API
typos - Source code spell checker
tauri - Build smaller, faster, and more secure desktop applications with a web frontend.
biscuit - Biscuit research OS
glow - GL on Whatever: a set of bindings to run GL anywhere and avoid target-specific code
browser - Create Elm programs that run in browsers!
rust-gpu - 🐉 Making Rust a first-class language and ecosystem for GPU shaders 🚧
steam-for-linux - Issue tracking for the Steam for Linux beta client
bevy - A refreshingly simple data-driven game engine built in Rust
cargo-public-api - List and diff the public API of Rust library crates between releases and commits. Detect breaking API changes and semver violations via CI or a CLI.
bgfx - Cross-platform, graphics API agnostic, "Bring Your Own Engine/Framework" style rendering library.