Datasets:
willtheorangeguy
/
2017-Spotlight-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
1.32k
[1498.16 --> 1502.08] The downside of that was it was using significantly more memory, right?
[1502.34 --> 1506.46] But it had a better success rate, right?
[1506.48 --> 1511.24] And it was using the bandwidth much more efficiently.
[1511.24 --> 1520.60] And the header compression, for example, we were able to save 96% of the header bytes, you know, compared to H1, right?
[1520.78 --> 1528.92] So, you know, actually it's 96% fewer header bytes sent over the wire with 100,000 requests.
[1529.38 --> 1531.20] That's a massive savings, right?
[1531.38 --> 1540.40] And if you're looking at the platform as a service where people are paying for bandwidth, you know, paying for this stuff, saving that much is significant.
[1540.40 --> 1540.90] A lot of money.
[1541.06 --> 1541.26] Right.
[1541.82 --> 1542.96] They'll spend that money in memory, though.
[1543.20 --> 1543.94] Yeah, yeah, yeah.
[1544.68 --> 1546.28] They'll make up for it in other ways.
[1547.26 --> 1552.12] And, you know, that increase in performance is significant.
[1552.24 --> 1553.20] You can't discount it.
[1553.56 --> 1558.76] There is, with the fact that TLS is there, it's required, there is an improvement in security.
[1559.24 --> 1561.00] But there are definite trade-offs.
[1561.30 --> 1566.86] And anyone looking to adopt H2 has to be aware of what those trade-offs are.
[1566.86 --> 1576.14] And it's something that, as we're going through in core, trying to figure this thing out, there's also going to be trade-offs in terms of API, right?
[1577.56 --> 1589.84] And one, like, simple example is the fact that the status message in H1, you know, how you have, like, the preamble on a response, HP, you know, 1.1, 200, OK.
[1589.84 --> 1594.00] That OK doesn't exist in H2.
[1594.74 --> 1597.58] They completely remove the status message, right?
[1597.66 --> 1600.02] So no more 404 not found.
[1600.16 --> 1602.08] It's just 404, right?
[1602.28 --> 1604.04] No more 500 server error.
[1604.38 --> 1605.72] There's no server error, right?
[1606.04 --> 1607.62] There is no standard way.
[1607.70 --> 1608.18] Just the number.
[1608.42 --> 1608.54] Yeah.
[1608.78 --> 1611.20] There's no standard way of conveying the status message.
[1611.64 --> 1613.36] They just completely removed it from the protocol.
[1613.36 --> 1621.92] Well, there are existing applications out there that use the status message, right, and actually put content there that the clients read.
[1622.26 --> 1624.18] Now, it's not recommended, right?
[1624.30 --> 1634.30] And H1 spec, you know, doesn't assign any semantics, reliable semantics, that anyone should use to, like, say, hey, that's a thing we should use.
[1634.74 --> 1638.40] But as users do, they'll use whatever's available to them, right?
[1638.40 --> 1641.66] That's a bummer because people will stop saying 200, OK, now they'll just say 200.
[1641.66 --> 1642.92] They'll say 200, right, right.
[1642.92 --> 1645.24] The 404 not found, the whole jokes, you know.
[1645.44 --> 1645.62] Right, right.
[1645.70 --> 1646.60] Nobody will get it anymore.
[1647.84 --> 1655.52] So if you look at nodes API or things like Express, you know, they have, like, you know, here's how you set the status message.
[1656.22 --> 1660.26] Well, that's a breaking change in those APIs when you go to H2.
[1660.26 --> 1673.82] So we have to make a decision of how closely does the H2 API have to match the H1 API and act the same way when we know that there are distinct differences that mean it can't.
[1673.82 --> 1678.32] So it makes upgrading or changing to H2 a very deliberate choice.
[1678.50 --> 1678.56] Yeah.
[1679.20 --> 1680.58] It's going to have to be very deliberate.
[1680.92 --> 1687.80] And it's only going to be in very simple, simple scenarios, which probably aren't realistic, that somebody would be able to say, OK, it works in both.
[1688.24 --> 1688.50] Right.
[1688.50 --> 1696.88] It's going to be a thing where you have to design your application specifically for H2 in order to take advantage of the capabilities of the event.
[1696.88 --> 1698.28] It's kind of putting a high barrier in front of it, too.
[1698.36 --> 1707.46] I mean, you can't expect adoption of what is, as you said, a better performing protocol if you put a mountain in front of it.
[1707.56 --> 1707.76] Right.
[1708.08 --> 1708.24] Right.
[1708.24 --> 1710.26] No one's going to want to climb that.
[1710.64 --> 1715.48] Or it's less enjoyable or less likely or whatever.
[1715.62 --> 1716.46] People do it.
[1716.66 --> 1719.04] We have lots of people that say they really want this.
[1719.20 --> 1720.34] They really want H2.
[1720.52 --> 1726.38] And we have a lot of people that are talking about it not necessarily for user-facing, right?
[1726.58 --> 1729.42] Setting up websites that anyone on the Internet can access.
[1729.42 --> 1738.98] They want to put it in their data center and have server-to-server communication be much more efficient, which is a huge use case for H2.
[1739.46 --> 1750.54] Especially since that is within protected environments and you have more control over what the client and a server, there's opportunities there where you don't have to necessarily worry about TLS.
[1750.76 --> 1755.20] You can do a plain text connection and you'll get far greater performance out of it.
[1755.68 --> 1757.56] But, again, it has to be a very deliberate choice.
[1757.56 --> 1758.28] Right.
[1758.68 --> 1763.02] So H2, is this something that you're solely working on or do you have a team working on it with you?
[1764.14 --> 1766.04] Right now, it's been primarily myself.
[1766.18 --> 1768.56] I'm working on kind of growing that team of contributors.
[1769.34 --> 1771.40] Is it in IBM or is it open source contributors?
[1771.46 --> 1772.32] It's open source.
[1772.48 --> 1775.42] I'm doing everything out in the open out on the GitHub repo.
[1775.42 --> 1776.32] Is it on your user then?
[1777.00 --> 1779.04] We're doing it under the Node organization.
[1779.36 --> 1786.50] So if you go github.com, node.js, slash HTTP2, all the work's being done there.
[1786.50 --> 1789.46] I saw that repo there, but I saw Ryan Dahl in there.
[1789.60 --> 1790.66] So this is not a new repo?
[1791.16 --> 1794.42] So it's a clone of the Node core.
[1794.66 --> 1794.84] Okay.
[1794.84 --> 1794.98] Right?
[1795.12 --> 1799.92] So even though the decision hasn't been made to get it into core yet.
[1799.98 --> 1800.24] Right.
[1800.34 --> 1801.36] You're assuming it is.
[1801.36 --> 1802.80] Assuming it is and developing it this.
[1803.04 --> 1803.46] I'm falling.
[1803.46 --> 1804.38] I was wondering why.
[1804.48 --> 1806.14] I was like, I expected it to be a module.
[1806.86 --> 1807.84] But then again.
[1807.94 --> 1815.28] Well, it's being implemented in such a way that we could easily extract it out as a native module if we needed to, if that decision was made.
[1815.62 --> 1815.72] Right.
[1816.12 --> 1818.62] It doesn't, I think, I can't say it doesn't use any.
[1818.62 --> 1820.96] With all this change, wouldn't it make sense just to cut the cord?
[1820.96 --> 1827.56] And, you know, one thing Thomas and Sam were talking about was verbally and documentation-wise deprecate it.
[1827.62 --> 1833.12] Don't do anything to the way it responds or, you know, using anything within Node core.
[1833.40 --> 1835.42] Why not just verbally deprecate it and then?
[1835.60 --> 1838.20] It's way too early for us to do that.
[1839.08 --> 1842.24] AH2 is a very immature protocol.
[1842.24 --> 1842.76] Right.
[1843.48 --> 1845.50] It still has to be proven.
[1845.86 --> 1849.26] And the vast majority of the web is still driven by H1.
[1851.38 --> 1856.68] Going out there and saying that, okay, we're going to deprecate this when H2 has not yet been proven.
[1857.00 --> 1857.30] Right.