3 ms·

That depends on if developers can be convinced to actually use multiple threads...

• mikewarot 6y ago
  You seem to assume there is a choice to be had, but the lawys of physics say otherwise The single thread Von Neuman model is almost out of steam. The costs to push this model 2x faster are likely to break Intel. Concurrent programming, like it or not, is the future.
• pmontra 6y ago
  We already did for a long time. In my business, web applications, that is mostly server side and it came as either running the app in multiple processes (Rails, Django) or with a runtime that natively use all cores (BEAM / Elixir). The front end is mostly single threaded (JavaScript) but browsers can use multiple threads to speed up the UI and we can also use web workers to do some real multithreading in JavaScript. Maybe some frontend framework uses them to speedup managing its DOM model. I hope I gave the idea, the terms are probably all wrong, I'm definitely more about the backend.
• mywittyname 6y ago
  Threading is very widely adopted today. Most programs that you use everyday will spawn hundreds or thousands of threads. Several languages today have features to manage thread creation, pooling, and task execution with minimal developer involvement. Coroutine & promise libraries are widely available in many languages and developers are generally comfortable with using them anymore.
• totalZero 6y ago
  Maybe if you can find a PC or server that only runs one process at a time. We live in a multithreaded world nowadays due to multitasking and virtualization.