text stringlengths 0 1.32k |
|---|
[1857.48 --> 1859.94] Would be, you know, very premature. |
[1860.14 --> 1860.98] So what do you do then? |
[1861.00 --> 1862.24] You just offer both? |
[1862.42 --> 1862.78] Both. |
[1862.94 --> 1863.10] Yeah. |
[1863.42 --> 1863.62] Yeah. |
[1863.68 --> 1868.58] And just say that, you know, Node is going to be a platform for HTTP development. |
[1868.92 --> 1869.10] Right. |
[1869.20 --> 1869.72] One and two. |
[1870.16 --> 1870.40] Right. |
[1870.40 --> 1877.76] And there will be mechanism that's built into the H2 specification that you can actually run H1 and H2 on the same port. |
[1878.46 --> 1880.40] You know, you can have a server that will offer both. |
[1880.58 --> 1883.34] And the client negotiates which one they want to use per socket. |
[1884.28 --> 1888.12] We're not quite there yet in terms of how we're going to figure out how to make that work in Node. |
[1888.22 --> 1893.04] But, you know, that's a key capability of H2. |
[1893.04 --> 1902.16] So if we are going to fully implement that spec, that means also implementing that upgrade path, which means we can't necessarily get rid of H1. |
[1902.40 --> 1902.56] Yeah. |
[1902.56 --> 1905.76] And the fact of the matter is we can't get rid of anything in core. |
[1906.16 --> 1906.32] Right. |
[1906.44 --> 1911.88] I mean, you see that, you know, in things like the recent buffer discussions, whether we deprecate, you know, things. |
[1911.88 --> 1923.04] We just we can't get rid of things that are that are so critical to what the Node ecosystem is doing that even having a deprecation message in there is problematic. |
[1923.04 --> 1923.48] Yeah. |
[1924.00 --> 1930.28] And something so fundamental as H1, I don't think we would ever get to a point where we would fully deprecate. |
[1930.82 --> 1947.34] I'll retract that deprecation statement and say it more like instead, because when we were having that discussion about the options of deprecating things was not to put it in where it was a response, but more so in like documentation where it was frowned upon. |
[1947.66 --> 1949.46] You know, it wasn't forced. |
[1949.46 --> 1952.90] And then you're obviously so much more closer. |
[1952.98 --> 1954.60] So I'm just outside of looking in. |
[1954.70 --> 1960.38] But I'm thinking, like, if it's so deliberate to choose it, wouldn't it make sense or potentially make sense? |
[1960.44 --> 1964.90] And this would be a decision you will eventually make to offer it as a module instead. |
[1965.16 --> 1968.64] That way you can have a clean break when it is time to move over. |
[1968.78 --> 1972.58] I'm just thinking if it's that deliberate, why not make it that deliberate where it's actually a require? |
[1972.58 --> 1976.74] Well, I mean, it's a legitimate, you know, it's a legitimate question. |
[1976.74 --> 1980.72] And that's actually one of the decisions the CTC has to make. |
[1980.86 --> 1983.52] You know, I have an opinion on it. |
[1983.90 --> 1988.96] But, you know, unfortunately, it's not just all up to me. |
[1989.60 --> 1990.02] Right. |
[1990.10 --> 1997.22] We have to listen to, you know, folks like Sam and Thomas and the ecosystem and figure out what is the right approach to take. |
[1997.22 --> 2002.70] And we're not close enough yet to reaching that decision. |
[2003.08 --> 2003.28] Right. |
[2003.34 --> 2014.32] So I'm being very deliberate in how I write this code to ensure that if we need to pull it out, if that ends up being the right thing to do, we can. |
[2015.44 --> 2018.92] You know, it's not making breaking changes to any existing part of node. |
[2018.92 --> 2024.58] It is a very distinct separate code path from the existing H1 stuff. |
[2026.04 --> 2032.66] You know, it would be a native module, you know, and all the things that come along with native modules, you know, so we'd have, you know, there would be some considerations there. |
[2032.88 --> 2033.06] Right. |
[2033.24 --> 2035.54] But if we needed to, we could. |
[2035.54 --> 2042.16] And, you know, like I said, I have my opinion on what it ultimately should do, but it's up to the community. |
[2042.34 --> 2048.94] It's up to, you know, the core team to make that decision for whatever reasons they want to make that decision. |
[2050.36 --> 2050.76] Cool. |
[2050.84 --> 2055.02] Let's close with any closing thoughts you might have on this subject. |
[2055.12 --> 2059.34] Anything I might not have asked you that you're like, I got to put this out there before we close down. |
[2059.50 --> 2062.54] Oh, you know, we've really covered, you know, a lot of it. |
[2062.54 --> 2070.94] I mean, kind of the big thing I would say is, you know, if the folks are really passionate about this, we need to hear from users. |
[2071.08 --> 2080.02] We need to hear from folks that, you know, that, you know, have ideas on how to implement it, right, or how to test or what kind of applications they want to build with this thing. |
[2080.48 --> 2084.78] I've had a lot of conversations so far, but, you know, it's a big ecosystem. |
[2085.00 --> 2086.30] There's a lot of people out there. |
[2086.30 --> 2086.60] Right. |
[2086.60 --> 2092.72] You know, so, you know, we can't have enough input on that direction. |
[2093.28 --> 2101.92] That information, that input is what's going to help drive that decision of what's going to happen with this code, right? |
[2102.52 --> 2104.22] What's the best way for people to reach out to you then? |
[2104.32 --> 2106.34] Like, if it's feedback you want, is it you personally? |
[2106.52 --> 2107.82] Is it, should they go to the repo? |
[2107.82 --> 2109.04] Go to the repo. |
[2109.14 --> 2109.66] Go to the repo. |
[2109.80 --> 2113.94] Open issues, you know, for the folks that really want to, like, you know, get in there. |
[2114.06 --> 2115.42] You know, pull requests are great. |
[2116.16 --> 2118.52] I've been making, there's been a lot of churn in the code. |
[2118.62 --> 2121.84] I've been getting in there and just, like, you know, hammering away at it for the past few weeks. |
[2121.96 --> 2122.42] With the machete? |
[2122.84 --> 2123.54] Yeah, pretty much. |
[2124.00 --> 2127.36] People have been asking, you know, it's like, well, where are the two do so we know where to jump in? |
[2127.40 --> 2132.74] It's like, well, I don't even know what the heck I'm going to do tomorrow, let alone what they recommend you jump in on. |
[2133.20 --> 2136.06] But, you know, it's starting to stabilize more. |
[2136.06 --> 2143.02] And there are very distinct areas that I know for sure, you know, tests, performance benchmarks, you know, those kinds of things. |
[2143.16 --> 2143.34] Right. |
[2143.48 --> 2147.20] That, you know, absolutely could use some help on. |
[2147.94 --> 2151.04] So anyone that wants to jump in, just go to that repo. |
[2151.26 --> 2152.16] Take a look at what's happening. |
[2152.16 --> 2153.06] Testing performance, things like that. |
[2153.12 --> 2153.36] Right. |
[2153.52 --> 2153.76] Okay. |
[2153.76 --> 2157.56] Well, we'll link up the repo in the show notes for this. |
[2157.86 --> 2163.38] And, James, thanks so much for, we're closing down, literally closing down Node Interactive. |
[2163.66 --> 2163.76] Oh, yeah. |
[2164.26 --> 2166.48] So thank you so much for taking the time to speak with me. |
[2166.86 --> 2167.16] Oh, yeah. |
[2167.16 --> 2168.46] It's important that we have this conversation. |
[2168.62 --> 2171.94] So I know that the Node community is going to appreciate what you have to say. |
[2172.12 --> 2172.44] Right on. |
[2172.60 --> 2172.82] Right on. |
[2172.88 --> 2173.28] Thanks, man. |
[2173.44 --> 2173.66] Thanks. |
[2176.16 --> 2181.90] Thanks again to our friends at the Linux Foundation and the Node Foundation for working with us on this project, |
[2181.90 --> 2185.94] as well as our friends at IBM and Strongloop for sponsoring this podcast series. |
[2186.26 --> 2187.44] It was a blast being there. |
[2187.70 --> 2188.88] We'll be there again next year. |
[2188.94 --> 2192.16] So look out for us in 2017 at Node Interactive. |
[2192.54 --> 2196.94] If you want to hear more JavaScript-focused podcasts from Changelog, check out JS Party, |
[2197.18 --> 2202.54] our new live weekly show with Michael Rogers, Alex Sexton, and Rachel White. |
[2202.94 --> 2205.38] Head to changelog.com slash JS Party. |
[2205.78 --> 2206.40] Click subscribe. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.