You are viewing an old version of this page. View the current version.
Compare with Current |
View Page History
Rationale
Java deployments increasingly rely on modularity services such as OSGi. In addition, packages such as NetKernel etc would like languages to behave as services. Clojure should behave well in such environments.
Plan
- Fix misfeatures that are broken in the face of modularity
- add-classpath
- all-ns?
- Add features to make Clojure a better language-as-service
Issues
- No standards for modularity of dynamically-generated code
- Most systems focus on the dynamic loading of statically compiled code
Labels: