text
stringlengths
0
2.35k
[701.70 --> 702.52] you come from Java.
[702.66 --> 703.46] You probably don't know
[703.46 --> 703.92] how to go.
[704.66 --> 705.38] Never mind.
[705.66 --> 706.64] Forget about it.
[707.08 --> 708.52] This will take some time
[708.52 --> 709.76] and it doesn't matter.
[709.92 --> 710.96] They could have 20 years
[710.96 --> 711.76] of experience
[711.76 --> 713.92] and still look at them
[713.92 --> 714.14] like,
[714.54 --> 715.36] but do you know Go?
[715.90 --> 716.32] Do you?
[717.00 --> 717.44] So,
[717.60 --> 718.48] that's where I am.
[718.62 --> 719.68] I am curious though
[719.68 --> 720.64] if we're getting any
[720.64 --> 721.84] remarks from our listeners.
[722.32 --> 722.54] So,
[722.88 --> 723.58] maybe they have
[723.58 --> 724.40] some opinions.
[724.68 --> 725.58] Not just yet.
[725.68 --> 726.32] Not just yet.
[726.36 --> 727.70] But maybe any minute now.
[727.90 --> 728.28] Hopefully.
[728.74 --> 729.74] One can only hope.
[730.78 --> 731.64] I'll be curious to hear
[731.64 --> 732.94] what are some of the
[732.94 --> 734.60] feedbacks that you got
[734.60 --> 735.58] over the email.
[735.76 --> 735.80] Like,
[735.84 --> 736.70] what are the
[736.70 --> 738.38] pros
[738.38 --> 739.20] or the people
[739.20 --> 740.26] who agreed or disagreed?
[740.36 --> 741.18] You said that they were
[741.18 --> 742.60] all backing their claims
[742.60 --> 743.34] which is wonderful.
[743.52 --> 744.42] It means you have
[744.42 --> 745.34] generally a great
[745.34 --> 746.44] discussion.
[746.70 --> 746.98] Well,
[747.10 --> 747.42] I mean,
[747.60 --> 748.46] so there is
[748.46 --> 749.50] expected practices.
[749.64 --> 750.42] What was the term you used?
[750.58 --> 751.16] Common practices.
[751.86 --> 752.80] And that's great.
[752.92 --> 753.02] So,
[753.26 --> 753.78] tell us about them.
[754.08 --> 754.22] Well,
[754.26 --> 755.04] the first comment
[755.04 --> 755.96] that I got was,
[756.42 --> 757.50] that was really funny,
[758.00 --> 758.22] was,
[758.38 --> 759.28] aren't generics enough?
[759.54 --> 760.34] OOP now?
[760.52 --> 760.70] Really?
[761.36 --> 762.28] Something like that.
[763.32 --> 764.64] I thought that was hilarious.
[765.40 --> 765.68] So,
[765.90 --> 767.70] people do refer me a lot.
[768.38 --> 770.04] to the Go FAQs
[770.04 --> 771.38] that specifically say
[771.38 --> 772.12] that the answer
[772.12 --> 773.12] to whether Go
[773.12 --> 774.30] is object-oriented
[774.30 --> 774.90] or not
[774.90 --> 776.66] is yes and no.
[778.02 --> 778.92] And then,
[779.28 --> 779.62] no,
[779.70 --> 779.98] actually,
[780.14 --> 781.28] is it a yes and no?
[781.52 --> 781.76] Or,
[781.92 --> 782.48] I don't remember.
[782.82 --> 784.08] I actually prepared it for you.
[784.16 --> 785.04] Let me read this out.
[785.18 --> 785.72] Oh, amazing.
[786.28 --> 786.94] Yes and no.
[787.24 --> 788.36] Although Go has
[788.36 --> 789.24] types and methods
[789.24 --> 790.82] and allows an object-oriented
[790.82 --> 791.78] style of programming,
[792.06 --> 793.34] there is no type hierarchy.
[793.92 --> 795.72] The concept of interface
[795.72 --> 796.58] in Go provides
[796.58 --> 797.62] a different approach
[797.62 --> 798.40] that we believe
[798.40 --> 799.42] is easy to use
[799.42 --> 800.12] and in some ways
[800.12 --> 800.72] more general.
[801.48 --> 802.68] There are also ways
[802.68 --> 803.68] to embed types
[803.68 --> 804.48] in other types
[804.48 --> 805.38] to provide something
[805.38 --> 806.14] analogous
[806.14 --> 807.08] but not identical
[807.08 --> 808.56] to subclassic.
[808.98 --> 809.54] Moreover,
[810.06 --> 810.76] methods in Go