Hacker News Reader

Comment by tomc1985 | Hacker News Reader

tomc1985

OH GOD NO

Adding ANOTHER interpreted language to the pile? Jeeze you guys are crazy. Just STFU and learn C/Go/Java

Does ANYONE in NodeJS world care about efficiency? Or does this "plebian" (ew! hacking is not plebian!) hackability trump all other concerns?

View on HN

Please don't.

https://news.ycombinator.com/newsguidelines.html

https://news.ycombinator.com/newswelcome.html

We detached this subthread from https://news.ycombinator.com/item?id=13940554 and marked it off-topic.

There might be an insult or two thrown around but detaching the thread removes necessary context. I do not think that this was the appropriate course of moderation.

It was uncivil, unsubstantive, dismissive of others' work, broke the HN guideline against using uppercase for emphasis, took the thread into a programming language flamewar... Please just don't post like that to HN.

I think the fact that you call java not-compiled, but python interpreted shows your misunderstanding in this area. Both run exactly the same way, they are compiled into an intermediate bytecode which is run in a "VM". The normal Java VM has a JIT, the normal python VM does not, but pypy does and achieves performance on par with some of your compiled languages, at the cost of reduced c compatibility.

I know C, Java, python, and a limited amount of javascript and go. I prefer writing python. And, for plugins, there are enormous downsides to using something that is compiled (C, go).

For me, a big irritation with Python - intermediate bytecode or not - is that foolish small mistakes in formatting, or missing symbols, etc. will only make themselves apparent when the interpreter (or bytecode interpreter) actually tries to run or use them. In some configurations, it can be preprocessed and checked, but the most typical and default use cases for Python do not promote this.

Honestly, this is not a problem in practice; if some application crashes due to a misspelled variable, then that very clearly indicates that testing coverage is lacking. IDEs also tend to indicate this, as do linters.

Though your

> the most typical and default use cases for Python do not promote this.

might be different from those I have encountered.

Uh, I lumped in Java with the compiled languages?

And yeah, thats right there's like 80 million Python variants, some of which are compiled.

that was a typo. "not-interpreted" was my intended statement.

And I'd love for you to show me a python variant that is compiled in the same way that C is compiled. The closest is nuitka, which...isn't.

cpython? I know the regular python-2.7 installer in debian does binary compilation, producing little *.pyc files for everything

They are binary files, but they aren't "compiled binaries in the same way that C is compiled", they are intermediate Python byte-code files and they still need the CPython runtime to interpret them.

As the other user mentioned, those are compiled in the same way java is compiled, but not in the same way that C is compiled. They still need an intermediate VM to run.

Reply on news.ycombinator.com