Easier onboarding and environment setup

[viridia]

Lately there has been a realization that lots of new users are learning Rust specifically so that they can write games in Bevy. This demographic fact should be reflected in our tutorial content: we need to double down on the amount of hand-holding we do, particularly in the environment setup portion of the tutorial.

The old tutorial has some platform-specific advice that is absent from the new tutorial:

https://bevy.org/learn/quick-start/getting-started/setup/

However, even this material is rather thin, and a bit confusing. For example, should new users try to develop under WSL or not? Why does it advise installing MSVC and CMake? What do those things have to do with Rust?

Perhaps we need a "What you'll need" section?

[alice-i-cecile]

We should completely cut the docker image setup: this adds a lot of maintenance and complexity and risks derailing users who think it's required.

[viridia]

@MIennaco

[viridia]

Thinking about this some more. It seems that we have a couple of competing goals:

• To give the reader early gratification and build confidence by showing an actual game running on their computer.
• To quickly set the reader up in a working development environment where they can be productive.

The reason that these two goals are in tension is because, depending on what platform they are targeting, the best/easiest development environment may not be the same as the best/easiest environment for running a demo.

If it were me, the way I would approach this is to be up front about target platform:

---

Bevy's support for cross-platform development is remarkably good: you can program a game that will run either in the browser (via WASM) or as a native app without too much difficulty. However, there are a number of advanced capabilities of Bevy that are simply not available in browser environments. If you want to make use of advanced rendering techniques, or push the envelope of visual fidelity, then you probably should decide up front what platforms you want to run your game on, before you start writing too much code. During development, you will also likely want to test your game in an environment that resembles the target platform (also known as "platform-native development"). This early decision will affect how your development workspace is set up.

(And then we go on to offer the user choice of different environment setups).