3 ms·
It's OK, the parent will be paying the price when they're still writing native x86 code in 20 years time.
by shawnz 8y ago
It's OK, the parent will be paying the price when they're still writing native x86 code in 20 years time.
- pjc50 8y agoshrug Nothing wrong with native code, and sometimes nothing else will get the job done. Besides, my retirement plan is to be the dinosaur brought out to fix all those 32-bit-time bugs in 2038.
- dekhn 8y agomost of my code is in Python (there are Qt bindings). That said, I'm interested in webassembly, and can also write javascript. I just don't think that browsers or javascript-based apps present a preferred alternative to native apps developed by teams who consider long-term API stability and getting the right regulatory boxes checked.
- ahartmetz 8y agoThe free performance lunch from ever faster hardware is over and that is saving native code for applications. The few percent hardware improvement each year is easily eaten by growing requirements.
- pkaye 8y agoLow level knowledge is useful at times. I rewrote a small amount of code on a project at work using SIMD instruction to reduce execution time by 60%. This is on something executes in tens of minutes so the time savings are quite noticeable.