Comparison with softbuffer
(#273)
This commit is contained in:
parent
5c1600926e
commit
8f66bce12e
|
@ -65,3 +65,7 @@ $ RUST_LOG=trace cargo run --package minimal-winit --release --no-default-featur
|
||||||
## Comparison with `minifb`
|
## Comparison with `minifb`
|
||||||
|
|
||||||
The [`minifb`](https://crates.io/crates/minifb) crate shares some similarities with `pixels`; it also allows rapid prototyping of 2D games and emulators. But it requires the use of its own window/GUI management, event loop, and input handling. One of the disadvantages with the `minifb` approach is the lack of hardware acceleration (except on macOS, which uses Metal but is not configurable). An advantage is that it relies on fewer dependencies.
|
The [`minifb`](https://crates.io/crates/minifb) crate shares some similarities with `pixels`; it also allows rapid prototyping of 2D games and emulators. But it requires the use of its own window/GUI management, event loop, and input handling. One of the disadvantages with the `minifb` approach is the lack of hardware acceleration (except on macOS, which uses Metal but is not configurable). An advantage is that it relies on fewer dependencies.
|
||||||
|
|
||||||
|
## Comparison with `softbuffer`
|
||||||
|
|
||||||
|
There is a more recent project called [`softbuffer`](https://github.com/john01dav/softbuffer). It provides similar capabilities to what `pixels` offers, but is intentionally limited to software-only (not hardware-accelerated) rasterization.
|
||||||
|
|
Loading…
Reference in a new issue