Re:Janet: a lightweight, expressive and modern Lisp
by nisa on Wednesday May 13, 2020 @06:21AM
(#23165389)
so what's better and out there and reasonable stable?
Re:Janet: a lightweight, expressive and modern Lisp
by zelphirkalt on Wednesday May 13, 2020 @06:59AM
(#23165615)
Probably BeamVM, giving you better options for scaling, abstracting away machine borders and lightweight processes.
Re:Janet: a lightweight, expressive and modern Lisp
by ethelward on Wednesday May 13, 2020 @09:26AM
(#23166640)
BeamVM is much worse than the JVM in the raw computing performances department.
Re:Janet: a lightweight, expressive and modern Lisp
by zelphirkalt on Wednesday May 13, 2020 @10:58AM
(#23167499)
As far as I know, people in the Erlang world tend to use NIFs for computation heavy tasks: http://erlang.org/doc/tutorial/nif.html However, I have not done that myself, so I cannot tell from experience how that works.
Re:Janet: a lightweight, expressive and modern Lisp
by varjag on Wednesday May 13, 2020 @06:22AM
(#23165397)
x86-64
Re:Janet: a lightweight, expressive and modern Lisp
by fouc on Wednesday May 13, 2020 @07:30AM
(#23165766)
market share is going to ARM
Re:Janet: a lightweight, expressive and modern Lisp
by varjag on Wednesday May 13, 2020 @04:22PM
(#23171385)
ARM is nice too, I concur
Re:Janet: a lightweight, expressive and modern Lisp
by smt88 on Wednesday May 13, 2020 @06:38AM
(#23165484)
From the narrow scope of web development, JVM is fine. Kotlin is able to have every ergonomic feature you'd want from a language, and it gets closer to the performance of C in TechEmpower than many other languages (notably C#, Node, and Python, three of the most popular languages).
Tuning can be a pain, but scaling anything is hard.
Re:Janet: a lightweight, expressive and modern Lisp
by varjag on Wednesday May 13, 2020 @06:51AM
(#23165573)
It is clear that a lot of very important and practical work had been delivered with Java/JVM. But the original point was not about what is possible, but what is optimal.
Kotlin, from the little I've seen, appears to be largely a syntactic variation of Java, so there is certainly good impedance to JVM. Clojure is less so, and here lies the reason everyone curses about its backtraces.
Can you jump over 64Kb in bytecode yet? Allocate a lexically scoped variable?
Of course, enormous amount of work has been put into making this particular pig fly at reasonable speed. Doesn't change the fact that most usability complaints about Clojure stem from reliance on JVM piggybacking.