There are a class of text editor settings and conventions that our approach is to be more opinionated on. We’re not saying these options aren’t without merit - most of us have certainly had battles or discussions about them.

We’re designing Gomix with an assumption that if people aren’t confronted with low level choices like this. Ideally, this approach will have a couple benefits to their life:

they’ll instead focus on issues around their actual code, or on the problem they’re trying to solve

we can help people avoid a deep, dark internet rabbit hole

no one should feel like they’re doing it wrong, or that they have to understand and make the “right” choice before coding

Since I’m interested in using Python with gomix I’d just like to add that it’s the default for Python to use four spaces, so I’m not sure how well this opinionated stance will hold outside of Javascript and maybe Ruby. It might just be me, but since proper Python code has four spaces I would probably still use those for Python code, even if it means double-tabbing in your editor. Especially if I’m creating a mix for educational purposes.

Someone copying over my example to a proper Python codebase would have to use four spaces anyway, to not go against the grain.

Therefore, if the spacing is fixed it should probably be configured on a per-language basis. Though you basically enter the same rabbit hole again.

I would like to throw out the suggestion to allow Glitch to support .editorconfig settings. That way every project can define how their code should appear. Default the project to 2 spaces and let authors change.