Write Future Work section for Bevy 0.17

[alice-i-cecile]

Probably going to be merged into the website repo, but this is easier to track for now.

Some ideas for what I want covered:

• BSN: obviously.
• Many-to-many relations (#20377): should be mergeable
• Resources-as-components (#19731): unblocked, valuable
• Materials overhaul: now unblocked, rendering is champing at the bit
• Asset preprocessing: 🥺
• Firewheel: very promising! Do we want to endorse it yet?
• More tilemap stuff: natural follow-up, but do we have folks ready to work on this?
• bevy_ui entity inspector (#20189): very hype
• Better assets in examples (#20660): long overdue
• Moar widgest: feathers isn't done yet!

What else do you have planned and want to highlight?

[JMS55]

Materials overhaul: now unblocked, rendering is champing at the bit

I wouldn't promise this 😅

[james7132]

IMO the Forte and tasks work might be interesting to a very selective subset of Rust programmers, but I'm not sure if that's ready for the limelight yet.

[ChiMuYuan]

About tilemap, there’s a PR bevyengine/bevy#20205 with a lot of updates, but it currently has conflicts. Also, many tilemap-related commits were submitted by @ConnerPetzold, so maybe he has plans for it.

[NthTensor]

IMO the Forte and tasks work might be interesting to a very selective subset of Rust programmers, but I'm not sure if that's ready for the limelight yet.

Agreed. I'd like to save this for the next release.

[alice-i-cecile]

bevyengine/bevy#20873 is a critical enough bug / architecture change that I'm interested in highlighting it early.