3 ms·
There always are situations where you need to squeeze out performance and there always will be. A. as mentioned above there are devices that have very limited
by hristov 17y ago
There always are situations where you need to squeeze out performance and there always will be.
A. as mentioned above there are devices that have very limited performance.
B. There is always software or parts of software where every last drop of performance needs to be squeezed out, regardless of how fast your computer is. For example, the scheduler for your OS. Or doing certain graphics calculations. If you have to repeat a certain type of code for every pixel over a million pixels, you do not want to be running a VM.
So this argument is a dead end. There will always be certain type of tasks where it pays to be as fast as possible. Even as computers get more powerful, software gets more complex and more abstracted which means there is always something on the bottom of all the abstractions that needs to run super fast and if it doesn't it will slow everything else to a crawl.
- stcredzero 17y agoThere always are situations where you need to squeeze out performance and there always will be...So this argument is a dead end. What argument do you think is going on here? My position is "all system programming doesn't have to be in C." It's not "C is dead" or any such nonsense. The "argument" is a dead end because it exists in the imaginations of other posters. My position isn't such a straw man!