Hacker News new | past | comments | ask | show | jobs | submit login

> Isn't "generating binaries" just as bad for other interpreted (interpeted-ish) languages?

I think this is the case for at least the most popular JIT'd languages: Java, C#, JS, and PHP. Also for the most popular interpreted languages: Python, Ruby and also PHP. I don't know about Visual Basic and R though.

I know that an exception is Dart, that combines a JIT and an AOT. I think EmacsLisp can now be also compiled, but I don't know if it works with all the code and is just free performance, or something more limited.

Edit: as pointed at by pjmlp, Java and C# already combine an AOT and a JIT. What I meant by the comment on Dart is that it can either be run with a VM or compiled to produce binaries.




Java and C# also have combined JIT and AOT since they exist, .NET moreso.

Other examples are Lisp and Scheme variants, Eiffel, OCaml, Haskell, Prolog.


The main SDKs and programming paradigms for Java and C# both don't mesh well with AOT, though. Reflection, heavy reflection based frameworks.

Not that many places use Java/C# AOT compilation, except for games/iOS apps.

Almost every place I've seen using Java/C# was using JIT.


Android uses a mix of JIT/AOT, just as most Java embedded development.

As for not everything being supported, well that is no different from having C++ code with RTTI and exceptions disabled, or being forced into a specific linking model due to possible problems with a third party dependency.


and that is why they failed to provide proper toolkits for android smartwatch and were forced to call samsung for help


Better watch the Wear talks, the only thing they are getting from Samsung is the Faces designer and the commitement to drop Tizen for Wear.

Is is still plain old Java/Kotlin/C++ as usual.

Press should be better informed, but that is asking too much in modern times.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: