6 ms·
> - compiles to a binary rather than running on a VM; To me, this is one the many reasons why Go will fail.
by laureny 14y ago
> - compiles to a binary rather than running on a VM;
To me, this is one the many reasons why Go will fail.
- kgabis 14y agoCould you elaborate on this?
- coldtea 14y agoI'm not the parent, but one reason could be that the feature is more about collaboration of different languages for different purposes on a shared ecosystem (JVM, CLR, JS as bytecode, etc). Which Go doesn't play well with.
- laureny 14y agoThese days, there are more advantages than drawbacks to running in a VM. The performance advantage of native over byte code has shrunk considerably to the point of being only relevant for a tiny portion of applications (e.g. games). On the other hand, there are considerable advantages to JVM's, as Java and the generation of language it kickstarted has shown.
- kgabis 14y agoHaving a VM also adds a whole lot of security concerns and in case of jvm - dependency on sun/oracle. VMs are not the only way to kickstart language generation, there are other options, such as llvm (yeah, that name is confusing in this context).
- pjmlp 14y agoVM is just a conceptual model. Most languages that usually have a VM, also tend to have native code compilers available, it is just that most HN folks tend to be unaware of them.