I'm back from Rubyconf.
Some people say Ruby is dead. We can probably gloss over Zed Shaw's famous rant, since it's from roundabout 2007. My understanding is that the thought came about because of the many new trends in programming languages: first node, then Erlang's comeback and the birth of Elixir. Evented programming, non-blocking IO, all the fancy buzzwords, and everyone craps on Ruby's Global Interpreter Lock.
Given the talks at Rubyconf, Ruby is most likely not dead (and my company's internal rubylist has an ongoing recent conversation about this if you're curious). There were talks on API design, on fault-tolerant data, on machine-learning, on parallel execution and concurrency, a talk on Raft (an algorithm to obtain consistency)...
Ruby's ecosystem is certainly doing a lot of hard work to stay current. If you use Rubinius or JRuby, you can leverage a ridiculously powerful library called celluloid, plug in celluloid-io and use reel, a webserver based on celluloid-io. Here's the quick blurb on celluloid-io: Celluloid::IO provides an event-driven IO system for building fast, scalable network applications that integrates directly with the Celluloid actor library, making it easy to combine both threaded and evented concepts. Celluloid::IO is ideal for servers which handle large numbers of mostly-idle connections, such as Websocket servers or chat/messaging systems.
In short, Ruby's doing pretty well.
Author Aldric Giacomoni