Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
What happens to Ruby when Rails dies? Ruby rode the Rails rocketship to worldwide renown. While a handful of us were writing Ruby code before Rails came along, most of us owe Rails a debt of gratitude for taking Ruby mainstream, allowing us to make a living writing code in a language we love. But opinions codified in Rails are falling out of favor. We're not writing apps that do heavy server-side rendering. Our apps have complex domain logic that grates against "The Rails Way." Is that it, then? Has Ruby entered its twilight years? Help us caption & translate this video! http://amara.org/v/Fovb/
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
**Ruby After Rails** presents an examination of Ruby's future in light of the declining dominance of the Rails framework. Speaker Ernie Miller discusses the historical context of Ruby's rise, largely attributed to Rails, and raises concerns about the implications of Rails potentially falling out of favor. Key points discussed include: - **Rails' Evolution**: The shift from traditional Rails applications focused on server-side rendering to a contemporary landscape where APIs and client-side frameworks dominate. - **Identity Crisis**: Miller reflects on his own identity as a Ruby developer and the fear surrounding Ruby’s relevance if Rails were to become obsolete. He suggests that his programming identity cannot be solely tied to a single framework. - **Technology Opinions**: The talk touches on the polarization within the programming community regarding tools and languages, contrasting the perspectives of those who champion specific technologies versus those who advocate for technology-agnosticism. - **Flexibility and Readability**: Miller expresses his fondness for Ruby due to its flexibility and readability compared to other languages, notably Perl and Python, which cater to different programming philosophies. - **Concurrency Challenges**: The speaker highlights Ruby's struggles with concurrency, referencing the insights of Tony Arcieri regarding missing language features necessary for better concurrent programming. - **Community and Growth**: He emphasizes the importance of the Ruby community, its encouragement of creativity, and the exploration of new languages by Rubyists as a sign of growth rather than a departure from Ruby. - **Legacy and Future**: The concluding thoughts focus on the lasting legacy of Ruby, the continuing influence of its community, and the idea that while frameworks may change, the fundamental relationships and ideas within programming endure. In summary, Miller advocates for a broader identity as programmers rather than being confined to a single language or framework. He expresses hope for Ruby's future, suggesting that even as technologies evolve, the community and ideologies that surround them contribute to ongoing development and innovation.
Suggest modifications
Cancel
