Regaining JavaScript Performance in your Website

Original: https://codingcat.dev/podcast/2-20-regaining-java-script-performance-in-your-website

▶ Watch on YouTube & Subscribe to CodingCat.dev

**Regaining JavaScript Performance in your Website **is a CodingCat.dev podcast episode featuring Ryan Carniato alongside Alex Patterson focused on JavaScript, Builder.io, React. Ryan Carniato teaches us about all the aspects of frontend frameworks and Javascript today. 2.20 - Regaining JavaScript Performance in your Website: We have Ryan Carniato on to talk about SolidJS and performance on your website. As well as comparing Qwik, React and SolidJS. Make sure to checkout @ryan Carniato's YouTube! https://codingcat.dev/podcast/2-20-regaining-java-script-performance-in-your-website Sponsors

https://Builder.io

Empower you Watch the full video breakdown on YouTube or explore the architectural notes, chapters, and official documentation links below.

Questions

1. Can you tell us about yourself and how you got started
2. JS Performance in 2020
3. Lets talk about this Partial Hydration Thread
4. How do frameworks like Qwik, Svelte, Marko compare with SolidJS?
   1. Would you say that React is the closest comparison?
5. Will something else start trending this year?
6. Q&A

Technical Overview: Regaining JavaScript Performance in your Website

2.20 - Regaining JavaScript Performance in your Website: We have Ryan Carniato on to talk about SolidJS and performance on your website. As well as comparing Qwik, React and SolidJS. Make sure to checkout @ryan Carniato's YouTube! https://codingcat.dev/podcast/2-20-regaining-java-script-performance-in-your-website Sponsors

https://Builder.io

Empower you

When applying the concepts from Regaining JavaScript Performance in your Website in a production codebase, teams working with JavaScript, Builder.io, React, Svelte should align their implementation with the MDN JavaScript Reference (ECMAScript specifications, Web APIs, and runtime fundamentals). Structuring your workflow around repeatable patterns, automated verification, and clear separation of concerns helps prevent regressions as your application scales.

Key Engineering Takeaways

• **Core Topic Focus: **Practical strategies for JavaScript, Builder.io, React, Svelte covered in "Regaining JavaScript Performance in your Website" (Ryan Carniato teaches us about all the aspects of frontend frameworks and Javascript today.).
• **Production Implementation: **Combine the architectural patterns demonstrated in this podcast with the official MDN JavaScript Reference for type safety, performance, and long-term maintainability.
• **Hands-On Video Walkthrough: **Follow along with the live coding demos and discussion on YouTube (Regaining JavaScript Performance in your Website) and subscribe to CodingCat.dev on YouTube for weekly deep dives.

Video Chapters & Timestamps

Jump directly to any segment of Regaining JavaScript Performance in your Website on YouTube using the timestamped chapters below:

• 00:00: PM (EST)
• 00:00: Intro
• 00:00: Ryan Intro
• 00:00: Why did you create Solid?
• 00:00: JavaScript Performance
• 00:00: Marko
• 00:00: Performance in Solid
• 00:00: Metrics
• 00:00: Svelte comparison
• 00:00: Are you still working for Ebay?
• 00:00: Svelte if it could do hooks
• 00:00: What is the future of the web?
• 00:00: Native Apps
• 00:00: Shifting the paradigm
• 00:00: Builder.io
• 00:00: Tweet thread about partial hydration
• 00:00: Performance differences
• 00:00: Demo of hydration
• 00:00: Jamstack
• 00:00: Solid feels like what React should be (Hacker News)

Resources, Links & Official Documentation

• *Watch on YouTube: *Regaining JavaScript Performance in your Website Full Video (plus Subscribe to CodingCat.dev)
• *builder.io: *https://Builder.io
• *:36 - Solid Hack: *https://hack.solidjs.com/
• *:00 - Ryan and Misko chat: *https://www.youtube.com/watch?v=lY6e7Hw4uVo&feature=youtu.be
• *:00 - Resident Alien: *https://www.syfy.com/resident-alien
• *Show Pick: *Hack SolidJS (picked by Alex Patterson)
• *Show Pick: *SolidJS is what I wanted React to be (picked by Alex Patterson)
• *Show Pick: *Building Qwik with Misko Hevery and Ryan Carniato (picked by Alex Patterson)
• *Show Pick: *Resident Alien (picked by Ryan Carniato)
• Ryan Carniato Guest Profile & Episodes on CodingCat.dev
• Ryan Carniato on GitHub
• Episode Sponsor: Builder.io
• MDN JavaScript Reference: ECMAScript specifications, Web APIs, and runtime fundamentals
• Builder.io Developer Documentation: Visual headless CMS, SDKs, and design-to-code workflows
• React Official Reference: Hooks, Server Components, and UI state patterns

Related CodingCat.dev Tutorials & Podcast Episodes

• Revealing all of Next.js 12's Features: We sit down with Lee Robinson, Head of Developer relations at Vercel, to talk all about Next.js 12.
• Scaling your JavaScript Career with Ui.dev: Alex sits down with Tyler McGinnis from Ui.dev and talks through scaling your JavaScript career. Tyler talks all about how you can use Ui.dev to learn in a succ...
• Automating Infrastructure with Digger.dev: We sit down to chat with Igor from http://Digger.dev how to automate all of your infrastructure needs on AWS. The goal of Digger is to make AWS simple!

Frequently Asked Questions (FAQ)

What are the main takeaways from Regaining JavaScript Performance in your Website?

Ryan Carniato teaches us about all the aspects of frontend frameworks and Javascript today. 2.20 - Regaining JavaScript Performance in your Website: We have Ryan Carniato on to talk about SolidJS and performance on your website. As well as comparing Qwik, React and SolidJS. Make sure to checkout @ryan Carniato's YouTube! https://codingcat.dev/podcast/2-20-regaining-java-script-performance-in-your-website Sponsors

https://Builder.io

Empower you Throughout this podcast, Ryan Carniato breaks down real-world implementation details for JavaScript, Builder.io, React so developers can apply these patterns directly in production.

How do you implement JavaScript best practices in production?

When adopting JavaScript and Builder.io in a production stack, start by validating your configuration against the MDN JavaScript Reference (ECMAScript specifications, Web APIs, and runtime fundamentals). Focus on incremental adoption, automated testing, and observability so your team can measure performance and developer velocity improvements at each stage.

Where can I watch the full Regaining JavaScript Performance in your Website walkthrough and find related code resources?

You can watch the complete video session for Regaining JavaScript Performance in your Website on the CodingCat.dev YouTube channel. For a deeper dive into JavaScript, check out our related guide: Revealing all of Next.js 12's Features.