4 ms·
The problem with these alternative programming environments is that the developers push off everything other than compiling code. Then the community is left to
by MoscMob 4y ago
The problem with these alternative programming environments is that the developers push off everything other than compiling code. Then the community is left to struggle for years with:
1. How to debug in the language that they write in.
2. How to write unit tests.
3. How to debug unit tests.
4. Common IDE and code-editor integration for 1, 2 and 3.
5. What's the package management story?
For example, the newer programming environment that's released in most recent history that attempts to do an excellent job at this, Deno, still struggles with basics such as IDE integration for debugging unit tests. It's a struggle.
I've heard the creator of Clojure all but say he has put no thought into package management. Nice language, but it's not worth the cost of having to change how the rest of us work when there's existing environments that address the very basics that a developer needs.
- runetech 4y ago> I've heard the creator of Clojure all but say he has put no thought into package management. Nice language, but it's not worth the cost of having to change how the rest of us work when there's existing environments that address the very basics that a developer needs. Clojure relies on maven for this. Maven is a pretty accomplished package manager in the Java ecosystem. If Rich Hickey said that I assume he meant that he did not _have_ to invent a package manager as it comes for free from the underlying system.
- fulafel 4y agoTo add, on Clojure you can also easily use git repos and local directories specified in deps.edn - these tend to get used mostly for private/internal deps. ClojureScript side mostly uses the Maven mechanism for getting ClojureScript deps from Clojars (a Maven repo), but can also import Node modules for interop.