ohanhi

This is a proposal for a lightning talk at the Reactive 2015 conference.

NOTE: If you like this, star ⭐ the Gist - the amount of stars decides whether it makes the cut!

The Joy of Composition

Why stateless rendering is pure bliss

React just got stateless components, meaning that they are in essence pure functions for rendering. Pure functions make it dead simple - even fun - to refactor your views

nolanlawson

// Promise.all is good for executing many promises at once
Promise.all([
  promise1,
  promise2
]);

// Promise.resolve is good for wrapping synchronous code
Promise.resolve().then(function () {
  if (somethingIsNotRight()) {
    throw new Error("I will be rejected asynchronously!");

jimweirich

gem 'minitest'
require 'minitest/autorun'
require './beer_song'

class BeerSongTest < Minitest::Test

  V8 =
    "8 bottles of beer on the wall, 8 bottles of beer.\n" +
    "Take one down and pass it around, 7 bottles of beer on the wall.\n"

st23am

require 'rrobots'

class Robot3
  include Robot
  def tick events
    @rapid_fire = 0 if @rapid_fire.nil?
    @last_seen = 0 if @last_seen.nil?
    @turn_speed = 3 if @turn_speed.nil?

    if time - @last_seen > 200

kulesa

class ActionDispatch::Routing::Mapper
  def draw(routes_name)
    instance_eval(File.read(Rails.root.join("config/routes", "#{@scope[:shallow_prefix]}", "#{routes_name}.rb")))
  end
end

BCX::Application.routes.draw do  
  draw :projects # => config/routes/projects.rb

  namespace :admin do

dhh

class ActionDispatch::Routing::Mapper
  def draw(routes_name)
    instance_eval(File.read(Rails.root.join("config/routes/#{routes_name}.rb")))
  end
end

BCX::Application.routes.draw do
  draw :api
  draw :account
  draw :session

radar

Welcome to #rubyonrails

Please behave in a polite, considerate and inclusive manner in the channel at all times. People volunteer their time in the channel to help people like you with your Rails problems and some respect (in both directions) will go an extremely long way.

These rules are in place so that you can get the quickest and best support from #rubyonrails.

Rule #0: Show rather than tell. Explaining your problem with code, stacktraces or errors is always preferred to explaining it with just text. Show us what's happening, rather than telling us.

1. Do your research before hand. Your question may be answerable with a quick Google search or by simply experimenting. If you're using a method in Rails, look it up in the API Docs or in the Official Guides.
2. If you've tried Googling, explain what terms you've tried to use so people can better help you.