This document summarizes Hiroaki Ninomiya's presentation on using Vue.js and Vuex at Repro. It discusses Repro's transition from Rails with CoffeeScript and jQuery to Rails 5 with ES6, Webpack, and Vue components. It describes moving from Sprockets to Webpack and adopting Vue.js and Vuex for frontend development. It also mentions Repro's expansion into a web SDK and recent product launches.
1. The document summarizes Repro Tech Meetup #5, which featured a talk on frontend reliability.
2. The talk discussed how frontend technology has evolved from JavaScript and Flash in the 2000s to modern techniques like virtual DOM and ES6.
3. It also covered how the speaker's company Repro approaches frontend development, including using tools like unit testing with Mocha and Karma, ESLint for linting, and system specs for Rails integration.
1. The document discusses the evolution of Rails and JavaScript integration over different Rails versions from Rails 4 to Rails 5.
2. It highlights how Rails 4 used Sprockets and included jQuery, CoffeeScript, and Rails JavaScript helpers, while Rails 5 switched to Webpack and introduced support for modern JavaScript frameworks like React and Vue.js.
3. The speaker then shares some of their experiences building applications with Rails and modern JavaScript including using Webpack, Vuex, and publishing packages to npm.
This document summarizes Hiroaki Ninomiya's presentation on using Vue.js and Vuex at Repro. It discusses Repro's transition from Rails with CoffeeScript and jQuery to Rails 5 with ES6, Webpack, and Vue components. It describes moving from Sprockets to Webpack and adopting Vue.js and Vuex for frontend development. It also mentions Repro's expansion into a web SDK and recent product launches.
1. The document summarizes Repro Tech Meetup #5, which featured a talk on frontend reliability.
2. The talk discussed how frontend technology has evolved from JavaScript and Flash in the 2000s to modern techniques like virtual DOM and ES6.
3. It also covered how the speaker's company Repro approaches frontend development, including using tools like unit testing with Mocha and Karma, ESLint for linting, and system specs for Rails integration.
1. The document discusses the evolution of Rails and JavaScript integration over different Rails versions from Rails 4 to Rails 5.
2. It highlights how Rails 4 used Sprockets and included jQuery, CoffeeScript, and Rails JavaScript helpers, while Rails 5 switched to Webpack and introduced support for modern JavaScript frameworks like React and Vue.js.
3. The speaker then shares some of their experiences building applications with Rails and modern JavaScript including using Webpack, Vuex, and publishing packages to npm.
This document summarizes a Rails developers meetup. It discusses using domain-driven design principles like separating domain models from presentation logic. Presenters act as interfaces between controllers and forms. Forms are updated to accept presenters as arguments. This improves separation of concerns. The meetup also covered continuous integration, technical debt, and domain-specific languages in Rails. Finally, it advertised an upcoming Repro Tech meetup and job openings at Repro.
The document discusses issues an end user is having with an app. The supplier of the app is frustrated as they are unable to resolve the user's problem. The end user is seeking help from the app supplier to fix the ongoing problem with the app.
This document summarizes a presentation about building a simple web application using Sinatra. It discusses using Sinatra and related gems like Capistrano for deployment and Ridgepole for migrations. It also compares the performance of the Sinatra app to Rails, finding the Sinatra app was faster. The presentation provided details on the Sinatra app called IMASquare that was built for a coding competition.
1) The document discusses modernizing Rails applications by adopting ES2015 and using JavaScript frameworks like Vue.
2) It provides examples of how a Rails app was modernized between 2014-2017 by migrating to newer JavaScript features and incorporating Vue components.
3) The author encourages adopting modern techniques like using JavaScript for views and components while keeping implementations simple.
The document discusses Foreign Function Interface (FFI) libraries for Ruby. It mentions the ffi gem which provides a FFI for Ruby and allows easy integration of Ruby with external libraries written in other languages like C. It also discusses PyCall which uses ffi to provide a way to call Python code from Ruby. Some example uses of FFI libraries are to call fast Fourier transform (FFT) code or integrate with C libraries for tasks like image processing.
This document discusses the Mastodon API. It provides instructions on how to register an application to access the Mastodon API and obtain an access token. It also mentions that the Mastodon API is similar to Twitter's API and recommends using the mastodon Ruby gem to interface with the Mastodon API. Finally, it references a Mastodon watcher script that can send Mastodon notifications to Slack.
This document discusses the Paperclip gem, which allows ActiveRecord models to manage file attachments. Paperclip aims to treat file attachments like normal attributes, delaying file operations until save. It handles validations, transformations, and removing files when set to nil. Setup involves declaring attachments with has_attached_file and Paperclip provides methods like exists? to check files.
This document discusses a personal project to build an image sharing application called imshk. It lists technologies used like Git, the Octokit GitHub gem, and the Heroku toolbelt. The project code is available on GitHub at https://github.com/treby/imshk.
This document summarizes the testdouble/suture gem, which allows recording and replaying method calls to support test doubles. It can record method calls to a database to later verify call arguments match expectations or return values match previously recorded values. The document outlines how suture creates a plan, chooses a surgeon strategy to operate according to the plan, and the different surgeon strategies like Observer, Auditor, and Remediator.