text stringlengths 0 1.62k |
|---|
[2911.26 --> 2915.10] innovation happens in the standard library and one of the things i liked about rust when i got |
[2915.10 --> 2920.48] involved early on was even at that point there was a there was a lot of interest in taking things that |
[2920.48 --> 2926.30] were hard-coded like the garbage collection type or um exactly how uh smart pointers work and make |
[2926.30 --> 2932.22] them things that you could experiment with in in in the ecosystem right as libraries um so first that |
[2932.22 --> 2938.16] was just making them libraries in rust itself but by by having cargo and creates.io a lot of the things |
[2938.16 --> 2942.30] that used to be in the standard library are still maintained by the core team but are now cargo |
[2942.30 --> 2950.06] packages and this is this is sort of an idea that i think got got uh explored by both bundler and npm |
[2950.06 --> 2954.20] and a lot of other package managers that came out around that time and what was really awesome about |
[2954.20 --> 2958.48] working on cargo for me was that i got to say okay let's take a look at sort of the effect of that |
[2958.48 --> 2964.20] like how did semver play into that semver turns out to be pretty important npm like adds the idea of |
[2964.20 --> 2969.32] having duplication right allowing you to have version 1.x of underscore and 2.x of underscore |
[2969.32 --> 2974.00] and having them both work in the same program and rust allows you to do that so how can we how can we |
[2974.00 --> 2980.06] do that how can we do without having massive binary sizes where you have like 57 copies of the glob package |
[2980.06 --> 2985.38] in in your npm projects right people who write uh who write rust programs probably care about binary |
[2985.38 --> 2991.50] size you don't want servo to be four gigabytes large right so um what what's awesome for me about |
[2991.50 --> 2996.50] cargo is that it was at least for me the first opportunity to really go start from scratch in |
[2996.50 --> 3000.74] building a package ecosystem that would take advantage of the fact that rust itself is very good |
[3000.74 --> 3007.70] at letting people do things in user space but also look at like how rust how sorry how bundler and npm |
[3007.70 --> 3015.28] uh made community a thing i uh also github of course right so like npm and bundler both came out around |
[3015.28 --> 3020.86] the time that github was becoming popular but i got to work on cargo after that was over after github is |
[3020.86 --> 3025.40] already popular people know how github works um and and so i i think people the way people should |
[3025.40 --> 3032.14] think about cargo um is that cargo is is basically building on what we learned from the first generation |
[3032.14 --> 3036.48] after github so it's like attempting to be a second generation after github package manager |
[3036.48 --> 3042.30] that is awesome and i think this is like for me this is like the big news about open source is that |
[3042.30 --> 3047.86] this works like you can have a packet ecosystem you can have user land experimentation um and you can make |
[3047.86 --> 3054.22] you can make that work in the context of a big a big ecosystem you know one thing that uh something |
[3054.22 --> 3059.34] you said that you would remind me back to 131 we had you and tom on to talk about the road to ember |
[3059.34 --> 3063.66] 2.0 was this that how you've learned from and i think it just seems like common knowledge but |
[3063.66 --> 3068.22] you've learned from things that happened elsewhere in other communities that were done well |
[3068.22 --> 3072.66] and implemented in the current community that you're doing your work in so in this case |
[3072.66 --> 3077.28] learning from github learning from npm in terms of a package package manager in the community and |
[3077.28 --> 3083.74] the importance here in rust um i just sort of made me reference back to to that i'm just also |
[3083.74 --> 3091.38] wondering if we could expect the cargo ink uh no definitely no cargo ink um but i think i think it's |
[3091.38 --> 3096.34] interesting that so dhh a long time ago had a blog post that said why there is no rails ink and |
[3096.34 --> 3100.32] that's still like i never actually print it out and put it on my wall but i kind of want to print |
[3100.32 --> 3105.02] that out and put it on my wall um about open source we do too yeah we go back to that one so |
[3105.02 --> 3110.48] that's like really like really important to me but when rails was first coming out it actually |
[3110.48 --> 3116.06] wasn't entirely clear how collaboration across the ecosystem was supposed to work like it's one thing |
[3116.06 --> 3120.94] to have like github is awesome github lets people collaborate but dependencies are a real thing right |
[3120.94 --> 3124.52] if you can't have uh if you can't have a thing that depends on something that depends on something |
[3124.52 --> 3128.94] else that depends on something else you can't actually build that high and so uh |
[3128.94 --> 3134.18] between all the things that happened over the past five years we've gone from when i started |
[3134.18 --> 3139.20] doing open source where it was like a huge project to add a dependency so certainly adding a dependency |
[3139.20 --> 3144.22] of a dependency was was almost intractable and then a dependency of a dependency of a dependency was |
[3144.22 --> 3148.90] basically like no literally nobody ever did that in the in the open source communities that i was part |
[3148.90 --> 3154.14] of to now where it's sort of it's the way it works right you expect to be able to build large stacks |
[3154.14 --> 3158.36] of your land of distractions you expect to not need betters included in the core you expect the |
[3158.36 --> 3163.16] core to stay small and nimble and focus on capabilities um this is also like the extensive |
[3163.16 --> 3168.92] web manifesto is trying to make that the way the web works and this is like i think it's kind of like |
[3168.92 --> 3173.62] to me the singularity right it's like figuring out that you can totally change the shape of iteration |
[3173.62 --> 3178.30] the iteration is not just uh like you can change the speed of iteration by making people work faster |
[3178.30 --> 3184.18] but you can only change the shape of iteration if the actual process of iteration changes and in our |
[3184.18 --> 3188.52] case having dependencies and dependencies dependencies making it so that anybody can work |
[3188.52 --> 3193.32] collaboratively work together like the shape of iteration has changed significantly and it's making |
[3193.32 --> 3197.72] things go much faster and that's awesome so i was happy to be able to make that a part of rust |
[3197.72 --> 3202.30] because i think like for me like the mind the most mind-blowing thing about rust we didn't talk about |
[3202.30 --> 3207.82] at all is the fact that you can have a browser like a web browser servo that is built using |
[3207.82 --> 3212.56] of the library package manager like the language is package manager you the way you build servos you |
[3212.56 --> 3217.38] download you get clone and then you run cargo build and that's like the way you build anything |
[3217.38 --> 3222.06] else and like what does that mean it means that they extract all kinds of stuff from inside servo |
[3222.06 --> 3226.24] their coding library their image processing these are all just off-the-shelf libraries that anyone |
[3226.24 --> 3230.36] can use for their own projects and they're all built together put together using the same approach |
[3230.36 --> 3235.32] and that like that's new like c++ doesn't have that c doesn't have that it's like a totally new thing |
[3235.32 --> 3242.16] so i guess fast forwarding a little bit to today a great day today april 3rd this is from the core |
[3242.16 --> 3246.56] team the whole entire rust core team so there is no byline that says steve wrote this yahuda wrote |
[3246.56 --> 3253.80] this or someone else wrote this a great announcement today rust 1.0 beta um what does it mean i guess |
[3253.80 --> 3259.82] you got 172 contributors for this release what does it mean for the community to have 1.0 here what |
[3259.82 --> 3264.02] does it mean to when you put the label beta on there in terms of what's out there now and how it |
[3264.02 --> 3268.98] would be used so the big step here is that historically speaking we've only had one release |
[3268.98 --> 3274.98] of the compiler and that's nightly every night a new compiler comes out um with today's release beta |
[3274.98 --> 3279.22] there's now two versions of the compiler the nightly version which continues to be put out every night |
[3279.22 --> 3284.22] and then the beta version which was released today uh tomorrow there will be a new nightly but there will |
[3284.22 --> 3290.68] probably not be a new beta um and so the way that this works is uh six weeks from now probably |
[3290.68 --> 3294.62] probably there's some there's some i want to hand wave slightly you know if we find something |
[3294.62 --> 3300.34] catastrophic we fix it immediately or whatever but the idea is that six weeks from today there will |
[3300.34 --> 3306.04] be a release of one point rust 1.0 final and so what happens at that point is the beta becomes the final |
[3306.04 --> 3312.20] and the nightly on that night becomes the new beta so so like nightly turns along every single night |
[3312.20 --> 3317.44] and then every six weeks we have a new release of the like pre-testing branch and then the actual |
[3317.44 --> 3322.20] release branch and so uh that's the first thing is this is the first step towards those kind of like |
[3322.20 --> 3327.20] train model which was originally pioneered by you know chrome and firefox and it's also used in ember |
[3327.20 --> 3333.46] um but the other thing that's a side effect of that is the beta channel comes with stability guarantees |
[3333.46 --> 3340.08] which we have never ever guaranteed basically any kind of stability whatsoever over the eight years of |
[3340.08 --> 3346.72] rust's development and so that's like the big major changes is that we're saying we still may change |
[3346.72 --> 3353.26] some small things but basically this is representative of the actual 1.0 final release which will have |
[3353.26 --> 3358.94] total backwards well total maybe a little strong but like drop-in replacement like 1.1 should be a |
[3358.94 --> 3364.70] drop-in replacement for 1.0 so we're offering very strong backwards compatibility guarantees yeah i think |
[3364.70 --> 3370.06] one way to think about it is that 1.0 beta is actually not different from 1.1 beta or 1.2 beta or 1.2 |
[3370.06 --> 3375.62] and uh for people who are not familiar steve talked about this but this is basically how browsers |
[3375.62 --> 3380.72] work and in my view this is the future like ember does it now rust does it in my view this is this is |
[3380.72 --> 3385.14] how you should do it how you should i'll be doing it for all my projects in the future it's awesome so |
[3385.14 --> 3391.44] but the the basic idea that there is uh you ship every six weeks but you also ship a staggered beta |
[3391.44 --> 3396.12] release and that beta release is extremely stable it's only the features that have been approved that |
[3396.12 --> 3399.70] are actually ready to go and you're just getting some feedback you have these you have nightlies that |
[3399.70 --> 3404.72] people can subscribe to and and the really awesome thing for me about all this stuff is that it lets |
[3404.72 --> 3410.58] people subscribe to a channel that is appropriate for their level of stability uh reliance right so |
[3410.58 --> 3414.82] some people might be unwilling to ever have instability they need to just keep rolling and |
[3414.82 --> 3419.84] those people should just use the the release channel right but some people want the new features as soon |
[3419.84 --> 3423.70] as they're basically ready maybe there's not they're not stability guaranteed yet but they're basically |
[3423.70 --> 3427.60] ready those people choose the beta channel and some people really want to be bleeding edge those people |
[3427.60 --> 3431.82] to use the nightly channel and the thing that's awesome about this is that it doesn't you can the |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.