One of my old pet peeves that I wish I had time to pursue was to experiment with a language that tried to separate presentation from the semantic model - I know there has been other attempts. I wish that got more attention. It's a tremendously hard thing to get right without ending up hampering communication more than you enable it, but the need for high fidelity interchange of programs is one of the biggest barriers to more rapidly iterating on improvements to the presentation of code.
Not identical of course, no, but same style would not be a problem. There's nothing in Haskells grammar that can't easily be adapted to a less terse style. It wouldn't solve all issus I have with Haskell by far, but it would go a long way to make me consider it readable.
> but you'll never see it until you get familiar with it.
I am familiar with it. It is how I came to detest the syntax.
How about you consider Mandarin instead.
However, we are comparing apples and oranges. Learning any language takes years, Mandarin a few more. The syntax of a programming language takes a few days at worst.
When someone invents a programming language where each of 30,000 library methods is a unique character that must be memorized separately, I'll be prepared to grant your point.