steel
wgpu
steel | wgpu | |
---|---|---|
9 | 197 | |
871 | 11,061 | |
- | 3.8% | |
9.0 | 9.9 | |
7 days ago | 6 days 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.
steel
-
Helix: Release 24.03 Highlights
I absolutely don't mind the plugin system being a Scheme. It's a plugin for a text editor, and Steel(https://github.com/mattwparas/steel) seems to be a lot less of a maintenance burden than WASM plugins(besides that I find the WASM tooling to be extremely complex).
But besides all that, Helix learned be that I don't need fancy plugins or endless finicking with config files and toolchains. Using a combination of other tools, like yazi and lazygit, helps me not only inside my editor but outside of it as well. And Kakoune does this even better. In that regard it has been a real eye-opener and refreshing. The downside is, it's hard to go back to other editors!
- Steel – An embeddable and extensible Scheme dialect
-
Steel – An embedded scheme interpreter in Rust
Basically the differences are in the concepts you'll use to write code. Lisps themselves are very different from each other, but just like the languages you're used to, lisps have standard libraries that can be called, and those building blocks can be used to build applications or whatever else. In this case specifically, Steel provides the facility to call Rust functions within a Steel program: https://github.com/mattwparas/steel.
So, although I haven't used Steel, it looks like the advantage you'd get from using it is the opportunity to take advantage of features it provides like transducers and contracts, which are feature common to other Lisps as well.
So, just like choosing any other language, it boils down to a series of tradeoffs.
-
What’s everyone working on this week (19/2023)?
I've been adding my language steel as the plugin language for helix. There is a lot of discussion around what the plugin system will look like for helix and I figured I'd give it a shot since steel was designed originally for embedding. So far its working pretty well, it turns helix into emacs (without the nearly 50 years of development, so not quite as good). I'm reasonably confident the changes won't be accepted upstream (my language is a scheme but I am the only developer at the moment), but even if not it is a really fun experiment. Hoping that it can be used as a basis for whatever plugin system they eventually land on. An example of what configuration would look like:
-
What’s everyone working on this week (7/2023)?
Working on automatic doc generation for steel. I've been procrastinating building this out for a while - some of the easy cases are really easy, while the hard cases are definitely not easy.
-
What's everyone working on this week (6/2023)?
I'm working on steel, an embedded scheme like programming language. I have lofty goals of eventually adding a JIT and making it viable as a standalone language, but for now its just about as fast as python, and makes for fairly pleasant embedded scripting. Recently added modules and dylibs, and am working on getting documentation into a better place so that adding more libraries becomes easier. I've written a functioning slack bot in it, which is pretty fun, eventually want to make a discord bot as well out of it just to stress test it a bit
- Guile Steel: a proposal for a systems Lisp
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?
freya - Cross-platform GUI library for 🦀 Rust powered by 🧬 Dioxus and 🎨 Skia.
vulkano - Safe and rich Rust wrapper around the Vulkan API
astro-float - Arbitrary precision floating point numbers library
tauri - Build smaller, faster, and more secure desktop applications with a web frontend.
schemetran
glow - GL on Whatever: a set of bindings to run GL anywhere and avoid target-specific code
rust-s3-async-ffi - Asynchronous streaming of AWS S3 objects in C and C++ powered by rust-s3
rust-gpu - 🐉 Making Rust a first-class language and ecosystem for GPU shaders 🚧
mdbook-pdf-headless_chrome - A forked version from headless_chrome used by mdbook-pdf for the latest version and expanding some response timeout to 300 seconds.
bevy - A refreshingly simple data-driven game engine built in Rust
tesseract-wasm - JS/WebAssembly build of the Tesseract OCR engine for use in browsers and Node
bgfx - Cross-platform, graphics API agnostic, "Bring Your Own Engine/Framework" style rendering library.