This does really sound unusual. For me, the ratio of reading to writing is about 4:1. Are you sure you are not writing too much new code, because you didn't invest the time to properly understand the existing one? When…
Using the heap layout, you can sometimes even eliminate branch misspredictions and subsequent (expensive) pipeline flushes. The basic idea is to allow your compiler to use predicated instructions. Do do this, you have…
This sounds somewhat similar to (software) transactional memory.
I guess that the kernel cannot know that the application (in your case scp) will not try to touch the data ever again. The current default behavior, which you call crazy, does however favor programs which do actually…
Is this a way of saying one should always live on the edge of incompetence? Edit: I ask this, because I have difficulties applying your ideas on fields where I don't have any good teachers around (e.g., lets say I want…
This does really sound unusual. For me, the ratio of reading to writing is about 4:1. Are you sure you are not writing too much new code, because you didn't invest the time to properly understand the existing one? When…
Using the heap layout, you can sometimes even eliminate branch misspredictions and subsequent (expensive) pipeline flushes. The basic idea is to allow your compiler to use predicated instructions. Do do this, you have…
This sounds somewhat similar to (software) transactional memory.
I guess that the kernel cannot know that the application (in your case scp) will not try to touch the data ever again. The current default behavior, which you call crazy, does however favor programs which do actually…
Is this a way of saying one should always live on the edge of incompetence? Edit: I ask this, because I have difficulties applying your ideas on fields where I don't have any good teachers around (e.g., lets say I want…