Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • 3
    Interpreted Go is a thing. There is also this one and this one. Commented Jan 19, 2023 at 16:12
  • And it is not so fast. Try to compile Kubernetes or something big. Fast is illusion. Commented Jan 19, 2023 at 19:28
  • 4
    @akostadinov, I interpreted OP's "waiting for compilation" complaint as "I just spent ten seconds making a one-line source code change, and now I'm waiting ten minutes on a build", which derails one's train of thought in the middle of an edit-debug cycle. Clearly a million new source lines will take a while for any technology to process, and two million is likely to take twice as long. I didn't see OP's question as being about lazy interpretation, where we win by deliberately ignoring a large number of source lines which some unit test never exercised. Commented Jan 19, 2023 at 20:05
  • Semantic differences between interpreted and compiled execution are a sign of a language deficit (it's too complicated to implement reliably). Considering undefined behaviour has its place when talking about a language that has it, but it's such a weird and dysfunctional misfeature that one shouldn't consider it when talking about in-principle questions like interpreted vs. compiled - it's a truly special case. Commented Jan 21, 2023 at 9:06
  • Semantic differences are either illegal, then either compiler or interpreter are wrong. Or they are covered by undefined / unspecified : implementation define behaviour in C or C++ and then it’s the programmers fault. Commented Jan 21, 2023 at 13:47