There's far too many typos for me to have any amount of confidence in the code itself.
Sorry, but I can't trust my business with people who cannot even be bothered to write proper English for their introduction.
Sorry, but I can't trust my business with people who cannot even be bothered to write proper English for their introduction.
I have had many bad experiences with incompetently-written libraries. A bad library can cost you days/weeks of productivity lost in fighting its idiosyncrasies and/or straight up bugs. A really-good indicator of the quality of a lib is the attention to detail in "minor" details like documentation.
Obviously if the docs are littered with typos they will be less useful, but there's another layer to it. English isn't much of a problem for sufficiently-skilled programmers, even if they are of foreign descent.
So, when I see a lib written in broken english like this, I make my conclusions about the attentiveness and skill of whoever wrote it. I'm not saying it's always right, but in the long-term this has saved me a lot of headaches.
Sorry for raining on everyone's parade, though. This really isn't the proper way to start a conversation.
Strongly disagree. Flexibility in a language leads to flexibility of the mind. The English language's incredible variety, massive vocabulary, and huge range of idioms is of great benefit to those that speak it (while also making it difficult to learn). Subtlety in a language is a virtue, not a vice.
For maximum linguistic impact, people should also learn languages that read right-to-left.
If you really want a more-or-less linguistically "simple" language, Spanish is a decent choice (and is also the second most widely used language, after Mandarin).
Indeed, but I think we're talking about language in two different ways: all your points are completely correct, but mainly of value to those who understand the language fairly well; my points were implicitly from the POV of a foreign learner trying to pick the language up.
As a native Anglophone, I love our freaky language, orthography and all. However, I try to keep reminding myself how horrible it is for new learners.
It's a pitch from dedicated folks. Treat it as such?
On topic: Looks like an interesting collection of ideas, and as I've never heard of hexagonal architecture I'll definitely have to look into this. Always researching better ways of doing structure.
As someone else said, he was being a dick about it, and the implication that English skills are somehow related to coding skills is obviously nonsense. (And he still managed to make mistakes of his own while criticising your language)
To be a bit more constructive, here's a slightly rewritten introductory paragraph that I believe reads more natural (though English isn't my native language either):
"There's an idea we have been working on for more than one year so far. As backend developers we were thrown into the mysterious world of frontend (client-side) apps without any good pattern for creating Single Page Apps. So we (GameBoxed + Arkency) invented one - hexagonal.js."
But the most frequently occurring English mistake on your page appears to be missing "the"'s. This error is very common with speakers of slavic languages. Based on the admittedly limited example of your English on the linked page, I think one of the biggest improvements you can get with relatively little effort would be if you spend some time reading up on how to identify where/how to use "the".