I find C/C++, et al curly brace syntax and semi colon at end of line, maybe; syntax absolutely abhorrent. Erlang reads like a sentence commas, and period at end. There's very little syntax and it makes sense. The problem it is different than what 90% people learned programming on (curly brace languages).
But the hard part of Erlang is OTP / understanding the concepts or rather unlearning the concepts from other programming paradigms.
i spent a couple of memorable weeks a few decades ago between jobs reading up on erlang, including joe armstrong's (RIP) wonderful phd thesis. when i started, erlang looked "strange" (i hadn't done much prolog in uni). but after being immersed in erlang for a few weeks, when i returned to look at some C/C++ code, they looked positively hideous compared to erlang's higher level functional, and prolog inspired pattern matching syntax.
It does look pretty weird if you have only ever worked in an imperative language.
If one can get past the initial impression though, they'll find it's actually a very simple, nice language. Much simpler than Scala/C++ and probably even Java these days. Also simpler than other functional languages like Haskell. I picked it up in about 1-2 weeks. There's very few gotchas in the language or hidden complexity. It flows well.
I'll also add the language suits the usage pattern. Pattern matching works very well with the gen_server approach. And the binary syntax is so nice if you need to deal with over the wire protocols, as is common in distributed systems.
You're preaching to the choir. I've been singing the praises of Erlang for about 15 years now - since I discovered it via a competitor's open source project.
I like it. It took a bit of getting used to ("bit" here used to mean "pretty minimal amount"). I didn't find it to be any sort of hurdle, and Erlang meshes quite well with how I think about programming. It's my favorite language of any that I've used.