Sponsors


Netlify




Sentry use the code “devchat” for 2 months free on Sentry’s small plan




Triplebyte offers a $1000 signing bonus


Panel


Thomas Aylott




David Ceddia




Lucas Reis


With special guest: Daishi Kato

Episode Summary

 

Todays guest Daishi Kato is a freelance programmer and has many open source libraries. He starts off by talking about how he got from tail call optimization to Redux and global state. Daishi talks about his definition of global state, how it differs from a regular state, and why it is a problem with the current context implementation. Thomas talks about his work with Android and how React has helped solved some of the problems they encountered. They talk about when different rendering issues they’ve encountered. Daishi shares his unique approach to solving rendering issues and how it applies to his libraries. His solution is to combine the system in React with proxy based tracking to solve issues with rendering. Daishi explains why this works and the importance of benchmarking. Daishi’s solution is designed as a same use state API, so someone can drop this in and see if it works.

Daishi talks about his definition of proxies and how it triggers the rerender. He also talks about how it handles conditional reads. This tracking happens every render and it doesn’t have the same limitations as hooks. The panel talks about the new version of React Redux library implementation and how it compares to Daishi’s. Daishi’s approach is useful for people earning Redux because the used tracked state gives you all the benefits without a lot of the complexity. Daishi talks about how it deals with deeply nested pieces of code.

The panel discusses the delicate balance of optimizing, but not doing it too soon, but to also remember how vital it is to maintain the performance of your app. Daishi’s work with Reactive React Redux to make sure things perform from the beginning is really important. It’s also important to understand how your product works so that when things do go wrong, you know how to fix it. Daisho talks about his other library React Tract for people who don’t like to use Redux.

Links


Mobex




GraphQL




Proc SQL




React-Tracked




Immer




Reactive React Redux




React Redux


 

Follow DevChat on Facebook and Twitter

Picks

David Ceddia:


A Compiler From Scratch video




Verbal Expressions


Thomas Aylott:


The Making of a Manager by Julie Zhou




Thomas’ Youtube channel


Lucas Reis:


Shun knives


Daishi Kato:


Remote Faces


Special Guest: Daishi Kato.

Sponsors


Netlify




Sentry use the code “devchat” for 2 months free on Sentry’s small plan




Triplebyte offers a $1000 signing bonus


Panel


Thomas Aylott




David Ceddia




Lucas Reis


With special guest: Daishi Kato

Episode Summary

 

Todays guest Daishi Kato is a freelance programmer and has many open source libraries. He starts off by talking about how he got from tail call optimization to Redux and global state. Daishi talks about his definition of global state, how it differs from a regular state, and why it is a problem with the current context implementation. Thomas talks about his work with Android and how React has helped solved some of the problems they encountered. They talk about when different rendering issues they’ve encountered. Daishi shares his unique approach to solving rendering issues and how it applies to his libraries. His solution is to combine the system in React with proxy based tracking to solve issues with rendering. Daishi explains why this works and the importance of benchmarking. Daishi’s solution is designed as a same use state API, so someone can drop this in and see if it works.

Daishi talks about his definition of proxies and how it triggers the rerender. He also talks about how it handles conditional reads. This tracking happens every render and it doesn’t have the same limitations as hooks. The panel talks about the new version of React Redux library implementation and how it compares to Daishi’s. Daishi’s approach is useful for people earning Redux because the used tracked state gives you all the benefits without a lot of the complexity. Daishi talks about how it deals with deeply nested pieces of code.

The panel discusses the delicate balance of optimizing, but not doing it too soon, but to also remember how vital it is to maintain the performance of your app. Daishi’s work with Reactive React Redux to make sure things perform from the beginning is really important. It’s also important to understand how your product works so that when things do go wrong, you know how to fix it. Daisho talks about his other library React Tract for people who don’t like to use Redux.

Links


Mobex




GraphQL




Proc SQL




React-Tracked




Immer




Reactive React Redux




React Redux


 

Follow DevChat on Facebook and Twitter

Picks

David Ceddia:


A Compiler From Scratch video




Verbal Expressions


Thomas Aylott:


The Making of a Manager by Julie Zhou




Thomas’ Youtube channel


Lucas Reis:


Shun knives


Daishi Kato:


Remote Faces



Special Guest: Daishi Kato.

Twitter Mentions