Datasets:
willtheorangeguy
/
2022-Go-Time-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
2.35k
[1537.60 --> 1538.22] bit of a
[1538.22 --> 1538.88] thread.
[1539.36 --> 1539.94] So it starts
[1539.94 --> 1540.46] with whenever
[1540.46 --> 1541.08] someone from
[1541.08 --> 1541.52] Java or
[1541.52 --> 1542.20] C++ or
[1542.20 --> 1542.68] C Sharp
[1542.68 --> 1544.82] comes to
[1544.82 --> 1545.02] Go,
[1545.16 --> 1545.58] they look for
[1545.58 --> 1545.94] class,
[1546.06 --> 1546.54] find struct
[1546.54 --> 1547.00] and stop
[1547.00 --> 1547.44] looking.
[1547.84 --> 1548.26] But this
[1548.26 --> 1548.78] misses two
[1548.78 --> 1549.38] fundamental
[1549.38 --> 1549.92] differences
[1549.92 --> 1550.54] between Go
[1550.54 --> 1551.54] and traditional
[1551.54 --> 1552.50] object-oriented
[1552.50 --> 1552.98] languages.
[1553.58 --> 1554.18] The first
[1554.18 --> 1554.70] one is that
[1554.70 --> 1555.04] it's not
[1555.04 --> 1555.84] only structs.
[1556.06 --> 1556.74] Any concrete
[1556.74 --> 1557.66] type can have
[1557.66 --> 1558.24] methods.
[1558.24 --> 1558.88] integers,
[1559.18 --> 1559.48] balls,
[1559.74 --> 1560.06] slices,
[1560.28 --> 1560.88] even funks.
[1561.32 --> 1561.94] But the
[1561.94 --> 1562.64] more important
[1562.64 --> 1563.86] idea is the
[1563.86 --> 1564.42] separation of
[1564.42 --> 1564.84] concepts.
[1564.98 --> 1565.40] Data and
[1565.40 --> 1566.00] behavior are
[1566.00 --> 1566.84] two distinct
[1566.84 --> 1567.42] concepts of
[1567.42 --> 1567.64] Go,
[1568.14 --> 1568.84] not conflated
[1568.84 --> 1569.44] into a single
[1569.44 --> 1569.98] notion of
[1569.98 --> 1570.42] class.
[1570.82 --> 1571.88] This is the
[1571.88 --> 1572.58] insight which
[1572.58 --> 1573.18] goes all the
[1573.18 --> 1573.70] way back to
[1573.70 --> 1574.70] small talk on
[1574.70 --> 1575.50] which the
[1575.50 --> 1576.32] object-oriented
[1576.32 --> 1577.10] type system,
[1577.24 --> 1577.76] including the
[1577.76 --> 1578.46] interface model,
[1578.58 --> 1578.98] is built.
[1579.40 --> 1579.70] So stopping
[1579.70 --> 1580.30] at struct
[1580.30 --> 1581.52] equals equals
[1581.52 --> 1582.58] class misses
[1582.58 --> 1583.86] much of what
[1583.86 --> 1584.50] makes Go
[1584.50 --> 1584.94] work.
[1584.94 --> 1585.66] So what
[1585.66 --> 1585.88] are your
[1585.88 --> 1586.20] thoughts?
[1586.60 --> 1587.18] I agree.
[1587.78 --> 1588.38] It sort of
[1588.38 --> 1589.00] works very
[1589.00 --> 1589.46] well with
[1589.46 --> 1590.10] everything that
[1590.10 --> 1591.02] I learned
[1591.02 --> 1592.14] recently about
[1592.14 --> 1592.52] this.
[1592.74 --> 1593.12] Honestly,
[1593.58 --> 1594.80] it feels like
[1594.80 --> 1595.72] Go is more
[1595.72 --> 1597.24] naturally object-oriented
[1597.24 --> 1599.16] than languages
[1599.16 --> 1600.00] that I worked
[1600.00 --> 1601.38] with before.
[1601.96 --> 1602.42] I had this
[1602.42 --> 1603.06] discussion with
[1603.06 --> 1603.66] my boyfriend
[1603.66 --> 1604.52] because of the
[1604.52 --> 1605.42] workshop and the
[1605.42 --> 1605.76] amount of
[1605.76 --> 1606.64] resistance that I
[1606.64 --> 1607.12] was getting.
[1607.50 --> 1608.14] Does he think
[1608.14 --> 1610.00] Go is object-oriented?
[1610.36 --> 1610.66] Yes.
[1611.04 --> 1611.86] So his answer
[1611.86 --> 1612.64] was, of course
[1612.64 --> 1613.06] it is.
[1613.62 --> 1614.88] It wasn't even a
[1614.88 --> 1615.58] question in his