If Unity was high quality, the workflow would be something like this.
- Open the Editor
- Make games
Unity is however not, so the workflow is something like this:
- Open the Editor
- Receive random errors on the console with literally no additional information as to why they happened or how they can be fixed
Ah yes, {}, thank you Unity I know everything now! (bonus points for the asset pipeline choices being one of deprecated or experimental) - Clear these errors because Unity has trained you to pay no attention to them and it’s not like you have the faintest idea where they’re coming from or if they’re caused or fixable by you
- Attempt to make games
Obviously I’m not asking for these errors to be silenced, that would just sweep the problem under the rug and that rug is pretty dome-shaped already. But I wouldn’t mind seeing more information about errors than an extremely generic C++ line working with iterators, or {}.
