我相信有很多原因，但我能想到的两个原因是

汇编代码肯定更难读(我肯定编写它也更耗时) 当您有一个庞大的开发团队在开发一个产品时，将代码划分为逻辑块并通过接口进行保护是很有帮助的。

我用汇编编程已经有一个月了。我经常用C写一段代码，然后把它编译成汇编来帮助我。也许我没有充分利用C编译器的优化功能，但似乎我的C asm源包含不必要的操作。所以我开始看到，一个好的C编译器胜过一个好的汇编编码器的说法并不总是正确的。

Anyways, my assembly programs are so fast. And the more I use assembly the less time it takes me to write out my code because it's really not that hard. Also the comment about assembly having poor legibility is not true. If you label your programs correctly and make comments when there is additional elaboration needed you should be all set. In fact in ways assembly is more clear to the programmer because they are seeing what is happening at the level of the processor. I don't know about other programmers but for me I like knowing what's happening, rather than things being in a sort of black box.

With that said the real advantage of compilers is that a compiler can understand patterns and relationships and then automatically code them in the appropriate locations in the source. One popular example are virtual functions in C++ which requires the compiler to optimally map function pointers. However a compiler is limited to doing what the maker of the compiler allows the compiler to do. This leads to programmers sometimes having to resort to doing bizarre things with their code , adding coding time, when they could have been done trivially with assembly.

Personally I think the marketplace heavily supports high level languages. If assembly language was the only language in existence today then their would be about 70% less people programming and who knows where our world would be, probably back in the 90's. Higher level languages appeal to a broader range of people. This allows a higher supply of programmers to build the needed infrastructure of our world. Developing nations like China and India benefit heavily from languages like Java. These countries will fast develop their IT infrastructure and people will become more interconnected. So my point is that high level languages are popular not because they produce superior code but because they help to meet demand in the world's marketplaces.

我“过去”写了很多汇编程序，我可以向你保证，当我用高级语言写程序时，我的效率要高得多。

我已经为6502、Z80、6809和8086芯片编写了大量的汇编程序。当C编译器在我所处理的平台上可用时，我就停止了这样做，并且立即提高了至少10倍的生产力。大多数优秀的程序员使用他们所使用的工具是出于合理的原因。

我只能回答为什么我个人不经常用汇编编写程序，主要原因是这样做比较乏味。此外，我认为在没有立即注意到的情况下，更容易把事情搞砸。例如，你可能在一个例程中改变了使用寄存器的方式，但在另一个地方却忘记了这一点。它会很好地组装起来，直到很久以后你才会注意到。

也就是说，我确实认为组装仍然有有效的用途。例如，我有许多非常优化的汇编例程来处理大量数据，使用SIMD并遵循偏执的“每一个比特都是神圣的”[引用V.Stob]方法。(但请注意，简单的程序集实现通常比编译器为您生成的要糟糕得多。)

随着汇编变得越来越不常见，出现了一个恶性循环:随着高级语言的成熟，汇编语言指令集的构建越来越少地是为了方便程序员，而更多地是为了方便编译器。

So now, realistically, it may be very hard to make the right decisions on, say, which registers you should use or which instructions are slightly more efficient. Compilers can use heuristics to figure out which tradeoffs are likely to have the best payoff. We can probably think through smaller problems and find local optimizations that might beat our now pretty sophisticated compilers, but odds are that in the average case, a good compiler will do a better job on the first try than a good programmer probably will. Eventually, like John Henry, we might beat the machine, but we might seriously burn ourselves out getting there.

Our problems are also now quite different. In 1986 I was trying to figure out how to get a little more speed out of small programs that involved putting a few hundred pixels on the screen; I wanted the animation to be less jerky. A fair case for assembly language. Now I'm trying to figure out how to represent abstractions around contract language and servicer policy for mortgages, and I'd rather read something that looks close to the language that the business folks speak. Unlike LISP macros, Assembly macros don't enforce much in the way of rules, so even though you might be able to get something reasonably close to a DSL in a good assembler, it'll be prone to all sorts of quirks that won't cause me problems if I wrote the same code in Ruby, Boo, Lisp, C# or even F#.

如果您的问题很容易用高效的汇编语言来表达，那么您的能力就更强了。