Re:If Java Is Dying, It Sure Looks Awfully Healthy
by nilliams on Thursday October 10, 2013 @07:41AM
(#6526865)
>> JS is pretty slow (It uses an interpreter!) The notion of using it on the backend is debatable.
It is pretty fast. It has a world class VM with an optimising JIT compiler. V8 is considerably faster than many other interpreted language, Ruby, Python etc. It's being used on the backend by many smart companies.
>> As for the hardware thing [...] It just a way to let web devs do something on the hardware without bothering to learn an actual low level language.
I know C. I use it when necessary but I'd rather write JS. Apparently so would plenty of other people. It's not about laziness.
Re:If Java Is Dying, It Sure Looks Awfully Healthy
by cmircea on Thursday October 10, 2013 @07:46AM
(#6526884)
Expect it doesn't use an interpreter these days, it is JIT compiled (a la V8). It's quite fast now.
Re:If Java Is Dying, It Sure Looks Awfully Healthy
by CmonDev on Thursday October 10, 2013 @12:41PM
(#6528627)
Is it still single-threaded only using one CPU core?
Re:If Java Is Dying, It Sure Looks Awfully Healthy
by olavgg on Thursday October 10, 2013 @05:23PM
(#6530134)
Well almost, you can use web workers and create "tasks" that will use more cpu cores.
https://developer.mozilla.org/en-US/docs/Web/Guide/Performan...
>It has built-in interpreters (read "Browsers") on every computer.
JS is pretty slow (It uses an interpreter!). The notion of using it on the backend is debatable. "A lot of people are putting a lot of effort in to it" isn't a valid argument. u said it yourself: "people are told to/forced to use it"
As for the hardware thing, didn't you read the HN discussion about that? no body thinks that's a good idea. It just a way to let web devs do something on the hardware without bothering to learn an actual low level language.