Personally, I’m a fan of just requiring whitespace around operators. I find expressions hard to read otherwise, so think it’s bad practice, but I also find precedence rules awkward in all but the simplest expressions, so like to use parentheses a lot, which mean I don’t necessarily need whitespace-based grouping to make expressions clearer, eg: “a/b + c” I would just write as “(a / b) + c” anyway. I’ve been programming for 20 years so it’s not just unfamiliarity, I guess I just found these things cause me speed bumps needlessly.

Refusing to allow symbols in identifiers might make some things easier to read, but is annoying as hell if you're touching anything scientific.

If you have something clear you break tokens on, like whitespace (except within quotes), then you should have no problems allowing arbitrary symbols inside an identifier.

    x = 0
    y = 1
    x+y = 0
    z = x+y

What is z?

x+y = 0 (with that specific syntax) will error in pretty much every language.

So we will refuse to allow symbols in identifiers after all?

The only programming languages where arithmetic symbols are allowed identifiers have an identifier sigil (ala Perl, PHP), require whitespace around arithmetic (some teaching languages), or don't have conventional arithmetic syntax (e.g. Forth, Lisp).

Please read the comment I originally answered to.

Or you're Lisp

Or The Language Formerly Known as Perl6 [1], where it won't cause much friction as variable names ordinarily start with a sigil.

[1] https://docs.raku.org/syntax/identifiers#Ordinary_identifier...

Or you require whitespace in arithmetic.

Or XPath