text stringlengths 0 1.36k |
|---|
**Mikeal Rogers:** What? |
**Alex Sexton:** The GitHub Octocat shadow person waves at you. |
**Mikeal Rogers:** Oh yeah, I've used that embed before. |
**Alex Sexton:** Oh, I haven't, so... |
**Mikeal Rogers:** I think I used that one in Roll Call, actually. |
**Alex Sexton:** "I'm Mikeal. I knew about everything beforehand." |
**Mikeal Rogers:** \[laughs\] That's the hipster JavaScript going on... I was into it before it was cool. |
**Jessica Lord:** Yeah... That's why JavaScript bread is over now. |
**Mikeal Rogers:** \[laughs\] Okay... Before we beat the horse to death, why don't we get into our picks? Does everybody have their personal picks ready? |
**Jessica Lord:** Oh, gosh... I knew this was coming... |
**Mikeal Rogers:** \[laughs\] Alex, do you wanna kick us off? |
**Alex Sexton:** Uhm... Nope. Let's take a small break. |
**Mikeal Rogers:** \[39:56\] \[laughs\] No, we don't need a break. So I have mine ready... Yeah, I let everybody know on the internets that I'm gonna be leaving the Node.js Foundation; there's a little blog post about it, and stuff like that. But yeah, after a few years of leading the foundation since we've started it,... |
And the project is in very good hands... Everything is very, very good. It's a very positive thing. But yeah, I just want everybody to know that I'm gonna be unemployed, and... |
**James Snell:** Come to Austin! |
**Mikeal Rogers:** Is that where unemployed people go to retire? |
**James Snell:** Well, it's warm... It's overly warm... |
**Mikeal Rogers:** \[laughs\] Overly warm... |
**Jessica Lord:** It's warm here in New York, too... |
**Mikeal Rogers:** Yeah, but in the next month or so, that's gonna turn into really muggy -- no, not muggy... Just like really humid and gross -- I've been in New York in the summer, it was not super fun. But I actually am gonna be in New York next month, so... |
**Alex Sexton:** I was talking to someone yesterday and they were talking about how publishing hours often have like a half-day on Friday - like if you work in news at all, or something like that - because everyone who worked in newspapers was rich enough to get the hell out of the city on the weekends, so they'd all p... |
**Mikeal Rogers:** I think I'm gonna slip this into my future employment contract... "I do half-days on Fridays, man..." |
**Alex Sexton:** "I gotta get into the mountains... I don't have A/C." |
**Jessica Lord:** Yeah, in the Bay... Escaping the heat of... |
**Mikeal Rogers:** In the Bay Area, yeah... \[laughter\] Alright, do you all have picks now? Was that enough time for you to think of something? |
**Jessica Lord:** I just went to my Instapaper and three of the top last things I saved were Tad, What's New In npm5 and What's New In Node 8, so I've got nothing... |
**Mikeal Rogers:** \[laughs\] You exhausted the list of things that you have around... |
**Jessica Lord:** Yeah. |
**Mikeal Rogers:** Okay. |
**Alex Sexton:** So maybe I'll do some shameless self-promotion... My pick this is -- Stripe put out some new products this past week. I think Stripe Connect has a new version, and then also something -- I'm trying to remember the non-internal name... Stripe Sigma. You can go look at what those are, but very specifical... |
\[43:06\] The Sigma page might as well be like a 3D C JavaScript that -- I don't know, it's really nifty. And then the other one uses some -- my very specific thing that I like about it is that it uses CSS Grid, which is kind of like a slightly useable thing on desktop modern browsers now - it's something we've talked ... |
So this is like a little section with the class name of Stripe, so open up your console and go to the Stripe.com/Connect and look at the Stripe section for a beautiful designer usage of the CSS Grid. That's my pick for the week. That 10 lines of HTML and CSS. \[laughter\] |
It's cool though, right? I'm always so excited when Stripe launches a new product, because "Cool, my company is doing something", but I'm really excited to see what the designers do for the landing page for those various products, because they're amazing. I love them. Shout out to Benjamin De Cock and Philipp Antoni. F... |
**Mikeal Rogers:** Awesome. So on that note, I guess that's gonna take us out. Thank you everybody for coming on. Rate us on iTunes, or something like that. We're done a little bit early today, everybody can get some extra food. \[laughter\] |
**Adam Stacoviak:** Or go shopping for a Tushy. |
**Mikeal Rogers:** \[laughter\] Exactly. Can we get Tushy to sponsor us? |
**Adam Stacoviak:** I don't see why they wouldn't... |
**Break:** \[45:09\] |
• Introduction and host introduction |
• Background and motivation for npm@5 release |
• Cache rewrite performance improvement (5x speed increase) |
• Additional performance updates and improvements |
• Usability improvements in npm@5, including default save functionality |
• Symlink feature and its benefits for monorepo development |
• Future plans and ongoing work on improving monorepo support |
• Optimizing default behavior in npm |
• Introducing new configuration options (--prefer-offline, --prefer-online) |
• Planning for a "low-mem" mode to reduce memory usage |
• Breaking down npm into smaller, reusable components |
• Avoiding dependency hell and maintaining flat installs |
• Providing building blocks for custom package managers |
• npm 5 supports all sources, including Git, with new semver support |
• npm 5 includes building and installing Git dependencies as step dependencies |
• npm 5's registry and package lock differ from yarn in terms of performance and lockfile management |
• npm 5 guarantees exact directory structure for installed modules, unlike yarn which only stores relationships between modules |
• concerns about post-install scripts still exist, but can be mitigated by using ignore scripts or running code in a sandboxed environment |
• there is ongoing work to prevent automated self-publishing worms and mitigate other security risks |
• npm@5 issues with breaking changes |
• Revisiting ecosystem concerns about scripts in package-lock.json and npm-shrinkwrap |
• Known issues with npm@5 and plans for release |
• Breakdown of changes in npm@5, including save by default and lockfile changes |
• Shrinkwrap usage and compatibility with npm@5 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.