You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm new to rust, and started learning wpgu two days ago.
I was irritated to find that this tutorial recommended by wgpu was not even compiling, and the new API is so complex and unstable that I couldn't use it.
Only after one day of trying different things, I found out that this tutorial series had a github repo, and the code in the repo, was working correctly.
I see three critical reason that caused this confusion:
The article contains bugs, and even the first tutorial doesn't compile. This will prevent first time visitors from continuing the series.
The over-dependence on the "web" aspect of wgpu is not useful for me. I want to develop a desktop application, and millions of other developers would want to do the same. Web dev is not a priority for us. Perhaps it would be better if the tutorial series was split into two parts. One for desktop development, and one for web development.
The article's UI design makes it difficult to find the link to this repo. As seen in this picture, the link to this repo is given at the bottom, in small text, and is almost invisible to a first time visitor. I did not notice it for one day. The source code should be linked at the top banner, or spread out multiple times throughout the article. The link to this repo should be included at the top of the left pane. Github icons should be used at the top of the repo (or anywhere you deem useful) to link to this repo.
Hello, I'm enjoying reading learn-wgpu.
As a result of changes made in rust-windowing/winit#3056, the following adjustments are necessary:
control_flow = ControlFlow::Exit
withcontrol_flow.exit()
.event_loop.run(move |event, _, control_flow| { ... })
toevent_loop.run(move |event, control_flow| { ... })
.The source code on github has been updated. However, it appears that the code on the article remains unchanged.
Readers who copy and paste this code will encounter compilation errors. This could discourage beginners from continuing with the article.
I can submit a pull request to address this issue.
The text was updated successfully, but these errors were encountered: