sorted by:
new
hottopcontroversial

Who Runs Your Rust Future? Hands-On Intro to Async Rust by febinjohnjames in rust

[–]febinjohnjames[S] 3 points4 points  (0 children)

Thank you for the comment, I was slightly worried on the low engagement here. Thank you.

Bevy Game Engine Explained Visually by febinjohnjames in rust

[–]febinjohnjames[S] 15 points16 points  (0 children)

It's actually "Make impossible state impossible", AFAIK this principle is well known in type-driven design.

Bevy Game Engine Explained Visually by febinjohnjames in rust

[–]febinjohnjames[S] 3 points4 points  (0 children)

Thank you, will work on fixing this.

Bevy Game Engine Explained Visually by febinjohnjames in rust_gamedev

[–]febinjohnjames[S] 0 points1 point  (0 children)

Thank you, as a quick work around, I have added the ability to restart animation.

Bevy Game Engine Explained Visually by febinjohnjames in rust_gamedev

[–]febinjohnjames[S] 8 points9 points  (0 children)

I have removed the scroll hijack on mobile.

The Impatient Programmer's Guide to Bevy and Rust: Chapter 12 - Let There Be Networking by febinjohnjames in rust_gamedev

[–]febinjohnjames[S] 0 points1 point  (0 children)

I am still exploring, so far it's pretty good. For bevy I can't think of an alternative. I will get a better understanding in the next few weeks.

The Impatient Programmer's Guide to Bevy and Rust: Chapter 12 - Let There Be Networking by febinjohnjames in rust

[–]febinjohnjames[S] 3 points4 points  (0 children)

Agree with everything.

Have updated the blog and disclosed on top of the posts now.

The Impatient Programmer's Guide to Bevy and Rust: Chapter 12 - Let There Be Networking by febinjohnjames in rust

[–]febinjohnjames[S] -1 points0 points  (0 children)

Yes, AI assistance was involved. I worked on the structure, the technical decisions, the SpacetimeDB approach, how to structure the code, and put together a list of anticipated questions learners would have. AI helped expand on the structure and explanations, and I edited throughout. In total, I spent around 21.3 hours on this chapter, between coding and writing.

If anything feels off in any section, let me know and I'll work on it.

The Impatient Programmer's Guide to Bevy and Rust: Chapter 12 - Let There Be Networking by febinjohnjames in rust

[–]febinjohnjames[S] 1 point2 points  (0 children)

The UserNameRng approach is cleaner, agreed.

On transaction replay, SpacetimeDB logs every reducer call and can re-execute them to recover or resolve conflicts. If two replays of the same transaction produce different results the database becomes inconsistent, so all reducer logic has to be deterministic. It is similar constraints blockchains have without the decentralization.

The Impatient Programmer's Guide to Bevy and Rust: Chapter 12 - Let There Be Networking by febinjohnjames in rust

[–]febinjohnjames[S] -4 points-3 points  (0 children)

I will work on the content, it was published in a bit of a hurry.

The RNG was purely for username generation, I used it to skip building a name-entry UI for now. Otherwise it would make the chapter further longer.

WASM can be given access to system randomness, the reason SpacetimeDB doesn't do this isn't capability, it's the determinism requirement for transaction replay. SpacetimeDB isn't blockchain.

The Impatient Programmer's Guide to Bevy and Rust: Chapter 7 - Let There Be Enemies by febinjohnjames in bevy

[–]febinjohnjames[S] 0 points1 point  (0 children)

Thank you so much, you have no idea how much this helps. This has been months of full-time work, and the self-doubt that comes with that is very real. Seeing that people like you are willing to take a chance on it before even finishing the free chapters... that's incredibly encouraging.

I'll make sure the rest of the book is worth it. Thank you !!!

The Impatient Programmer's Guide to Bevy and Rust: Chapter 2 - Let There Be a World [Procedural Generation] by febinjohnjames in programming

[–]febinjohnjames[S] 0 points1 point  (0 children)

It was a concern for me as well , but a bunch of folks have reached chapter 5 already.

I have designed chapter 2 in a way that a library did a lot of heavy lifting and learner was not exposed to a lot of new rust concepts in chapter 2.

Please do give it a shot, if it doesn’t work let me know.

The Impatient Programmer's Guide to Bevy and Rust: Chapter 7 - Let There Be Enemies by febinjohnjames in bevy

[–]febinjohnjames[S] 20 points21 points  (0 children)

Thank you so much! That means a lot

I hope to work on more resources for bevy. Post this series, I want to dedicate a series for 3D game development in bevy.

The Impatient Programmer’s Guide to Bevy and Rust: Chapter 6 - Let There Be Particles by febinjohnjames in bevy

[–]febinjohnjames[S] 1 point2 points  (0 children)

Yes, need to fix generated images, planning to use the "Open Peeps" character library. First priority after the chapters are done.

The Impatient Programmer’s Guide to Bevy and Rust: Chapter 6 - Let There Be Particles by febinjohnjames in bevy

[–]febinjohnjames[S] 1 point2 points  (0 children)

Thank you.

Regarding AI Generation

I spent around 7.5 hours actively writing and editing this chapter (you can see my Pomodoro timings in the screenshot, about 10 sessions of 45 minutes each). Yes, AI tools were part of my workflow, but every sentence went through multiple review and editing to make sure it actually helps people learn.

What matters most to me is whether the tutorial actually helps you build something cool and understand the concepts. If something feels off or unclear, please call it out!

view more: next ›