upvote

points

by pjmlp2 days ago |
comments
upvoteby creata2 days ago|
[-]
> we have so much better dynamic languages with advanced JIT implementations

What are some of these better languages that you're referring to? (The usual dynamic language JITs I hear people praise are LuaJIT and Chez. And V8. And the JVM?)

reply
upvoteby pjmlp2 days ago|
parent|
next
[-]
Smalltalk, Self, whose research lead to Hotspot and V8, Common Lisp.

And the usual, in Python everything is dynamic, well it is even more so in an image based live coding environment, where any break into the debugger, with code changes and resume execution can come back to a complete different world.

Additionally there are features like Smalltalk become: message, where two objects can change places everywhere they are used in the image, and current execution.

reply
upvoteby esafak2 days ago|
parent|
prev|
next
[-]
I'd suggest F#, Clojure, Elixir, Scala, and TS, if that counts.
reply
upvoteby kasajian20 hours ago|
parent|
[-]
Clojure could never really be a thing since it ignores the most important rule: fast startup. Because of this, and for no other reason, Clojure will always be an "also ran". It's not about competency of the people working on it. It's a solvable problem the community doesn't acknowledge exists, unless you press them on it, in which case they think "graal" and "babashka" is a valid response, and you're back to square 1.
reply
upvoteby __s1 days ago|
parent|
prev|
[-]
Even Ruby has JIT now
reply
upvoteby creata1 days ago|
parent|
[-]
True! But pjmlp was referring specifically to advanced JIT implementations, so I wondered which JITs he was referring to as advanced.
reply
upvoteby pjmlp1 days ago|
parent|
[-]
In Ruby's case that would be RubyMotion, TruffleRubby and JRuby.

That trace back to Apple's efforts with MacRuby, or Sun's (for a while Netbeans even had Ruby support).

reply
upvoteby ysleepy1 days ago|
parent|
[-]
If you go that route, GraalPy is there too, so the argument is not as strong as it seems.
reply
upvoteby pjmlp19 hours ago|
parent|
[-]
You missed my remark about PyPy feeling abandoned on the corner, well the same applies to GraalPy.

The Ruby JITs I mentioned are used in production.

While other dynamic language comunities embrace their JITs, in Python world, outside using it as a DSL for GPGPU JITs, it is pretty much let's just keep using CPythion with C and C++ extensions. Adding a JIT to CPython only became a thing after Facebook and Microsoft decided to push for its development.

reply