It’s hard to subscribe to the mailing list. First, there’s the
link to the forum, with no discernible differentiation from the mailing
list. Next, there’s the web form to subscribe with… that doesn’t
work. (I’ve tried with both my Google and personal accounts – no
soup.) I humbly submit that making the manual method to subscribe be
listed first.
Sorry for the late reply:
There was a problem with the web form so that the subscription requests
queued up for quite some time. It’s fixed since a couple of days.
Wouldn’t it make sense to have another mailing list for the forum?
For example ruby-talk and ruby-forum, this way the mailing list
subscriber can choose themselves if they want to wade through forum
messages.
Indeed. Currently there is a quite confusing situation with this one-way
forwarding. As ruby-forum.com does not point out this fact it may happen
that someone wants to reply on ruby-forum.com to a message submitted via
the ruby-talk ML, leading to the original poster never seeing the reply
as it will not leave ruby-forum.com.
I definitely agree to separating the ruby-talk ML and ruby-forum.com,
but this should be done properly rather than with this in-between
situation.
I will reject HTML emails. | Ich akzeptiere keine HTML-Nachrichten.
|
Use GnuPG for mail encryption: | GnuPG für Mail-Verschlüsselung: http://www.gnupg.org | The GNU Privacy Guard
I think it could be multiple things. Ruby as a stand-alone language
always seemed to be overshadowed by Rails. When I look in my industry
(semiconductors), most people are still using Perl, with some migrating
over to Python and a few of us Ruby. But, of the non-Perl languages
Python seems to be gaining some traction.
There are also now dozens of languages out there for various things
(Haskell, Erlang, etc.) that have also I think added to the perceived
‘decline’. Ruby isn’t the sexy new language anymore.
But that’s just what I’m thinking here. Could be I’m way off base.
if one subtracts [ANN] postings during the last few weeks traffic here
seems to have plummeted. Are there any obvious reasons I might be
overlooking?
Three months later I can say that the observation seems to be
confirmed: it’s sad but this forum (the mailing list) is actually
starving. Apart from the mentioned forum ↔ mailing list gateway
issues there does not seem to be a clear reason. Maybe mailing lists
are not fashionable any more.
I think it could be multiple things. Ruby as a stand-alone language always
seemed to be overshadowed by Rails.
[…]
Ruby isn’t the sexy new language anymore.
I would second that.
However, it remindes me of the Perl crisis years ago. The language
seemed old,
unattractive and just to stubborn to finallly die. Still, during that
time,
seasoned programmers decided to stick with the language and create new
and
awesome things with it. For example, Moose was created during that time.
AFAIK, Ruby does not have anything that is like Moose (or Moo or Mouse),
and
I’m missing it every now and then.
I don’t think that Ruby is dying. But that’s just my very personal
opinion.
I think it could be multiple things. Ruby as a stand-alone language always
seemed to be overshadowed by Rails.
[…]
Ruby isn’t the sexy new language anymore.
I would second that.
That’s true. And if you look at the Linux desktop there are more
applications with a graphical UI around written in Python than in
Ruby.
I don’t think that Ruby is dying. But that’s just my very personal opinion.
Just to avoid misunderstandings: my use of “dying” only referred to
this forum (the mailing list). Decreased popularity (but not dying)
was just one possible explanation for the effect we see here. Others
have offered other explanations such as the Ruby mailing list gateway
issues.
I have the impression that MLs globally decline, as Usenet did :(. No
idea
why, and no idea whether it is actually true, but hey why not throw a
conjecture, huh?
That’s true. And if you look at the Linux desktop there are more
applications with a graphical UI around written in Python than in
Ruby.
As someone relatively new to the Ruby community (around 1 year), lack of
solid support for a GUI toolkit (I’m thinking Qt) was a major “con” at
the time I adopted Ruby (then deciding whether to throw my hat in with
Python or Ruby). Still chose Ruby but this is definitely limiting (to my
use case(s)).
Cheers,
Chris
Chris T.
610.425.7807
“Work as if you were to live a hundred years. Pray as if you were to
die tomorrow.”
-Benjamin Franklin
As someone relatively new to the Ruby community (around 1 year), lack of
solid support for a GUI toolkit (I’m thinking Qt) was a major “con” at
the time I adopted Ruby (then deciding whether to throw my hat in with
Python or Ruby). Still chose Ruby but this is definitely limiting (to my
use case(s)).
Qt seems to lack any language binding except for JavaScript through qml.
However, two projects exist: qtbindings [1], which supports Ruby 1.9 and
2.0.
I’m not quite sure on what YaST is based since they adopted Ruby.
Shoes [2] is also a nice toolkit with a DSL, but it is not based on Qt,
sadly.
I feel like the mailing-list(ML) is on the decline because most MLs are
on
the decline. Also, content wise most of the emails I receive are pretty
much lacking…
Ruby as a whole is a language I do love…I was a total programming
newbie
a year ago and learned both ruby and python…but gravitated more to
Ruby
because I love how expressive and intuitive Ruby is. Recently though, I
have started using python more and more because there’s just so much
more
available to python users in terms of modules(Gems) , Web Frameworks,
and
the community (to me at least) seems more robust. Rails dominates Ruby
almost to a point where most people don’t explore the language for
anything
other than web development.
My office mate is currently looking at Ruby since that’s what I’m
writing all my code in. He was asking me just last week about Tk. I
couldn’t think of any recent scripts I had seen that used Tk. Are people
using Tk much these days?
I would like to cite here the enormous amount of time and energy that
Kouheui Sutou and a few other heroes are pouring since ages into the
creation and maintenance of the Ruby bindings of Gnome, GTK and
friends.
