3 ms·
That was quite an arrogant post that really seemed to miss the forest for the trees. Sure, perhaps you can build a faster prime number generator in assembly, bu
by SoftwareMaven 15y ago
That was quite an arrogant post that really seemed to miss the forest for the trees. Sure, perhaps you can build a faster prime number generator in assembly, but you'll never build a better application in assembly (where better is defined as feature rich, secure, etc), and that's what the job is about.
- archangel_one 15y agoPerformance can also be a feature.
- SoftwareMaven 15y agoAbsolutely! But performance in most applications is not determined at the bit level. Most apps performance needs are met at the architectural level (prevent blocking on whatever). Fewer apps performance needs are met at the algorithmic level (O(log n) is much faster than O(n log n)). It is a rare app that finds it's performance requirements in the ops and bits (Highly math-centric apps. Others exist, I'm sure). I've generally found that's the order I go in meeting performance requirements. When I've failed to meet those requirements, I've generally worked backwards up the list, with each step getting more expensive in an exponential fashion.