text stringlengths 0 1.36k |
|---|
**Mikeal Rogers:** Well, I also think when you're comparing -- the trade-off of \[unintelligible 00:57:30.16\] is that it's a lower file size, but then you have to take some CPU cycles to decompress it. It matters if you have a fast CPU versus a slow disk, or a slow disk versus a fast CPU, or if you just have a fast bo... |
**John-David Dalton:** Right. |
**Mikeal Rogers:** On a MacBook you do have an SSD, but you're also on top of the worst file system ever created by human beings, so... |
**John-David Dalton:** But this is also a single-time load for the lifetime of the application, because Node caches the loaded modules as well... So what you'll be concerned with is your startup cost, and that's something that you can weigh. |
For me, the benefit is really clear because most -- so I should also mention this... Lodash 5 will not have an index file, will not have a main monolithic include; everything is cherry-picked, which means that -- a common usage is for people to reach for about five or six of the 300+ methods, and just use five or six. ... |
**Mikeal Rogers:** Right now I actually ended up pulling down the Lodash.whatever method that I need from npm, so that I get a smaller version - how is that gonna change in Lodash 5 with this? |
**John-David Dalton:** So that actually ends up being a larger version. I'm stopping the individually packaged methods - like the Lodash.chunk package - because it turns out code can't be shared very well across those packages. Something that's nice about a single package that has a lot of submodules within it is that ... |
Something I'm doing with the Lodash 5 is before, it gave you all the functionality upfront, and then you have to opt out of functionality, which means it created a bigger build by default. Lodash 5 is going in the opposite direction and giving you minimal functionality upfront, and then there'll be mechanisms for you t... |
With that, I think the need for individual packages will be reduced, and I can standardize folks on just using the single Lodash package and the build tools around that, like Webpack and Babel or whatever you need to optimize and enhance your package and bundle. |
**Mikeal Rogers:** \[01:00:19.13\] In order to do this, are Rollup and Webpack gonna have to become aware of your module system? |
**John-David Dalton:** Actually, for the gzip files, they will; they will have to become aware. I have already contributed the loader to Webpack, and it's part of their Webpack-contrib. So it's already in Webpack, it's already been published for them. For the other ones, yeah, they'll have to. What's great is that it's... |
**Mikeal Rogers:** That's great. Alex, do you have any remaining questions before we move on to picks? |
**Alex Sexton:** No, let's do some picks. |
**Mikeal Rogers:** Yeah, this is all super compelling. Alright, Alex, why don't you kick us off. |
**Alex Sexton:** I am going to pick somewhat of an ecosystem of ideas, kind of... It's the Fantasy Land specification. At Stripe we use some types, and then there's some people who are really into types, and they make me use them a little more than I like, but some things end up being really pretty and good... And ther... |
**John-David Dalton:** Actually, I believe they were naming it that because someone had been poking fun at them in a Reddit thread, and they said "You must be living in a fantasy land!" and that's how the spec name came. |
**Alex Sexton:** So I like it a lot, but I agree that it's a fantasy land. We use some subset of these at Stripe as part of our stuff, but it's just like whenever you need either algebraic structure to handle errors, and leftMap, rigthMap, whatever type stuff... But then there's kind of a community that wraps popular t... |
For instance, there's a Lodash Fantasy Land implementation that-- |
**John-David Dalton:** Oh, now way! |
**Alex Sexton:** Yeah, so you can get that, or you can get Ramda Fantasy Land as well. Any of that different stuff... Not only is it typed, because there are type defs for both TypeScrypt and FlowType, but also it adds in these algebraic structures for how things come back and how you use them, and things... And it's c... |
I think if you kind of start with it or use it for some base core of your fetching code, or something like that... Any sub-ecosystem could completely use this and be pretty successful, even if you can use it across everything, because other libraries don't necessarily \[unintelligible 01:03:33.06\] |
**Alex Sexton:** I tend to think for functional programming a little goes a long way; I'm into the "a little bit in moderation is a good thing." I'm on the fence about this whole FP thing. I offer functional forms of Lodash modules called Lodash/fp - it's built into the existing 4.0 - and that has everything auto-curri... |
\[01:04:26.02\] I see FP as kind of that same thing where it may not be as big of an audience, but they are very enthusiastic. The users of functional programming styles are very enthusiastic, they're super eager to help, so I'm trying to decide how to continue that with Lodash 5, too. Totally cool, yeah. |
**Alex Sexton:** Yeah, you should look into Fantasy Land. |
**John-David Dalton:** Yeah. It's actually the most requested feature on Lodash right now - a Fantasy Land compliant version. |
**Alex Sexton:** Well, cool. |
**John-David Dalton:** I bet you didn't know that! Totally close! |
**Alex Sexton:** I did see that issue, but yeah. |
**Mikeal Rogers:** Alright. JDD, do you have a pick for us? |
**John-David Dalton:** I do have a pick, and it is for projects like Babel. I would say they're always looking for contributors to help. Projects that I see requesting for contributions and pull requests would be things like Mocha, MomentJS, Babel... If you're looking to get into open source and you're looking to get y... |
I would say look to those, especially if you use them in your day job. If you use Babel, go contribute back to it; if you use MomentJS, which is awesome for dates, contribute back a little bit. It means the world to the maintainers; they're just like everyone else, they're trying to find the time to work on the project... |
**Alex Sexton:** The time may have passed, but for a long time the best place to contribute - anything that TJ wrote and abandoned was in dire need of people to do easy fixes. I think Mocha still falls there. |
**John-David Dalton:** Yeah. That means the world to people. Help out. Lodash itself is in a pretty good, stable state. I'm taking my time with version five, so I'm coasting on that front, but on these other ones, these other projects could really use some help managing issues and pull requests and features. |
**Mikeal Rogers:** Cool. My pick is Mapzen. If you've ever had to integrate a map with a website or app that you're using, you probably poked around with a few things that are terrible and then settled on Mapbox. Mapbox's definitely set like a great standard - they were better than everything else - but they get really... |
\[01:07:12.08\] Also, I have a bunch of code sitting around that I have to copy and paste in in order to figure out how to do things. So the Mapzen JavaScript API is just a little bit more evolved, a little bit easier to use. They have a lot of the same support and cool tools and everything, but it's just a bit easier,... |
Alright, thanks everybody for joining us, thanks JDD for coming on for this episode. |
**John-David Dalton:** Thanks for having me. |
**Mikeal Rogers:** Yeah, anytime. With that, we're all done for today. Thanks, everybody! |
**John-David Dalton:** Bye! |
• Discussion of community poll results showing poor Node.js documentation |
• Importance of clear and concise documentation in learning programming languages |
• Difficulty of writing good documentation for entry-level learners |
• Role of Stack Overflow in providing information on programming languages |
• Responsibilities of maintainers and contributors to provide resources and support for users |
• Challenges of managing multiple sources of information and knowledge in the community |
• Writing documentation during development to make it easier in the long run |
• Using types (e.g. Flow, TypeScript) for automatic documentation generation |
• Having a culture of documenting code and providing examples |
• Stripe's frontend explorer for displaying example usage of components |
• ReadTheDocs.io as a central repository for project documentation |
• MDN as an example of high-quality, persistent documentation |
• Hiring technical writers to improve documentation quality |
• Communicating with technical writers to ensure they have the necessary information |
• Examples of well-documented projects (e.g. Johnny-Five, Stripe API) |
• Documentation is made specific to the user with automatic scraping |
• Living documentation makes people understand what they need to send and receive |
• Good documentation encourages users to connect with a product and share its benefits |
• Writing good documentation is work that should not be an excuse for bad documentation |
• As a project grows, maintaining living documentation becomes increasingly difficult due to changing code and growing user base |
• Running tests against API endpoints can help ensure documentation accuracy |
• Non-blocking UI rendering techniques are discussed, including concurrency in the UI thread and server-side rendering with isomorphic JavaScript. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.