text
stringlengths
0
1.36k
• Decorators: Their use and potential for simplifying code, but also possible overcomplication
• Comparison between function components and class components in React
• Create React App: Its purpose, features, and benefits for managing a React project with ease
• React CLI tools and the suggested set of tools for building a React application
• Create React App was created to address feedback about lack of supported tools working together
• It started as a hackathon project and has since grown into a robust toolset with its own configuration and build system
• The toolset includes ESLint, Webpack, CSS, and Babel configurations that are hidden from the user to ensure compatibility and ease of use
• Users can either stay within the defined boundaries and receive updates or "eject" and configure their project manually
• A key feature in Create React App's 1.0 release is its integration with Webpack 2, which natively supports imports and exports without requiring Babel compilation
• This change allows for improved static analysis and better optimization of bundle size and tree shaking
• The speaker is discussing a platform or tool that has its own primitives and module system, similar to Node.js
• They are reframing their thinking about this tool and finding it interesting because it crosses boundaries of old tools
• The tool is compared to being like "grunt" or "babble", but also acts as a piece of glue between different systems
• It needs to understand ES6 modules natively in order to perform tasks like tree shaking
• The speaker mentions reading about updates to React and Create React App, including the addition of new features to JEST
• JEST is discussed as a testing framework that allows for unit tests and functional style tests without needing a browser
• It's mentioned that JEST has become a default choice for testing due to its support from Facebook
• The speaker highlights new features in the latest release, including immersive watch mode, better snapshot format, and automatic coverage reporting
• They also discuss how Create React App now includes JEST by default and provides a test directory with a test already written
• Finally, they touch on the issue of writing tests in the same JavaScript as components while using Babel and Webpack.
• Discussion on a framework's caching strategy and service worker implementation
• Fears of accidentally caching everything without a way to break out
• Service workers in React and how they can automatically update components
• Content Security Policy (CSP) as a default feature in Ember CLI
• Toolkit-style CLI helper features for solid generic defaults
• Distinguishing between a boilerplate generator and a living, evolving tool
• Comparison of create React app to Rails scaffolding
• Code splitting with Webpack
• Dynamic imports with async/await syntax
• Standards track for asynchronous imports
• Create React App support for code splitting
• Reducing JavaScript bundle size for PWAs
• Standardizing configuration for React apps
• Comparison to Ember CLI and Glimmer updates
• Future goals for frameworks: compiling to modern features, not ES5
• Current limitations in compiler performance benefits for developers
• Configuring Babel settings to optimize compilation and target features
• Trade-offs between development ease and performance considerations
• Electron project as the current topic of discussion
• Overview of Electron, its history, and key features
• Examples of successful applications built with Electron, including MongoDB's DB admin tool and Voltra music app
• Comfort level with Node.js and Electron
• Differences between building web apps with Node vs Electron
• NPM modules and their accessibility in Electron
• Cross-browser environment for running HTML in headless mode
• Comparison of Adobe Air/Flex and Electron
• Discussion on the benefits of using desktop applications, including increased engagement and attention
• Discussing the desktop's continued value
• GitHub's desktop apps and their transition to Electron
• Experience with moving from native applications to Electron
• Webpack 2 features, specifically tree shaking
• Critique of tree shaking as a crutch for bad coding practices
• Tree shaking benefits in certain situations
• Introduction of new project (CodeSomething) that optimizes code at compile-time
• Use of minifiers and multiple tools for optimization
• Discussion of immutable data structures and functional programming
• Recommendation of an Anjana Vakil talk on JS Confu about immutable data
• Discussion of immutable data structures and the ECMA spec
• Recommendation of the book "Hackers" by Steve Levy as a resource for learning about early hacker culture
• Description of the book's three parts, including its focus on the Tech Model Railroad Club at MIT, the homebrew computer club, and the gaming industry
• Mention of an appendix titled "The Last Hacker" which explores Richard Stallman's role in hacker culture before the GNU project
• Discussion of other resources for learning about early hacker culture and tech movies that hold up well
• Bandwidth partner: Fastly.com
• Episode editor: Jonathan Youngblood
• Theme music producer: Breakmaster Cylinder
• Closing remarks and thanks for listening
[0.00 --> 5.92] Bandwidth for JSParty is provided by Fastly. Learn more at Fastly.com.
[10.24 --> 14.40] Welcome to JSParty, a weekly celebration of JavaScript and the web.
[14.76 --> 19.72] Tune in live on Fridays at 3 p.m. U.S. Eastern at changelaw.com slash live.
[19.72 --> 24.12] Join the community and Slack with us in real time. Head to changelaw.com slash community.
[24.42 --> 28.34] Follow us on Twitter. We're at JSPartyFM. And now on to the show.
[28.34 --> 32.44] Hey, everybody. Welcome to JSParty. It's a party every week with JavaScript.
[33.06 --> 34.86] We're back. I'm Michael Rogers.
[35.38 --> 36.40] I'm Rachel White.
[36.80 --> 38.24] And I'm Alan Sampson.
[38.84 --> 44.08] Yep. And Rachel and I are back from a nice little vacation in Europe.
[44.98 --> 51.06] If you didn't, like, check out the episode where YayQuery took over.
[51.14 --> 52.76] Definitely go back and listen to that one.
[52.82 --> 56.16] That one was so good that Rachel and I were actually fired.
[56.16 --> 60.62] I got a text from Adam Stachowiak while I was in Europe, but just said you're fired.
[61.54 --> 64.56] And then it turned out that they can't do it.
[64.70 --> 67.94] They can't schedule it for another nine months.
[68.20 --> 73.44] So we're filling in now for them until they can come back around.
[74.10 --> 75.00] All right. Let's jump into it.
[75.00 --> 84.30] Okay. So we're going to talk about actually using ES6 and ES7 features, new language features,
[84.40 --> 87.34] with and without compilers and some of the trade-offs and stuff like that.
[88.04 --> 89.34] Don't look at my years now.
[89.74 --> 91.32] Is it ES2015?
[91.32 --> 97.46] I think that we should just talk about specific features rather than what bucket they land in,
[97.54 --> 99.90] because they actually get implemented sort of out of order anyway.
[100.16 --> 100.28] Right.
[100.62 --> 106.92] So Rachel, what features are you using that you've been enjoying from the new language stuff?
[107.62 --> 108.18] I'm not.
[109.54 --> 110.10] You're not.
[110.10 --> 110.12] You're not.
[110.12 --> 110.14] You're not.
[110.14 --> 110.20] You're not.
[110.20 --> 110.74] You're not.
[110.74 --> 110.92] You're sick.
[110.92 --> 116.90] No. I mean, the only thing that I've used really, because since I don't write production code,