I’m a developer with nearly 8+ years of experience mostly in the JavaScript and Java/C# space with a couple of years of experience in Go. I’ve dabbled in functional languages like F# and Haskell. I found the article difficult to understand and the code examples were off putting to me, so I agree with your assessment.
That being said, I may not be the article’s target audience.
I’m not at all saying they should be an expert after a week. But learning those things is part of being a software developer/programmer and I don’t think, “Well the language sucks” is a valid argument.
I do agree it’s a complaint about the language. However, I think it does ultimately fall on the developer to know how to work with the language including the bad/ugly/awful parts. I also think not polluting the global scope is a pretty foundational thing to know or be aware of. It’s really easy to shoot yourself in the foot or have naming collisions/overwrites happen if you aren’t careful.
Another example would be memory allocation/freeing in a non-GC language. Sure, it’s a pain that I have to deal with it, but it’s still on me to make sure my application works in the language I’ve chosen and doesn’t leak memory all over the place.
That being said, I may not be the article’s target audience.