2 ms·
In the end, it is all machine code. All that recursion, lazy evaluation, monads, lambdas, virtual methods and coroutines. In the end, they are all stack manipu
by GuB-42 7y ago
In the end, it is all machine code.
All that recursion, lazy evaluation, monads, lambdas, virtual methods and coroutines. In the end, they are all stack manipulation and jump instructions. High level languages are just a more convenient way of writing assembly.
I like to take that approach when comparing languages. What a program might do in term of machine instructions, and see how I can make another language output similar instructions. The one that can do it the more naturally wins.
- coldtea 7y ago>In the end, it is all machine code. All that recursion, lazy evaluation, monads, lambdas, virtual methods and coroutines. In the end, they are all stack manipulation and jump instructions. High level languages are just a more convenient way of writing assembly. Well, in the end the universe dies in the heat death stage, and nothing matters. But we're not "in the end", so this final analysis "it's all machine code anyway" is reductionistic. It might be all machine code, but the abstraction at which we think and program matters, for the correctness, speed of writing, speed of understanding it later, and performance of the deliverable...
- grugagag 7y agoLets extend this analogy to books: all books are just letters and words writen on a page. And some pictures too. It doesn’t matter how a book is written as long as it produces letters, words and paragraphs and pictures. It doesn’t sound right, does it?
- nradov 7y agoThat's not a fair extension of the analogy. An equivalent analogy would be that you can use any text editor or word processor to write a book.