Carp – A statically typed Lisp, without a GC, for real-time applications
1–10 of 139 posts
Re: Carp – A statically typed Lisp, without a GC, for real-time applications
#2Anyone who had used or tried Carp and Janet (that was on frontpage the other day)?
What are some strong points on Carp vs. Janet?
Re: Carp – A statically typed Lisp, without a GC, for real-time applications
#3Anyone who had used or tried Carp and Janet (that was on frontpage the other day)? What are some strong points on Carp vs. Janet?
Janet is dynamic with a garbage collector.
Carp is a GC-less static Lisp with deterministic memory allocation via a Rust-like borrow checker.
I only wish Carp had stayed nearer Clojure's syntax. A more familiar syntax would make it more accessible.
Re: Carp – A statically typed Lisp, without a GC, for real-time applications
#4Anyone who had used or tried Carp and Janet (that was on frontpage the other day)? What are some strong points on Carp vs. Janet?
I have not used carp, and janet only briefly. However, other than both using lisp syntax, there are very little similarities between the two.
Janet has a garbage collector, no static types, no ownership tracking - the perf. is similar to lua, so is not be ideal for low-level/realtime systems, which carp is targeting.
Re: Carp – A statically typed Lisp, without a GC, for real-time applications
#5Anyone who had used or tried Carp and Janet (that was on frontpage the other day)? What are some strong points on Carp vs. Janet?
I have not used carp, and janet only briefly. However, other than both using lisp syntax, there are very little similarities between the two. Janet has a garbage collector, no static types, no ownership tracking - the perf. is similar to lua, so is not be ideal for low-level/realtime systems, which carp is targeting.
Thank you and @pgt. I thought Janet compiles to C or native bytecode due to its strong interop with C.
Re: Carp – A statically typed Lisp, without a GC, for real-time applications
#6Anyone who had used or tried Carp and Janet (that was on frontpage the other day)? What are some strong points on Carp vs. Janet?
I have not used carp, and janet only briefly. However, other than both using lisp syntax, there are very little similarities between the two. Janet has a garbage collector, no static types, no ownership tracking - the perf. is similar to lua, so is not be ideal for low-level/realtime systems, which carp is targeting.
> the perf. is similar to lua, so is not be ideal for low-level/realtime systems
Lua runs on a bunch of low level systems, and not just for hobbyists (it's at the core of VxWorks, for example). Can you expand on why you think the language doesn't meet your performance criteria?
Re: Carp – A statically typed Lisp, without a GC, for real-time applications
#7There is also interesting CL implementation that is based on the LLVM framework - Clasp[1]. It can be natively compiled and designed for performance.
Re: Carp – A statically typed Lisp, without a GC, for real-time applications
#8Was it always the case that, on a weekly basis (if not more often), new languages would sprout? It seems to me like considerable amounts of energy are invested on re-inventing-the-wheel instead of solving real problems with existing tools.
Re: Carp – A statically typed Lisp, without a GC, for real-time applications
#9"Real-time" has a specific meaning in embedded and computing context. Does it mean that programs written in Carp have any guarantee on their order or duration of execution?
Re: Carp – A statically typed Lisp, without a GC, for real-time applications
#10"Real-time" has a specific meaning in embedded and computing context. Does it mean that programs written in Carp have any guarantee on their order or duration of execution?
Unless it has a scheduler for a concurrency or threading framework, what other characteristics beyond memory management would be relevant? I guess maybe certain types of built-in data structures--you'd probably want a map/dictionary based on red-black or AVL trees rather than a hash table.