Show notes
Panel:
Aimee Knight
Charles Max Wood
Joe Eames
AJ O’Neil
Chris Ferdinandi
Special Guests: Charles Lowell (New Mexico) & Taras Mankovski (Toronto)
In this episode, the panel talks with two special guests Charles and Taras. Charles Lowell is a principle engineer at Frontside, and he loves to code. Taras works with Charles and joined Frontside, because of Charles’ love for coding. There are great personalities at Frontside, which are quite diverse. Check out this episode to hear about microstates, microstates with react, Redux, and much more!
Show Topics:
1:32 – Guest: My mind is focused on the how and not the what. I will zoom my mind out and let’s talk about the purposes of microstates. It means a few things. 1.) It’s going to work no matter what framework you are using. 2.) You shouldn’t have to be constantly reinventing the wheel. React Roundup – I talked about it there at this conference.
Finally, it really needs to feel JavaScript. We didn’t want you to feel like you weren’t using JavaScript. It uses computer properties off of those models. It doesn’t feel like there is anything special that you are doing. There are just a few simple rules. You can’t mutate the state in place. If you work with JavaScript you can use it very easily. Is that a high-level view?
8:15 – Aimee: Redux feels like JavaScript to me.
(Guest continues to talk about WHY they created microstates.)
Guest: We wanted to scale very well what you need when your needs to change.
Guest continued: Will we be able to people can distribute React components a sweet array of components ready for me to use – would I be able to do the same for a small piece of state? We call them state machines, but ultimately we have some state that is driving it. Would we be able to distribute and share?
Guest: With microstates you can have strict control and it gives you the benefit of doing sophisticated things very easily.
(The Guest continues diving into his answer.)
Maybe this is a good time to talk about the stability benefits and the lazy benefits because microstates is both of those things.
Stability – if I invoke a transition and the result is unchanged – same microstate – it doesn’t emit an event. It recognizes it internally. It will recognize that it’s the same item. Using that in Ember or Redux you’d have to be doing thousands of actions and doing all that computation, but stability at that level.
Also, stability in the sense of a tree. If I change one object then that changes it won’t change an element that it doesn’t need to change.
Microstates let’s you do a few things: the quality of your data all in one place and you can share.
40:23 – Guest: Absolutely. We have BIG TEST and it has a Vue component.
48:00 – (Guest continues.)
Essentially you can hook up microstates to a fire hose.
The next thing is settling on a pattern for modeling side effects inside microstates. Microstates are STATE and it’s immutable.
53:05 – Advertisement for Charles Max Wood’s course!
Links:
Kendo UI
Frontside
Redux
Microstates
Microstates with React
Taras Mankovski’s Twitter
Taras Mankovski’s GitHub
Taras Mankovski’s LinkedIn
Taras Mankovski’s Frontside Bio
Charles Lowell’s Twitter
Charles Lowell’s GitHub
Charles Lowell’s Frontside Bio
Schedule Once
Ruby on Rails
Angular
Get A Coder Job
YouTube Talks
Email: [email protected]
Working with State Machines
Twitch TV
BigTest
Close Brace
REEF
The Developer Experience
YouTube Video
Sponsors:
Kendo UI
Sentry.io – 2 months free – DEVCHAT/code
Get A Coder Job
Picks:
Aimee
ShopTalk Episode 327
Professional JavaScript for Web Developers
Technical Debt
Stripe
Taras
Twitch Channel
Big Test
Frontside
Charles Lowell
Chalkboards
Sargent Art Chalk
Chris
Close Brace
LaCroix Water
Chris’s Git Hub
Joe
The Developer Experience Bait and Switch
Good Bye Redux
Recording Dungeon and Dragons
AJ
UtahJS Conf
Start with Why
The Rust Book
VanillaJS w/ Chris
Zero to One
Charles
Podwrench.com - beta
getacoderjob.com

