Replies: 4 comments 5 replies
-
I started in the no C camp. But now I see it as a very fine idea. |
Beta Was this translation helpful? Give feedback.
-
Along the lines of "without any dependencies", how about not growing any additional dependencies (on things already in spork) if merged? I think that would make the json bits still easily usable a la carte without being influenced by other parts of spork. |
Beta Was this translation helpful? Give feedback.
-
One thing that attracts me to Janet is that it's a native program implemented in C. So having native modules in spork ("contrib") is a good thing in my book, as long as it's clear what native libraries (better yet, Debian packages) that I need to have already installed as prerequisites. (Or, when I do |
Beta Was this translation helpful? Give feedback.
-
Another possible way forward: suppose in the future there's some good native modules for Janet written in something other than C (like, for example, Hare, Zig, Rust, etc.) ... modules that you'd like to be part of spork. I wonder if it would then make sense to have separate projects, one for each native implementation language: spork-c |
Beta Was this translation helpful? Give feedback.
-
Currently, spork is a utility library for Janet, but is limited to pure Janet only. However, by merging things like the
json
package (which is written in C) into spork, I think spork itself can be more useful and easier to maintain. Thoughts? I can see some people might like to keep things like JSON separate, but I think it is better to bundle things together for ease of development.Beta Was this translation helpful? Give feedback.
All reactions