Re:JIT: So you want to be faster than an interpreter on mode...
by duped on Monday October 13, 2025 @08:40PM
(#45574944)
What advantage does JIT compilation have over Swift or Obj-C?
[ Parent
| on HN ]
Re:JIT: So you want to be faster than an interpreter on mode...
by saagarjha on Monday October 13, 2025 @08:54PM
(#45575026)
It speeds up interpreted languages.
Re:JIT: So you want to be faster than an interpreter on mode...
by Pulcinella on Monday October 13, 2025 @08:58PM
(#45575054)
And emulation.
Re:JIT: So you want to be faster than an interpreter on mode...
by saagarjha on Monday October 13, 2025 @09:01PM
(#45575076)
What is an architecture but a scripting language to interpret? ;)
Re:JIT: So you want to be faster than an interpreter on mode...
by duped on Tuesday October 14, 2025 @10:51AM
(#45580804)
I get that, but what interpreted language do you want to write iOS apps in when there's Swift and Obj-C right there, with bespoke support and tooling from Apple?
And if you care about performance, why aren't you writing that code in native to begin with?
Re:JIT: So you want to be faster than an interpreter on mode...
by saagarjha on Wednesday October 15, 2025 @03:42AM
(#45589253)
Why would you care about faster cars when planes exist?
Re:JIT: So you want to be faster than an interpreter on mode...
by ranger_danger on Friday October 17, 2025 @11:46PM
(#45624730)
Re:JIT: So you want to be faster than an interpreter on mode...
by ranger_danger on Friday October 17, 2025 @11:44PM
(#45624723)
...Javascript.
Re:JIT: So you want to be faster than an interpreter on mode...
by bencyoung on Tuesday October 14, 2025 @04:26AM
(#45577562)
JIT compilation can be faster for compiled languages too, as it allows data driven inlining and devirtualization, as well as "effective constant" propogation and runtime architecture feature detection
Re:JIT: So you want to be faster than an interpreter on mode...
by varjag on Tuesday October 14, 2025 @06:42AM
(#45578404)
It can be but it never is.
Re:JIT: So you want to be faster than an interpreter on mode...
by __s on Tuesday October 14, 2025 @07:46AM
(#45578872)
Especially after PGO (profiling guided optimization) gets most of the way there
Re:JIT: So you want to be faster than an interpreter on mode...
by ignoramous on Tuesday October 14, 2025 @07:26AM
(#45578706)
To re-optimize compiled code blocks isn't without effort. Google has publicly spoken about AutoFDO and Propeller [0], after Meta had open sourced BOLT [1] in 2021.
AutoFDO has since been ported to Android and adopted by Yandex [3].
[0] https://lwn.net/Articles/995397/
Re:JIT: So you want to be faster than an interpreter on mode...
by Rohansi on Tuesday October 14, 2025 @12:09PM
(#45581752)
But is that because of JIT compilation or other decisions for how the language should work (dynamic typing, GC, etc.)?
Re:JIT: So you want to be faster than an interpreter on mode...
by ranger_danger on Friday October 17, 2025 @11:35PM
(#45624690)
Hard disagree. Many newer game system emulators (32-bit and up) rely on JIT or "dynarecs" to get playable speeds, and they pretty much all use high performance compiled languages already. They often double the performance over their interpreter or more.
Re:JIT: So you want to be faster than an interpreter on mode...
by duped on Tuesday October 14, 2025 @10:50AM
(#45580785)
Is there a production JIT for a compiled language that is actually faster? I understand the theory, I don't think the practice backs it up.
Re:JIT: So you want to be faster than an interpreter on mode...
by fragmede on Tuesday October 14, 2025 @10:57AM
(#45580876)
Depends, what do you consider Java?
Re:JIT: So you want to be faster than an interpreter on mode...
by varjag on Tuesday October 14, 2025 @11:28AM
(#45581209)
Java is certainly not the fastest language out there.
Re:JIT: So you want to be faster than an interpreter on mode...
by pcwalton on Tuesday October 14, 2025 @02:27PM
(#45583199)
Sure, but the relevant comparison isn't between languages: it's between a state-of-the-art JIT implementation of one language and a likewise-state-of-the-art AOT implementation of the same language. Unfortunately there aren't many examples of this; most languages have a preferred implementation strategy that receives much more effort than the other one.