How dead is ruby?
Language we love is fading, reduced conferences, projects/commits, but final straw Code camps dropping Rails IEEE Spectrum out of top 10
How dead is Ruby?
Exaggerated? But failing
Huge potential
Want to have a future, wish it were ruby,listen here
Is Ruby dying? What’s a Rubyist to do?
The language we love is fading, reduced #s of: conferences, projects, commits, job positions. It’s dropped out of the IEEE Spectrum top 10, and is being dropped by numerous code schools,
While reports of Ruby’s demise are greatly exaggerated, where there’s smoke, there’s fire. What’s Ruby’s relevance in these hot areas in tech:
- Front end web frameworks
- Isomorphic code
- Mobile
- Scaling, speed, size, paralleism/concurrency
The typical answer is that Ruby is not. It’s little known that Ruby or Ruby-esque solutions exist in these categories. There is a future off the beaten path!
This talk will go over not typically known Ruby and/or Ruby-esque solutions to the tech areas in which the world at large feels Ruby has little to no relevance. The desired outcome is to educate Rubyists on paths that can lead to their future happiness and employability.
I love Ruby the language, it’s library and community. It’s given me years of joyful employment and I’ve been trying to give back at every opportunity. While I’ve been trying to explore, create, spread, and evangelize the “Future of Ruby” for a while now, seeing this year that Ruby has dropped out of the IEEE Spectrum top 10 and that code schools are dropping Ruby has convince me that it is still worth trying to show the Ruby community that there is a future for Ruby and Ruby-esque solutions. Hopefully the message can be heard, else we all switch to being Javascript programmers.