From humble beginnings at an MSP, I've adventured through life as a sysadmin, into an engineer, and finally landed as a developer focused on fixing problems with automation.
I would also suggest maybe an edit to clarify your thoughts on the Threading part, Lane.
Might confuse people. Instead of threading, maybe use "concurrency". Instead of "multiple cores", maybe use "handling multiple jobs/tasks". This would make it more generalistic (if that word even exists).
Threading will handle jobs concurrently (quickly switching between one and another, when it makes sense - e.g. IO-bound tasks).
But threads won't help with parallelization (performing multiple tasks simultaneously). In this case, we really need multiple processors, as you mentioned.
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.
I would also suggest maybe an edit to clarify your thoughts on the Threading part, Lane.
Might confuse people. Instead of threading, maybe use "concurrency". Instead of "multiple cores", maybe use "handling multiple jobs/tasks". This would make it more generalistic (if that word even exists).
Threading will handle jobs concurrently (quickly switching between one and another, when it makes sense - e.g. IO-bound tasks).
But threads won't help with parallelization (performing multiple tasks simultaneously). In this case, we really need multiple processors, as you mentioned.