Post #2716234
2026-04-25 00:29 UTC
@MartyFouts@mastodon.online To clarify - I don't mean you should *actually* know what the compiler is going to do. That is hard, and most compilers don't actually go through those intermediate stages.
I mean that when you're writing a piece of code in a language, you should be able to *in theory* write the same code using the next simpler language. Now, you're choosing not to do that for efficiency - but you COULD. And knowing what that version would look like will inform how you write the real code.
Replies (1)
-
@MartyFouts@mastodon.online 2026-04-25 00:58
@TomF@mastodon.gamedev.place Yes, I got that. I don’t agree. At least not for most programmers, most of the time. understanding the semantics of the language at the level of abstraction of the language and its model has been enough for most programmers and problems for at least 50 years. There are exceptions, of course. But what used to be a requirement for everyone when I started 50 years ago is now the exception rather than the rule.