Very nice article. One thing you got wrong though is concurrency and parallelism. What you describe as concurrent is really just a case of parallel processing. Even if two processes don't run in parallel on the hardware level, and instead there's a scheduler switching back and forth, they are still, conceptually speaking, running in parallel.
Concurrency is the property of your code to be able to run in any order (including in parallel) and still working the same in all cases.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Very nice article. One thing you got wrong though is concurrency and parallelism. What you describe as concurrent is really just a case of parallel processing. Even if two processes don't run in parallel on the hardware level, and instead there's a scheduler switching back and forth, they are still, conceptually speaking, running in parallel.
Concurrency is the property of your code to be able to run in any order (including in parallel) and still working the same in all cases.