learn-wgpu VS veloren

Nice.

Speaking of Snake game, if you want to go even deeper, you can try to use the wgpu crate to combine Rust and WebGPU to write everything from scratch. Here is the tutorial:

https://sotrh.github.io/learn-wgpu/#what-is-wgpu

I once wrote a code editor with wgpu, from font rendering to char/line state management (very rough) for music live coding:

https://github.com/glicol/glicol-wgpu

It runs in browsers, even including Safari!

https://sotrh.github.io/learn-wgpu/ This is probably the best resource out there for learning wgpu specifically. If you're unfamiliar with graphics, the learnopengl one is good. If you've got experience though, jumping right into that one is a shout or looking at some vulkan ones as they're pretty similar in terms of architecture.

- https://sotrh.github.io/learn-wgpu

Most of The WGPU I learnt is from https://sotrh.github.io/learn-wgpu/ but it doesn't really talk about designing n stuff, I thought of checking out the source code for Bevy or even games like veloren. But well, their codebases are pretty big to get started in the first place.

So I was wondering if opting for option 1 would be better to begin with. OpenGL has a much bigger community and wgpu only has its documentation which I hear is not quite up there yet. There is this excellent tutorial for wgpu that I read through, but it seems like wgpu can be a lot more complicated than starting with OpenGL.

I started with wgpu tutorial (https://sotrh.github.io/learn-wgpu/) since I like the idea of portability and it's a Rust-first library, but it seems I'm missing some foundations of how CG works in general: the code is given, a little of explanation like it assumes I already know something, maybe I'm wrong, but I wish there was a longer explicit version.

If you haven't seen it: https://sotrh.github.io/learn-wgpu/ is a good introduction that will explain most of what you asked, then can refer to rend3d or bevys renderer to see how a render graph works.

I know that code.org's lessons have a "view the real code" box, helping to ease one into the "here's how to think about problems and structure, but here's the actual JavaScript that underpins it". If you haven't tried that, it may help

I also recently learned that Brilliant uses block-based lessons, too, so there's obviously some there-there

I would guess that a lot of the problem is one of actualization: how does one go from solving "someone else's problems" to one of realizing their own ideas. Based on what I've seen, I'd guess that a Minecraft mod port that maps blockly down into lua would go a long way toward "do some things that materialize change in an environment that is familiar." I haven't used Roblox, but I believe it's similar so if they have a programming language, same-same. I started to suggest using Valoren <https://gitlab.com/veloren/veloren#get-veloren> since it's actual FOSS and thus would be much, much easier to integrate into, but I haven't played it in order to know how much uncanny-valley it would have with any preexisting Minecraft experience

Games (Veloren, or check out this website for updates on other games being developed in Rust)

Firstly, it's open-source. That means that all code associated with the project is freely available (it's right here!) and you're welcome to download, modify, recompile, and make changes to it as you wish. In fact, there have already been a few forks of the project that added new items, abilities, bosses, and other such things. Veloren is also released under GPL v3, a license that pretty much ensures that the code will always be open-source, meaning that anybody can take the existing code and remix it, mod it, or otherwise build upon it.

I found this on the gitlab https://gitlab.com/veloren/veloren/-/issues/1755

sounds like a wayland issue, can you check our https://gitlab.com/veloren/veloren/-/issues list and if you dont find this error, you could help us by opening a bug and giving it a good description: Maybe there is even a workaround in our book:

Trying to replace C with something like Rust, is essentially saying that we should rewrite all kernels in Rust. C is the common language because it talks to the kernel, which talks to the hardware.

Forgetting how much would need to be replaced with objectively much slower code, Rust simply cannot do some things. You cannot always make absolute guarantees about memory safety for example when it comes to low-level programming. Sometimes to be fast, you have to make assumptions and take risks.

I am currently watching the Veloron game [1] as an example of how larger Rust projects may begin to look. I see something like this [2] and it doesn't look all dissimilar from C, just with a new syntax. Has writing this game eliminated all bugs? Nope [3]. Maybe there are less segfaults and bad memory management, but this was just one class of bugs.

[1] https://gitlab.com/veloren/veloren

[2] https://gitlab.com/veloren/veloren/-/blob/master/server/src/...

[3] https://gitlab.com/veloren/veloren/-/issues/?sort=closed_des...

Oh dang, looks like it's open source too. licensed under GPLv3 - https://gitlab.com/veloren/veloren

It's really amazing to see how Veloren has improved over the years. Makes me wonder what we'll see in the future. I was really surprised when I saw the train tracks merge request 😄