Compiled and Interpreted Languages: Two Ways of Saying Tomato

I have no idea why this is getting re-posted in such short order:

https://news.ycombinator.com/item?id=34330966

https://news.ycombinator.com/item?id=34336223

Anyhoo here are two related discussions:

* https://www.reddit.com/r/ProgrammingLanguages/comments/108gs...

* https://lobste.rs/s/evkxyk/compiled_interpreted_languages_tw...

Personally, I think there is and should be such a distinction, but it looks to me as though it was rather an intentional rather than an extensional one, like you can't tell when adding grain of sand adds up enough to call it a 'heap', or you can perfectly sit on a couch table and put your coffee cup on the bar stool. The latter turns the place-things-on-me thing into a piece of sitting furniture, and the sitting furniture acts as a table.

Once upon a time I was challenged to write some smallish piece of software in Java and I immediately got annoyed by that extra compilation step. I 'solved' that by putting compilation and execution into a single command line incantation.

Sure, if you look at it that way, there 'are no heaps', 'no chairs no tables', 'no compilation no interpretation just computation' but when you come back from the trip, a hammer's still a hammer and a screw won't nail it.