DoodlingDev

[Hotwire on the thoughtbot Blog](https://thoughtbot.com/blog/tags/hotwire)

[thoughtbot Hotwire Examples](https://github.com/thoughtbot/hotwire-example-template)

[Hotrails Turbo Rails Tutorial](https://www.hotrails.dev/turbo-rails)

[30 Days of Hotwire by @ilrock__ on Twitter](https://twitter.com/ilrock__/status/1631315562390519809)

[Code Sample Image Tool](https://www.snappify.com)

subfuzion

Common Options

-#, --progress-bar Make curl display a simple progress bar instead of the more informational standard meter.

-b, --cookie <name=data> Supply cookie with request. If no =, then specifies the cookie file to use (see -c).

-c, --cookie-jar <file name> File to save response cookies to.

jarednorman

Webpack with Rails Part 1

I don't like Sprockets, but it's the easiest and best choice for lots of Ruby on Rails projects. When looking for a better way to manage my JavaScript assets and an improved developer story, my current tool of choice is webpack. While I wish Rails supported drop-in asset pipelines the way that Phoenix does, it's not hard to use webpack with Rails.

chantastic

Hi Nicholas,

I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:

The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't

dolfelt

Code for deploying ember-cli applications with Gulp.js

brianr

select *
from item_occurrence
where timestamp >= unix_timestamp() - 24 * 60 * 60
  and request.url like '%mydomain.com%'

acolyer

Internet Scale Services Checklist

A checklist for designing and developing internet scale services, inspired by James Hamilton's 2007 paper "On Desgining and Deploying Internet-Scale Services."

• http://mvdirona.com/jrh/talksandpapers/jamesrh_lisa.pdf

Basic tenets

• Does the design expect failures to happen regularly and handle them gracefully?
• Have we kept things as simple as possible?

ahoward

# make this script run, update your gist with the running script, and it's
# output in a separate gist.  the entire quzi should take 1-3 minutes, but you
# get 5.
#


# the meat - take < 5 minutes to do this
#
  assert :hash do
    x = nil

jlongster

var dom = Bloop.dom;

var Box = Bloop.createClass({
  getInitialState: function() {
    return { number: 0 };
  },
  
  updateNumber: function() {
    this.state.number++;
  },

jlongster

(function() {
  // Do not use this library. This is just a fun example to prove a
  // point.
  
  var Bloop = window.Bloop = {};

  var mountId = 0;
  function newMountId() {
    return mountId++;
  }