text
stringlengths
0
1.82k
[2189.16 --> 2189.54] areas,
[2189.62 --> 2189.84] so having
[2189.84 --> 2190.46] good examples
[2190.46 --> 2190.86] around that
[2190.86 --> 2191.42] makes a lot
[2191.42 --> 2191.80] of sense.
[2192.68 --> 2192.98] So,
[2193.34 --> 2193.60] finishing
[2193.60 --> 2194.28] those examples,
[2194.90 --> 2195.44] making sure
[2195.44 --> 2195.88] everybody is
[2195.88 --> 2196.30] happy with
[2196.30 --> 2196.58] those,
[2196.80 --> 2197.58] and then I
[2197.58 --> 2197.88] think at
[2197.88 --> 2198.32] that point
[2198.32 --> 2198.78] we'll be
[2198.78 --> 2199.40] ready to
[2199.40 --> 2200.82] freeze and
[2200.82 --> 2201.38] kind of
[2201.38 --> 2202.12] ship 1.0,
[2202.26 --> 2202.48] whatever
[2202.68 --> 2202.98] means.
[2203.82 --> 2204.34] But the
[2204.34 --> 2204.66] idea is
[2204.66 --> 2205.06] that then
[2205.06 --> 2205.50] that is
[2205.50 --> 2205.86] stable.
[2206.18 --> 2206.66] So if
[2206.66 --> 2207.04] you were
[2207.04 --> 2207.72] waiting for
[2207.72 --> 2208.02] Goa to
[2208.02 --> 2208.46] be stable
[2208.46 --> 2208.90] to use
[2208.90 --> 2209.06] it,
[2209.16 --> 2209.38] there you
[2209.38 --> 2209.56] go,
[2209.70 --> 2209.88] now you
[2209.88 --> 2210.20] can start
[2210.20 --> 2210.64] using it.
[2211.34 --> 2211.94] And now
[2211.94 --> 2212.76] for moving
[2212.76 --> 2213.22] on for
[2213.22 --> 2214.12] VNEX 2.0,
[2214.56 --> 2215.62] I think there's
[2215.62 --> 2216.04] a couple of
[2216.04 --> 2216.94] interesting areas
[2216.94 --> 2217.44] I'm looking at
[2217.44 --> 2217.76] right now.
[2217.86 --> 2218.26] One is
[2218.26 --> 2220.80] extending Goa
[2220.80 --> 2221.82] beyond HTTP.
[2222.62 --> 2223.24] So in
[2223.24 --> 2223.62] particular,
[2223.88 --> 2224.12] I've been
[2224.12 --> 2224.48] looking at
[2224.48 --> 2225.06] GRPC.
[2225.06 --> 2226.58] I think it's
[2226.58 --> 2227.06] an area
[2227.06 --> 2227.88] that I've
[2227.88 --> 2228.74] been asked
[2228.74 --> 2229.16] a lot,
[2229.52 --> 2229.86] and it's
[2229.86 --> 2230.36] also something
[2230.36 --> 2230.76] we are
[2230.76 --> 2231.24] looking at
[2231.24 --> 2231.62] here at
[2231.62 --> 2232.08] RightScale.
[2232.64 --> 2233.50] So I'd
[2233.50 --> 2233.92] like to see
[2233.92 --> 2234.22] what we
[2234.22 --> 2234.56] can do
[2234.56 --> 2234.88] there.
[2235.48 --> 2236.00] It's going
[2236.00 --> 2236.12] to be
[2236.12 --> 2236.48] interesting
[2236.48 --> 2237.90] because some
[2237.90 --> 2238.14] of the
[2238.14 --> 2238.86] abstractions
[2238.86 --> 2240.20] don't match
[2240.20 --> 2241.06] exactly the
[2241.06 --> 2242.12] HTTP rest
[2242.12 --> 2242.70] abstractions,
[2242.86 --> 2243.14] so we're
[2243.14 --> 2243.72] going to have
[2243.72 --> 2245.06] to come up
[2245.06 --> 2245.54] with some
[2245.54 --> 2246.72] interesting
[2246.72 --> 2247.56] solutions there,
[2247.68 --> 2248.12] but I think
[2248.12 --> 2248.64] it makes
[2248.64 --> 2248.94] sense.
[2249.66 --> 2250.14] And another
[2250.14 --> 2250.92] interesting space
[2250.92 --> 2251.42] is making
[2251.42 --> 2251.94] the DSL
[2251.94 --> 2252.60] engine a
[2252.60 --> 2252.96] bit more
[2252.96 --> 2253.40] flexible.
[2253.98 --> 2254.54] So today