Elixir is known for being a language made for building distributed applications that scale, are massively concurrent, and have self-healing properties. All of these adjectives paint Elixir in a grandiose light. And for good reasons! But is Elixir also a language that can be used for the more mundane tasks of this world like scripting? I think the answer is a definite yes. To see this, let’s take a
In its eleventh year as an open source project, we have decided to halt work on Paperclip. This comes from a combination of already slowed work on the project, a constantly growing list of issues and pull requests that we struggle to keep on top of, and most recently the release of ActiveStorage in Rails 5.2. Migrating For moving from Paperclip to ActiveStorage, please see the migration guide. As
Photo by NCWRC and courtesy of Ohio University. Licensed CC-BY-NC. Cocaine was originally extracted from how Paperclip handled shelling out its commands to ImageMagick. I named it “Cocaine” because, one, I really enjoy puns and, two, I fully didn’t expect anyone else to use it. But, as they say, no matter what you assume, people will do something differently. Is that what they say? Anyway, point i
Lucky catches bugs, returns responses quickly, and helps you write maintainable code. Lucky’s actions help you to process requests and return responses as reliably and productively as possible. To make Lucky actions rock solid, we looked at the problems we often experience while building apps. Problems that we wanted to solve with Lucky These issues often slow down development or cause embarrassin
These days, most Rails projects use some form of factories in their test set up. What problem do they solve and why are they needed? Too much info Given a User model with first_name, last_name, and location fields, we could write a test like: describe "#full_name" do it "combines first and last name" do user = User.new( first_name: "Joël", last_name: "Quenneville", location: "Boston" ) expect(user
We’re renaming factory_girl to factory_bot (and factory_girl_rails to factory_bot_rails). All the same functionality of factory_girl, now under a different name. Initial Rollout After the rename of the gem, we rolled out version 4.8.2 of all of factory_girl, factory_girl_rails, factory_bot, and factory_bot_rails on October 20, 2017. We decided on a patch-level release because after internal testin
When dealing with code, it’s usually apparent when it’s time to move on to the next feature or wrap up the project. Once the code works and it’s written well you can typically call it a day. In design however, drawing that line can be tricky and has the tendency to be very subjective. While others may look at a design and think it’s up to par, sometimes there’s an uneasy feeling that it’s not quit
In this article, we examine a few features of React Native that helped us ship a cross-platform iOS and Android app in 8 weeks, without sacrificing user experience on either platform. First, we’ll see how code reuse and a fast feedback cycle let us move really quickly and help us rapidly iterate on our designs. Then, we’ll learn about the framework’s flexbox-based layout system and evaluate a few
You’re excited about building a new application which allows users to sign up and host their own blog. You decide that each blog will have their own space by providing a subdomain. Let’s start off with a feature spec. require "rails_helper" feature "user views a blog" do scenario "homepage" do blog = create( :blog, subdomain: "bobloblaw", title: "Bob Loblaw's Law Blog", description: "Welcome to my
Some aspects look different at a first glance. For example, Elixir code looks a bit more verbose than Ruby code. Module names are spelled out in most function calls. Modules being used in the current file are explicitly included. State is passed into functions as arguments. Before explaining how macros can extend the language, its documentation page explicitly discourages its use. Elixir can indee
About a year and a half ago we built an internal tool for company-wide announcements. We had originally built the back-end in Phoenix and the front-end in React, taking advantage of Redux and Phoenix channels to deliver updates to the browser in real-time. This made for a great real-time experience but it also slowed down the pace of development and caused fewer people to contribute. About three m
Ruby on Rails 5.0 was just announced! Rails continues to be secure, productive, extensible, stable, and makes us happy thanks to the consistent work of the core team and hundreds of contributors. To all of you who helped triage an issue with Rails or its ecosystem, contributed any new issue, improved documentation, or submitted code: thank you! Writing Ruby is fun and productive thanks to your wor
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く