AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() ![]() ![]() I think only WebAssembly has a shot, in the sense that there's no replacing JS for the time being. (yes I know about gopherJS, dartto js and webassembly, but they are not there yet. Other examples of JITs: PyPy for Python, LuaJIT for Lua, CLR for all. One nice thing about compiling down to native code is that you can ship binaries without needing to deploy a runtime this is one of Go's strongest features, in my opinion! Like comment: Like comment: 16 likes Performance is a big factor when it comes to interpreted vs compiled - the rule of thumb is that compiled is faster than interpreted, but there are fancy interpreted systems which will generate faster code (I think some commercial Smalltalk implementations do this). A lot of interpreted languages - Python, Ruby, Lua - actually compile to bytecode and execute that when you run a script. ![]() Then you get into interesting territory with languages like Java, which are compiled to bytecode, and the bytecode is interpreted (and possibly just-in-time compiled) at runtime. Scheme and ML are other languages which have both interpreted and compiled implementations. At the risk of being pedantic, there's no reason you can't have both a compiled and interpreted implementation of a language - for example, Haskell has GHC, which compiles down to native code, and the lapsed Hugs implementation, which is an interpreted implementation of Haskell. ![]()
0 Comments
Read More
Leave a Reply. |