Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
In this talk we'll delve into the web frameworks Rails, Hanami and Sinatra and we'll explain how we try to combine the best out of the frameworks to create web apps at 84codes.
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 the video titled "Ruby off Rails," Erica Weistrand presents insights into web development practices at her company, 84 Codes, highlighting their use of various Ruby frameworks: Rails, Hanami, and Sinatra. She begins by introducing herself and her work experience, particularly within the observability team, focusing on message brokers like RabbitMQ and the newly developed LMQ. The talk progresses to clarify the role of message brokers in handling asynchronous communication between services within applications, using a web shop as a relatable example. Erica explains the architecture and ecosystem of applications at 84 Codes, emphasizing the company’s reliance on Ruby and the significance of using multiple programming languages like JavaScript, Clojure, and Crystal to meet efficiency needs. She provides an overview of the three frameworks: - **Sinatra**: Emphasized for its simplicity and API-first approach. However, it lacks enforced structure, which can lead to messy architecture if not managed correctly. - **Rails**: Widely known for its opinionated design and extensive feature set, facilitating quick development with less boilerplate. It’s best suited for traditional web applications but can become complex without proper management due to its conventions. - **Hanami**: Known for being lightweight and modular, encouraging developers to utilize abstractions effectively while adhering to the MVC pattern. Key points discussed include: - The challenges faced with the unstructured setup in Sinatra, where communication patterns differ, causing confusion. - The benefits of frameworks that enforce structure, like Rails and Hanami, which aid in the usability of the applications by reducing ambiguity in code organization. - The integration of third-party libraries and gems to enhance functionality within their applications. Ultimately, Erica considers the implications of transitioning away from Sinatra to either Rails or Hanami, which could potentially streamline development processes and improve community support. However, such a transition would require significant resources and careful exploration during implementation. She concludes by reflecting on her learnings during the preparation of the talk, encouraging developers to explore different frameworks while acknowledging the strengths and weaknesses of each based on their unique needs.
Suggest modifications
Cancel