Basilisp should pursue tight integration with python module system. #1262
amano-kenji
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
My intuition tells me basilisp should go all the way with pyproject.toml and maybe basilisp.edn. deps.edn and project.clj inevitably require jar dependencies which are not meant to be used outside JVM. A basilisp project that relies on jars cannot be uploaded as a python library to pypi.
There is no functioning cross-platform packaging system for any programming language. Some scheme programmers created cross-platform package managers like akku.scm and others, but they aren't great, and they were built from scratch to be cross-platform.
The biggest pain point of clojurescript is that it doesn't try to integrate with javascript module system. That's why cherry is being written to target ES6 modules. If basilisp doesn't tightly integrate with python module system, it will be painful to use basilisp. I want cherry, not clojurescript.
A hosted language should tightly integrate with the host module system. Rust is not a hosted language and tries to ignore C as much as possible. Rust also doesn't care too much about interoperating with other languages.
Beta Was this translation helpful? Give feedback.
All reactions