News for hackers. Stuff that matters.

A comment on Why I rewrote my Rust keyboard firmware in Zig: consistency, mastery, and fun. Parent comment

Re:Why I rewrote my Rust keyboard firmware in Zig: consisten... by p0nce on Sunday March 07, 2021 @08:37AM (#26375727)
Yes. But you could see the new crop of native languages as: as close to LISP as possible without codegen in the runtime. There is this 2x gap between JIT and AOT. (EDIT: Other than that I'm not sure if any of the new kids can introspect on the content - lines of codes - of a function, like LISP would).
[ Parent | on HN ]
Re:Why I rewrote my Rust keyboard firmware in Zig: consisten... by pjmlp on Sunday March 07, 2021 @05:09PM (#26380257)
Lisps support AOT compilation since several decades, image tree shaking, and actually having a compiler in the runtime allows for tooling that most languages lack.
[ Parent | on HN ]
Re:Why I rewrote my Rust keyboard firmware in Zig: consisten... by p0nce on Sunday March 07, 2021 @05:44PM (#26380519)
Can you avoid having a compiler in the runtime?
[ Parent | on HN ]
Re:Why I rewrote my Rust keyboard firmware in Zig: consisten... by pjmlp on Monday March 08, 2021 @02:46AM (#26383200)
Sure, AOT compilation + tree shaking.

This is one way,

http://www.lispworks.com/documentation/lw70/DV/html/delivery...

[ Parent | on HN ]
Re:Why I rewrote my Rust keyboard firmware in Zig: consisten... by p0nce on Monday March 08, 2021 @04:14AM (#26383647)
So a D successor could be a LISP with mainstream syntax and UX?
[ Parent | on HN ]
Re:Why I rewrote my Rust keyboard firmware in Zig: consisten... by pjmlp on Monday March 08, 2021 @05:29AM (#26384200)
Well, there is Dylan.

D doesn't need a successor, rather a better marketing and fixing all lose ends.

[ Parent | on HN ]