5 ms·

Is Ruby supposed to be an example of "not dying" language? Because it has certainly passed its glory days as well. Also Common Lisp is better in every way ;) T

by Grue3 9y ago

Is Ruby supposed to be an example of "not dying" language? Because it has certainly passed its glory days as well. Also Common Lisp is better in every way ;) There's even a JVM implementation (ABCL) for people who like that sort of stuff.

swannodette 9y ago
I don't know but it seems to me Ruby is dying the same way anything else with 200,000+ questions on Stack Overflow is dying (i.e. it isn't).
- dragandj 9y ago
  David, you have to put more bugs in ClojureScript - we need way more questions on StackOverflow ASAP! :)
- cutler 9y ago
  ... and 134,468 gems at a rate of 33 per day (http://www.modulecounts.com http://www.modulecounts.com).
flavio81 9y ago
True, Common Lisp is better in every way, but still Clojure has its uses (in my opinion, mainly when you need to interact with a lot of Java libraries and don't want to submit to the sadism of the Java language.) Also, the more Clojure users out there, the more people are potentially able to "jump" to the other Lisps like Racket, Arc, Scheme, and CL.
- throwaway7645 9y ago
  Does anyone actually use Arc? Racket, Common Lisp, Clojure, Picolisp even yes. Arc was just used for this forum right and is based on Racket?
mark_l_watson 9y ago
I agree with you, Common Lisp does seem better and ABCL does well with Java interop (as does Clojure). While the community around Clojure is fantastically good, I don't like the language itself as much. Personally for my hacking pleasure, Haskell, Common Lisp, Chez Scheme (or other Schemes), and Ruby are all more fun for me to use.
- GigaMos 9y ago
  If I remember correctly, you showed some kindness towards Clojure (the language). May I ask, what made you reconsider?
jakebasile 9y ago
Why do you consider Common Lisp better in every way?
mirekrusin 9y ago
Funnily enough Ruby is doing not too bad - according to contributions [1] it's at stable speed since 2008 (!) without any slowdown. Similarly Rails [2] looks like healthy, steady project. Ruby/Rails, for rapid prototyping [3] with minimal friction [4] it's still, after years, considered by many, as the best tool for the job. [1] https://github.com/ruby/ruby/graphs/contributors https://github.com/ruby/ruby/graphs/contributors [2] https://github.com/rails/rails/graphs/contributors https://github.com/rails/rails/graphs/contributors [3] rapid prototypes land as production systems - that's a pro tip. [4] minimal friction on all levels that you, as a programer care - from reading and writing code, scaffolding, dev/staging/production deployment, database migrations, testing to caching etc. - not many setups give you all of this.
dragonwriter 9y ago
> Is Ruby supposed to be an example of "not dying" language? Because it has certainly passed its glory days as well. It may have past the (or a local) hype peak, but it seems to be doing just fine. Not being the edgy flavor of the month isn't the same as dying.

by Grue3 9y ago

swannodette 9y ago

I don't know but it seems to me Ruby is dying the same way anything else with 200,000+ questions on Stack Overflow is dying (i.e. it isn't).

dragandj 9y ago
David, you have to put more bugs in ClojureScript - we need way more questions on StackOverflow ASAP! :)
cutler 9y ago
... and 134,468 gems at a rate of 33 per day (http://www.modulecounts.com http://www.modulecounts.com).

flavio81 9y ago

True, Common Lisp is better in every way, but still Clojure has its uses (in my opinion, mainly when you need to interact with a lot of Java libraries and don't want to submit to the sadism of the Java language.) Also, the more Clojure users out there, the more people are potentially able to "jump" to the other Lisps like Racket, Arc, Scheme, and CL.

throwaway7645 9y ago
Does anyone actually use Arc? Racket, Common Lisp, Clojure, Picolisp even yes. Arc was just used for this forum right and is based on Racket?

mark_l_watson 9y ago

I agree with you, Common Lisp does seem better and ABCL does well with Java interop (as does Clojure). While the community around Clojure is fantastically good, I don't like the language itself as much. Personally for my hacking pleasure, Haskell, Common Lisp, Chez Scheme (or other Schemes), and Ruby are all more fun for me to use.

GigaMos 9y ago
If I remember correctly, you showed some kindness towards Clojure (the language). May I ask, what made you reconsider?

jakebasile 9y ago

Why do you consider Common Lisp better in every way?

mirekrusin 9y ago

Funnily enough Ruby is doing not too bad - according to contributions [1] it's at stable speed since 2008 (!) without any slowdown. Similarly Rails [2] looks like healthy, steady project. Ruby/Rails, for rapid prototyping [3] with minimal friction [4] it's still, after years, considered by many, as the best tool for the job. [1] https://github.com/ruby/ruby/graphs/contributors https://github.com/ruby/ruby/graphs/contributors [2] https://github.com/rails/rails/graphs/contributors https://github.com/rails/rails/graphs/contributors [3] rapid prototypes land as production systems - that's a pro tip. [4] minimal friction on all levels that you, as a programer care - from reading and writing code, scaffolding, dev/staging/production deployment, database migrations, testing to caching etc. - not many setups give you all of this.

dragonwriter 9y ago

> Is Ruby supposed to be an example of "not dying" language? Because it has certainly passed its glory days as well. It may have past the (or a local) hype peak, but it seems to be doing just fine. Not being the edgy flavor of the month isn't the same as dying.