4 ms·
With Bevy being in early development still, are you worried about frequent maintenance to fix breaking changes?
by mysterydip 3y ago
With Bevy being in early development still, are you worried about frequent maintenance to fix breaking changes?
- indigochill 3y agoI'd guess from "It is not a full-fledged, properly maintained thing" in the README, probably not.
- teh_cmc 3y agoAs mentioned in the README, Revy is not meant to be a polished / properly maintained project -- it's just a proof-of-concept. I've talked more about how and why it came to exist in the first place in this thread [1], if you're interested. That being said, I do intend to publish updates when new versions of either Rerun or Bevy land; if only to experiment with new APIs as they come online. Now, to answer your question, I've been using Bevy since the 0.1 release and, in my experience, keeping up with the changes upstream has always been pretty painless. Their organization nand release process is top-notch, with some of the most high quality changelogs and migration guides I've ever seen in any project, and releases are rare enough (~about once a quarter) to just not be an issue. The community maintains compatibility matrices such as this one [2], and things generally just work :tm:. [1] https://www.reddit.com/r/rust/comments/1b6bqv1/revy_proofofconcept_timetravel_debugger_for_bevy/ktb4ei2/ https://www.reddit.com/r/rust/comments/1b6bqv1/revy_proofofc... [2] https://github.com/rerun-io/revy?tab=readme-ov-file#compatibility https://github.com/rerun-io/revy?tab=readme-ov-file#compatib...