5 ms·
What is the sweat spot for clojure? Seems like it could be useful in places where the programmers are also responsible for "data entry" and it's better to use a
by wrnr 6y ago
What is the sweat spot for clojure? Seems like it could be useful in places where the programmers are also responsible for "data entry" and it's better to use a lisp instead of xml or java annotations.
- raspasov 6y agoAnywhere where Java/JVM languages (server) or JavaScript (clients + server) is appropriate.
- cutler 6y agoSince a large part of the Java world revolves around Spring I can hardly see Clojure being relevant. Now Kotlin, that's a different story.
- raspasov 6y agoIf Spring is a hard requirement, sure. Writing Java-in-Clojure is pointless. I meant it more in the sense if you value simplicity and you are starting a project more or less from scratch or integrating into a good Java project that doesn’t rely on crufty frameworks.
- fulafel 6y agoThe JVM is incidental for most Clojure projects I think.
- phyrex 6y agoThe creator, Rich Hickey, explains that Clojure has been explicitly designed for 'situated programs' in this talk: https://www.youtube.com/watch?v=2V1FtfBDsLU https://www.youtube.com/watch?v=2V1FtfBDsLU
- fulafel 6y agoIT's a good functionally biased general purpouse dynamic language, with lots of libraries available, quick edit/debug feedback cycle, good tooling, and also works on the frontend where it can share code with the backend. So a lot of things.