text
stringlengths
0
1.82k
[2461.22 --> 2461.48] time I
[2461.48 --> 2461.92] used Cobra
[2461.92 --> 2462.42] and Viper.
[2463.48 --> 2464.16] Today I
[2464.16 --> 2464.54] would have
[2464.54 --> 2464.88] an easy
[2464.88 --> 2465.32] time.
[2465.46 --> 2465.66] But if
[2465.66 --> 2466.06] it was my
[2466.06 --> 2466.76] first time
[2466.76 --> 2468.06] this would
[2468.06 --> 2468.44] be so
[2468.44 --> 2468.78] easy.
[2469.04 --> 2469.60] This would
[2469.60 --> 2469.82] have been
[2469.82 --> 2470.18] so easy
[2470.18 --> 2470.64] because the
[2470.64 --> 2471.00] documentation
[2471.00 --> 2472.86] is amazing.
[2473.14 --> 2473.56] Kudos to
[2473.56 --> 2475.06] the project
[2475.06 --> 2475.52] container.
[2476.70 --> 2478.34] I just
[2478.34 --> 2478.98] quickly looked
[2478.98 --> 2479.40] at this
[2479.40 --> 2480.78] but it
[2480.78 --> 2481.22] seems like
[2481.22 --> 2481.72] it has
[2481.72 --> 2483.72] integrations
[2483.72 --> 2484.18] for other
[2484.18 --> 2484.58] things.
[2484.88 --> 2486.54] You can
[2486.54 --> 2487.52] define a
[2487.52 --> 2487.92] particular
[2487.92 --> 2489.14] argument as
[2489.14 --> 2489.76] a PID
[2489.76 --> 2491.14] file and
[2491.14 --> 2492.02] it decodes
[2492.02 --> 2492.48] that and
[2492.48 --> 2492.90] gives you
[2492.90 --> 2493.50] a pointer
[2493.50 --> 2493.84] to the
[2493.84 --> 2494.36] file so
[2494.36 --> 2494.60] you can
[2494.60 --> 2495.14] interact with
[2495.14 --> 2495.44] it that
[2495.44 --> 2495.64] way.
[2495.64 --> 2496.80] It is an
[2496.80 --> 2497.12] interesting
[2497.12 --> 2498.00] approach with
[2498.00 --> 2498.32] these
[2498.32 --> 2499.66] decoders.
[2499.86 --> 2500.12] I'll have
[2500.12 --> 2500.34] to look
[2500.34 --> 2500.64] into this
[2500.64 --> 2500.84] a little
[2500.84 --> 2501.10] more.
[2501.58 --> 2502.02] Exactly.
[2502.66 --> 2503.60] You can
[2503.60 --> 2506.60] define your
[2506.60 --> 2507.52] flags as
[2507.52 --> 2508.46] slice or
[2508.46 --> 2510.02] map and
[2510.02 --> 2510.46] there are
[2510.46 --> 2510.92] the features
[2510.92 --> 2511.26] there.
[2511.98 --> 2512.26] That's
[2512.26 --> 2512.58] interesting.
[2513.30 --> 2513.86] My
[2513.86 --> 2515.20] edition for
[2515.20 --> 2515.70] this week
[2515.70 --> 2516.26] is the
[2516.26 --> 2516.70] post by
[2516.70 --> 2517.34] Scott Mansfield
[2517.34 --> 2517.56] from
[2517.56 --> 2518.34] Netflix
[2518.34 --> 2519.36] about
[2519.36 --> 2520.04] application
[2520.04 --> 2520.64] data
[2520.64 --> 2521.08] caching.
[2521.68 --> 2522.50] It is
[2522.50 --> 2523.52] way too
[2523.52 --> 2523.94] in-depth
[2523.94 --> 2524.40] and too
[2524.40 --> 2524.86] long to
[2524.86 --> 2525.20] discuss
[2525.20 --> 2525.44] here.
[2525.64 --> 2526.66] There are
[2526.66 --> 2527.04] some
[2527.04 --> 2528.10] interesting
[2528.10 --> 2528.58] discussions
[2528.58 --> 2529.28] about
[2529.28 --> 2529.74] data
[2529.74 --> 2530.12] storage
[2530.12 --> 2530.28] and
[2530.28 --> 2530.46] data
[2530.46 --> 2531.02] structure.
[2531.74 --> 2532.94] Go tools
[2532.94 --> 2533.98] like the
[2533.98 --> 2534.30] REND