Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Last year, DHH said "good frameworks are extractions, not inventions." The success of Rails lets us forget its roots as an extraction from an HTML-based UI. The failure of Rails has been its perception as "best web framework ever" instead of "best web framework for apps like Basecamp". Given that, it's clear why Rails makes writing a UI in HTML a joy but does few favors for JavaScript-heavy apps. Joy can be had in JavaScript, and we'll show how with Lineman.js & tools extracted to help find it! Justin Searls has two professional passions: writing great software and sharing what he's learned in order to help others write even greater software. He and his team at Test Double have the pleasure of living out both passions every day, working closely with clients to find simple solutions to complex problems. Help us caption & translate this video! http://amara.org/v/FG05/
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
In his RailsConf 2014 presentation, Justin Searls discusses the limitations of using Ruby on Rails as the sole solution for web applications that require heavy JavaScript interaction. He argues that while Rails has been highly successful, its framework has led developers to rely on server-side solutions for problems that are best solved on the client-side. Key points from the presentation include: - **Monolithic Application Architecture**: Searls emphasizes the issue of monolithic applications, which can lead to complications as more features are added. The workflow often defaults to using Rails for all web applications, which may not suit JavaScript-heavy needs. - **The Genesis of Rails**: Rails was created to solve specific problems identified by Basecamp. However, its design caters primarily to traditional web workflows, hindering development for modern, dynamic applications. - **JavaScript and Client-Side Tools**: Many Rails developers tend to overlook modern JavaScript tools due to a lack of familiarity and experience. Searls notes that it is essential to seek better tools and frameworks that align with current web application demands. - **Comparison with Other Frameworks**: Searls argues that non-Ruby developers may be better equipped to handle modern JavaScript environments, as they are not bound by the Rails’ influence. - **Lineman.js Introduction**: To address these challenges, Searls introduces Lineman.js, a tool designed to improve JavaScript development workflows. Lineman provides rapid feedback and supports modern JavaScript practices, enhancing productivity compared to traditional Rails approaches. - **Separation of Concerns**: He advocates for separating front-end and back-end development, which can simplify the complexity of applications and allow for better alignment of tools used on both ends. - **Modern Build Tools**: Searls underscores the importance of build tools like Grunt, which can streamline the development process and integrate well with modern JavaScript libraries. In conclusion, Searls calls for a shift in how developers view Rails not as a one-size-fits-all solution, but rather as a framework that shines for applications akin to Basecamp. He encourages embracing JavaScript’s potential and leveraging tools like Lineman.js for better application development practices.
Suggest modifications
Cancel
