text
stringlengths
0
1.82k
[1621.32 --> 1622.08] and I think
[1622.08 --> 1622.56] Goa is trying
[1622.56 --> 1623.56] to strike the
[1623.56 --> 1623.86] balance
[1623.86 --> 1624.30] between the
[1624.30 --> 1624.48] two.
[1624.78 --> 1624.92] Yeah,
[1624.96 --> 1625.62] my impression
[1625.62 --> 1626.34] was that
[1626.34 --> 1627.78] it was very
[1627.78 --> 1629.50] easy in the
[1629.50 --> 1630.04] sense that
[1630.04 --> 1630.78] when you
[1630.78 --> 1631.46] jump into
[1631.46 --> 1632.24] a Rails app
[1632.24 --> 1633.74] it's very easy
[1633.74 --> 1634.40] to get going.
[1635.08 --> 1635.56] So it was
[1635.56 --> 1636.24] easy in that
[1636.24 --> 1637.00] sense but it
[1637.00 --> 1637.34] was also
[1637.34 --> 1638.24] simple and
[1638.24 --> 1638.94] that's what
[1638.94 --> 1639.72] I was trying
[1639.72 --> 1640.50] to say
[1640.50 --> 1642.60] in Rails
[1642.60 --> 1643.04] I'm using
[1643.04 --> 1643.44] a lot of
[1643.44 --> 1644.06] abstractions
[1644.06 --> 1644.42] that maybe
[1644.42 --> 1645.02] I went into
[1645.02 --> 1645.38] the Rails
[1645.38 --> 1646.20] source code
[1646.20 --> 1646.72] and looked
[1646.72 --> 1647.14] at it
[1647.14 --> 1647.86] and I know
[1647.86 --> 1648.42] what it is
[1648.42 --> 1649.66] but probably
[1649.66 --> 1650.46] I didn't
[1650.46 --> 1650.86] and with
[1650.86 --> 1652.24] using
[1652.24 --> 1653.28] Goa and
[1653.28 --> 1653.94] Gorma
[1653.94 --> 1655.20] I see
[1655.20 --> 1655.92] everything right
[1655.92 --> 1656.18] there.
[1656.40 --> 1657.48] I have direct
[1657.48 --> 1658.10] control of
[1658.10 --> 1658.62] what's going
[1658.62 --> 1659.94] on and
[1659.94 --> 1660.88] it's simple.
[1661.54 --> 1661.58] Yeah,
[1661.64 --> 1661.94] that makes
[1661.94 --> 1662.18] sense.
[1662.58 --> 1662.90] I'm happy
[1662.90 --> 1663.18] you said
[1663.18 --> 1663.38] that.
[1663.50 --> 1663.62] I mean
[1663.62 --> 1663.82] that was
[1663.82 --> 1664.24] definitely
[1664.24 --> 1665.18] a goal
[1665.18 --> 1665.64] too is
[1665.64 --> 1666.54] trying to
[1666.54 --> 1667.54] simplify
[1667.54 --> 1668.16] things
[1668.16 --> 1668.92] and kind
[1668.92 --> 1669.34] of hide
[1669.34 --> 1669.58] a lot
[1669.58 --> 1669.90] of the
[1669.90 --> 1670.32] complexity
[1670.32 --> 1670.90] of hooking
[1670.90 --> 1671.64] up the
[1671.64 --> 1672.02] mux
[1672.02 --> 1674.00] and so
[1674.00 --> 1674.34] in a
[1674.34 --> 1675.04] general code
[1675.04 --> 1676.30] and then
[1676.30 --> 1677.24] what you
[1677.24 --> 1677.68] have to
[1677.68 --> 1678.04] implement
[1678.04 --> 1678.48] as the
[1678.48 --> 1678.88] user
[1678.88 --> 1679.94] should be
[1679.94 --> 1680.20] fairly
[1680.20 --> 1680.72] straightforward.
[1681.02 --> 1681.36] Basically
[1681.36 --> 1681.90] the data
[1681.90 --> 1682.32] structures
[1682.32 --> 1682.64] you have
[1682.64 --> 1682.92] to deal
[1682.92 --> 1683.22] with
[1683.22 --> 1683.88] are the
[1683.88 --> 1684.10] ones
[1684.10 --> 1684.62] that you
[1684.62 --> 1685.06] define
[1685.06 --> 1685.32] in your
[1685.32 --> 1685.78] design
[1685.78 --> 1686.80] so it
[1686.80 --> 1686.94] should
[1686.94 --> 1687.32] all be