text
stringlengths
0
2.35k
[2592.54 --> 2594.52] is not
[2594.52 --> 2595.50] maintainable code.
[2596.18 --> 2596.56] So,
[2596.78 --> 2597.32] letting go,
[2597.32 --> 2598.08] Go has
[2598.08 --> 2598.52] been written
[2598.52 --> 2599.08] in a way
[2599.08 --> 2599.60] that should
[2599.60 --> 2600.18] allow us
[2600.18 --> 2601.00] to utilize
[2601.00 --> 2601.80] all the
[2601.80 --> 2602.20] features.
[2603.14 --> 2603.76] So, the
[2603.76 --> 2604.32] idea that
[2604.32 --> 2604.96] people don't
[2604.96 --> 2606.38] do it is,
[2606.94 --> 2607.26] well, she
[2607.26 --> 2608.06] said, I
[2608.06 --> 2608.42] don't know
[2608.42 --> 2608.72] what to
[2608.72 --> 2610.30] say else
[2610.30 --> 2610.82] about it.
[2610.82 --> 2611.42] What are
[2611.42 --> 2611.88] some good
[2611.88 --> 2612.94] or bad
[2612.94 --> 2613.80] use cases
[2613.80 --> 2614.64] for using
[2614.64 --> 2615.00] that?
[2615.34 --> 2615.86] Like, you
[2615.86 --> 2616.26] mentioned,
[2616.52 --> 2617.02] billing is
[2617.02 --> 2617.80] your close
[2617.80 --> 2618.10] to home
[2618.10 --> 2618.60] example.
[2619.06 --> 2619.24] Do you
[2619.24 --> 2619.66] have some
[2619.66 --> 2621.50] other use
[2621.50 --> 2621.94] cases you
[2621.94 --> 2622.18] would say
[2622.18 --> 2622.90] definitely use
[2622.90 --> 2623.12] it or
[2623.12 --> 2623.48] definitely
[2623.48 --> 2623.94] don't?
[2623.94 --> 2625.24] So, the
[2625.24 --> 2625.84] quote that
[2625.84 --> 2627.18] Rob Pike,
[2627.50 --> 2627.80] that I
[2627.80 --> 2628.08] think
[2628.08 --> 2628.70] whatever,
[2629.00 --> 2629.34] whomever
[2629.34 --> 2630.10] sent me
[2630.10 --> 2631.08] the message
[2631.08 --> 2631.80] was basing
[2631.80 --> 2632.34] it on,
[2632.58 --> 2633.08] he said
[2633.08 --> 2633.60] that, I
[2633.60 --> 2633.88] don't know,
[2633.96 --> 2634.40] there were
[2634.40 --> 2635.26] multiple,
[2635.76 --> 2636.56] a professor
[2636.56 --> 2637.30] used multiple
[2637.30 --> 2638.18] classes to
[2638.18 --> 2638.82] perform something
[2638.82 --> 2639.24] that was a
[2639.24 --> 2639.96] simple lookup.
[2640.50 --> 2641.26] And I think
[2641.26 --> 2641.90] this is it.
[2641.98 --> 2642.50] And I also
[2642.50 --> 2643.36] understand why
[2643.36 --> 2643.96] it happened.
[2644.84 --> 2645.30] But again,
[2645.38 --> 2645.92] it's not
[2645.92 --> 2646.24] Go,
[2646.40 --> 2646.86] actually.
[2647.68 --> 2648.70] So, again,
[2648.76 --> 2649.22] when we go
[2649.22 --> 2649.98] back to
[2649.98 --> 2651.52] Java,
[2652.34 --> 2652.82] you are not
[2652.82 --> 2653.56] able to
[2653.56 --> 2654.30] say that
[2654.30 --> 2655.14] A is B
[2655.14 --> 2655.88] unless A is
[2655.88 --> 2656.54] aware of B
[2656.54 --> 2657.42] and knows
[2657.42 --> 2657.66] that it
[2657.66 --> 2658.32] implements B.
[2658.82 --> 2659.22] So, you
[2659.22 --> 2659.78] can't really
[2659.78 --> 2660.36] say that A
[2660.36 --> 2660.76] is B.
[2661.36 --> 2661.82] And then in
[2661.82 --> 2662.32] those languages,
[2662.32 --> 2662.74] you really
[2662.74 --> 2663.54] have to work
[2663.54 --> 2664.98] extra hard
[2664.98 --> 2666.70] to express
[2666.70 --> 2667.24] the idea
[2667.24 --> 2667.66] that A
[2667.66 --> 2668.00] is B.