Earlier quoted context omitted.
There seems to be a very nice solution to the parenthesis problem: https://sourceforge.net/p/readable/wiki/Home/ I have no idea why it hasn't caught on. As far as I'm aware, there's no Clojure implementation. Lispers like their parentheses.
Perhaps because significant white space (e.g. Python) has quite a lot of detractors of its own.
Is Clojure dying, and what has Ruby got to do with it?
11–20 of 261 posts
Re: Is Clojure dying, and what has Ruby got to do with it?
#12in my opinion, this is a key reason, why clojure is not thriving
i can't think of any (problem) domain, where clojure have a framework or library, than is significantly better than most other frameworks or libraries
if you are not number 1 at anything, it is hard to thrive
Re: Is Clojure dying, and what has Ruby got to do with it?
#13I'm still left with the question of "why all the parenthesis?" While it might sound silly and reductionist, it is ostensibly the single hurdle I could never overcome when it came to lisp languages. The majority resides with the fact that it could work without them, so I see it as an ancient artifact.
There seems to be a very nice solution to the parenthesis problem: https://sourceforge.net/p/readable/wiki/Home/ I have no idea why it hasn't caught on. As far as I'm aware, there's no Clojure implementation. Lispers like their parentheses.
Re: Is Clojure dying, and what has Ruby got to do with it?
#14I'm still left with the question of "why all the parenthesis?" While it might sound silly and reductionist, it is ostensibly the single hurdle I could never overcome when it came to lisp languages. The majority resides with the fact that it could work without them, so I see it as an ancient artifact.
Another reason Lisp programmers tolerate parentheses hell is that Lisp development has often paralleled that of emacs and emacs-like editors that make manipulating s-expressions extremely intuitive.
Re: Is Clojure dying, and what has Ruby got to do with it?
#15I'm still left with the question of "why all the parenthesis?" While it might sound silly and reductionist, it is ostensibly the single hurdle I could never overcome when it came to lisp languages. The majority resides with the fact that it could work without them, so I see it as an ancient artifact.
Re: Is Clojure dying, and what has Ruby got to do with it?
#16I'm still left with the question of "why all the parenthesis?" While it might sound silly and reductionist, it is ostensibly the single hurdle I could never overcome when it came to lisp languages. The majority resides with the fact that it could work without them, so I see it as an ancient artifact.
Re: Is Clojure dying, and what has Ruby got to do with it?
#17Re: Is Clojure dying, and what has Ruby got to do with it?
#18Going further, it seems like the whole category of alternative languages hit a peak about three years ago, and interest has been dwindling since. It's like coders got their fix of "new ways of thinking about code", and now have gone back to whatever they feel most productive in. Moreover, the buzziest alt languages now (Elixir, Go, Kotlin) seem to be much closer to existing mainstream languages than the buzzy ones of…
5 years ago mainstream was something like PHP or Java 6.
Re: Is Clojure dying, and what has Ruby got to do with it?
#19Also Common Lisp is better in every way ;) There's even a JVM implementation (ABCL) for people who like that sort of stuff.
Re: Is Clojure dying, and what has Ruby got to do with it?
#20I'm still left with the question of "why all the parenthesis?" While it might sound silly and reductionist, it is ostensibly the single hurdle I could never overcome when it came to lisp languages. The majority resides with the fact that it could work without them, so I see it as an ancient artifact.
I almost never have to think about the parentheses while editing, any more than I would braces in a c-like language. It's really freeing. It's also fully integrated into Cursive so there isn't even a setup step if you're using that already.