It’s cooking spray.

Look at the serving size.

Thats not what I’m talking about.

python is one of the few popular languages where presentation is semantic but I’m talking about separating semantics from presentation. you should be able to radically change how you see the code without actually changing the file.

I should be able to apply a personal style to the code and view it with small indentations, or large indentations, with line widths of 80char or 120char, function args within parentheses or not. I should even be able to localize it into another natural language, or even view and edit it as a flow chart instead of text, all without actually changing the underlying file that contains the semantics.

That’s way jargon is. If a field uses too much jargon, it raises the bar for entry unreasonably high. Instead of having a decent but imperfect understanding of something, you have no understanding.

Code semantic should be separate from code presentation.
In other words, tabs vs spaces is a stupid argument.

We’ve learned that separating semantics and presentation is good for the code we write but we’ve never bothered to apply it to languages. Everyone on the team should be able to apply their own formatting preferences without affecting the underlying file.