Koivurova, Timo, author

Stapleton, Geoff, author

McNamara, Ken

Norman, M. A

Kozin, L. F. (Leonid Fomich), author

Most of them are involved in transporting vegetables to the Chennai market

The panelists discuss Knockout.js with Steven Sanderson

Panel Kris Kowal (twitter github blog) Domenic Denicola (twitter github blog) AJ O’Neal (twitter github blog) Jamison Dance (twitter github blog) Joe Eames (twitter github blog) Merrick Christensen (twitter github) Charles Max Wood (twitter github Teach Me To Code Intro to CoffeeScript) Discussion 02:41 - Promises Asynchonous programming 05:09 - Using Promises from top to bottom 07:08 - Domains NodeConf SummerCamp 07:55 - Q 10:22 - q.nfbind 11:15 - Q vs jQuery You’re Missing the Point of Promises Coming from jQuery 15:41 - long-stack-traces turn chaining JavaScriptStackTraceApi: Overview of the V8 JavaScript stack trace API (error.prepare stack trace) 19:36 - Original Promises/A spec and Promises/A+ spec when.js Promises Test Suite Underscore deferred 24:22 - .then Chai as Promised 26:58 - Nesting Promises spread method 28:38 - Error Handling causeway 32:57 - Benefits of Promises Error Handling Multiple Async at once Handle things before and after they happen 40:29 - task.js 41:33 - Language e programming language CoffeeScript 44:11 - Mocking Promises 45:44 - Testing Promises Mocha as Promised Picks Code Triage (Jamison) The Creative Sandbox Guidebook (Joe) Steam (Joe) Pluralsight (Joe) montage (Kris) montagejs / mr (Kris) CascadiaJS 2012 - Domenic Denicola (Domenic) Omnifocus (Chuck) Buckyballs (AJ) Transcript JOE: I can’t imagine your baby face with a beard, Jamison. JAMISON: I never thought I had a baby face. AJ: It was always a man face to me. JOE: Everybody who is 15 years younger than me has a baby face. [This episode is sponsored by ComponentOne, makers of Wijmo. If you need stunning UI elements or awesome graphs and charts, then go to wijmo.com and check them out.] [This show is sponsored by Gaslight Software. They are putting on Mastering Backbone training in San Francisco at the Mission Bay Conference Center, December 3rd through 5th. They'll be covering Jasmine, Backbone and CoffeeScript. For more information or to register, go to training.gaslightsoftware.com] [Hosting and bandwidth provided by the Blue Box Group. Check them out at bluebox.net] CHUCK: Hey everybody. Welcome to episode 37 of the JavaScript Jabber show. This week on our panel, we have AJ O'Neal. AJ: Yo, yo, yo, comin' at you live from the executive boardroom suite of Orem, Utah. CHUCK: Jamison Dance. JAMISON: Hey guys! CHUCK: Joe Eames. JOE: Hey there! CHUCK: Merrick Christensen MERRICK: What's up. CHUCK: I'm Charles Max Wood from devchat.tv and this week we have some guests -- and that is Kris Kowal. KRIS: Hello. Yeah, Kowal. CHUCK: Kowal. OK. And Domenic Denicola. Did I say that right? DOMENIC: Denicola. CHUCK: Denicola. DOMENIC: It’s OK I got Americanized. That's probably the proper Italian pronunciation. Hi guys! CHUCK: I speak proper Italian, so probably. KRIS: Yeah and for what it’s worth, I think that the proper Polish is Kowal or something, but yeah. JAMISON: Kris, are you from the Midwest? You have kind of Minnesota-ish accent. KRIS: No. I'm actually unfortunately from somewhere in the suburbs of Los Angeles, but I grew up indoors and did listen to Prairie Home Companion. So I don’t know. Maybe. [laughter] CHUCK: Awesome. All right. So this week we are going to be talking about… actually there's one thing I need to announce before. If you are listening to this episode, you’ll probably notice a little bit of a difference with our sponsorship message. I actually left off one important piece to one of the sponsorship messages and that is for the Gaslight software training that's going to be in San Francisco, if you wanna sign up, go to training.gaslightsoftware.com and you can sign up there. They’ve been a terrific sponsor and I feel kind of bad that I botched that. But anyway,

Anton Kovalyov joins the Jabber gang to talk about JSHint, linting, parsing, lexing and much more.

The panelists discuss The New York Times and JavaScript with Eitan Konigsburg, Alastair Coote and Reed Emmons.

The panelists discuss dependency injection with Vojta Jína & Misko Hevery.

The panelists discuss the Koa Framework with Gerred Dillon and Will Conant.

Check out Newbie Remote Conf!

02:11 - Heiko Behrens Introduction

• Twitter
• GitHub
• Blog

02:42 - François Baldassari Introduction

• Twitter
• GitHub

03:04 - JavaScript and Pebble

• Espruino
• jerryscript

06:40 - Watch vs Phone

• Pebble.js

09:32 - Memory Constraints and Code Size Limitations

• APIs
• rockyjs
• tween.js

26:24 - Advantages of Writing in JavaScript

32:09 - Capabilities of the Watch

• iPhreaks Episode #153: Using Mobile Devices to Manage Diabetes with Scott Hanselman

37:08 - Running Web Servers

39:29 - Resources

• rockyjs
• Newsletter
• Pebble Slack Channel
• Pebble Developer Page
• @PebbleDev
• Pebble TicToc Source

41:58 - Voice Capabilities

43:06 - UI For the Round Face vs Square Face

46:18 - Future Pebble Milestones

Picks

• Vortex Poker 3 (Jamison)
• Thao & The Get Down Stay Down (Jamison)
• Maciej Ceglowski: Barely succeed! It's easier! (Jamison)
• The Way of Kings Trilogy by Brandon Sanderson (Joe)
• Juniors Are Awesome (Aimee)
• octotree (Aimee)
• Fully Alive by Ken Davis (Chuck)
• Sara Soueidan (Heiko)
• Jake Archibald: Using the service worker (Heiko)
• beyond tellerrand’s Videos (Heiko)
• Fabien Chouteau: Make with Ada: Formal proof on my wrist (François)
• pebble.rs (François)
• The World of Yesterday by Stefan Zweig (François)

See Also

• iPhreaks Show Episode #146: Pebble with Heiko Behrens and Daniel Rodríguez Troitiño

React Remote Conf and Angular Remote Conf

03:18 - Dennis Ushakov Introduction

• Twitter
• GitHub
• JetBrains
  • JetBrains Issue Tracker
• WebStorm
  • @WebStormIDE  

03:54 - Writing an IDE in Java

• YouTrack
• TeamCity  

04:50 - Specs

05:43 - WebStorm Defined

• Integrated Development Environment (IDE)

06:19 - IDEs vs Text Editors

08:31 - Building an IDE

• Language Support
• External Tool Support
• Abstract Syntax Tree (AST)

13:00 - Code Reuse

15:07 - Prioritizing Features

17:11 - Why is IDE tooling important?

• “Code is read a lot more than it’s written.”

19:57 - Refactorings

• The Dynamic Nature of JavaScript
• TypeScript-specific Refactorings

23:35 - Next Versions of Webstorm

• Early Access Program

25:07 - Framework Support; Usage Data

28:12 - Other Technology and Framework Support

31:12 - Working for JetBrains

32:17 - Release Cycles and Procedures

• Early Access Program

34:39 - Java Source Code Contribution

• Kotlin

Picks

• Jesse Kriss: Human scale technology (Jamison)
• React Rally (Jamison)
• Vote (Chuck)
• Transmit (Chuck)
• Steam Squad (Dennis)
• Ergobaby Four Position 360 Baby Carrier (Dennis)

On today's episode of My JS Story, Charles Max Wood welcomes Dennis Ushakov. Dennis is a team lead of WebStorm and RubyMine at JetBrains. Tune in to My JS Story Dennis Ushakov to learn more about his programming experience in Java and JavaScript.

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:20 – Chuck: Let’s talk about microstates – what is that?

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?

7:13 – Panel: There are a lot of pieces. If I spoke on a few specific things I would say that it enables programming with state machines.

7:42 – Panel: We wanted it to fell like JavaScript – that’s what I heard.

7:49 – Aimee: I heard that, too.

7:59 – Guest.

8:15 – Aimee: Redux feels like JavaScript to me.

8:25 – Guest: It’s actually – a tool – that it feels natural so it’s not contrived. It’s all JavaScript.

8:49 – Panel.

9:28 – Guest: Idiomatic Ember for example. Idiomatic in the sense that it gives you object for you to work with, which are simple objects.

10:12 – Guest: You have your reducers and your...we could do those things but ultimately it’s powerful – and not action names – we use method names; the name of the method.

11:20 – Panel: I was digging through docs, and it feels like NORMAL JavaScript. It doesn’t seem like it’s tied to a certain framework or library platform?

11:45 – Guest: Yes, we felt a lot of time designing the interfaces the API and the implementation. We wanted it to feel natural but a tool that people reach for.

(Guest continues to talk about WHY they created microstates.)

Guest: We wanted to scale very well what you need when your needs to change.

13:39 – Chuck: I have a lot of friends who get into React and then they put in Redux then they realize they have to do a lot of work – and that makes sense to do less is more.

14:17 – Guest: To define these microstates and build them up incrementally...building smaller microstates out of larger ones.

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?

16:15 – Panel: I understand that this is tiny – but why wouldn’t I just use the native features in specific the immutability component to it?

16:42 – Guest: I’m glad you asked that question. We wanted to answer the question...

Guest: With microstates you can have strict control and it gives you the benefit of doing sophisticated things very easily.

18:33 – Guest: You mentioned immutability that’s good that you did. It’s important to capture – and capturing the naturalness of JavaScript. It’s easy to build complex structures – and there is an appeal to that. We are building these graphs and these building up these trees. You brought up immutability – why through it away b/c it’s the essence of being a developer. If you have 3-4-5 levels of nesting you have to de-structure – get to the piece of data – change it – and in your state transition 80% of your code is navigating to the change and only 20% to actually make the change. You don’t have to make that tradeoff.

21:25 – Aimee: The one thing I like about the immutability b/c of the way you test it.

21:45 – Guest: There a few things you can test. 

23:01 – Aimee: You did a good job of explaining it.

23:15 – Guest: It makes the things usually hard  easy! With immutability you can loose control, and if that happens you can get so confused. You don’t have a way to have a way to navigate to clarity. That’s what this does is make it less confusing. It gives you order and structure. It gives you a very clear path to do things you need to do. If there is a property on your object, and if there is a way to change it...

25:29 – Guest: The only constant is change no matter what framework you are working on.

24:46 – Chuck: We are talking about the benefits and philosophy. What if I have an app – and I realize I need state management – how do I put microstates into my app? It’s using Angular or React – how do I get my data into microstates?

26:35 – Guest: I can tell you what the integration looks like for any framework. You take a type and you passed that type and some value to the create function so what you get is a microstate.

(The Guest continues diving into his answer.)

28:18 – Guest: That story is very similar to Redux, basically an event emitter. The state changes on the store.

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.

31:33 – Advertisement: Sentry.io

32:29 – Guest: I want to go back to your question, Chuck. Did we answer it?

32:40 – Chuck: Kind of.

32:50 – Guest.

32:59 – Guest: In Angular for example you can essentially turn a microstate...

33:51 – Guest: You could implement a connect, too. Because the primitive is small – there is no limit.

34:18 – Chuck summarizes their answers into his own words.

34:42 – Guest: If you were using a vanilla React component – this dot – I will bind this. You bind all of these features and then you pass them into your template. You can take it as a property...those are those handlers. They will perform the transition, update and what needs to be updated will happen.

35:55 – Chuck: Data and transitions are 2 separate things but you melded them together to feel like 1 thing. This way it keeps clean and fast.

36:16 – Guest: Every framework helps you in each way.

Microstates let’s you do a few things: the quality of your data all in one place and you can share.

38:12 – Guest: He made and integrated Microstates with Redux tools.

38:28 – Guest talks about paths, microstates to trees.

39:22 – Chuck.

39:25 – Panel: When I think about state machines I have been half listening / half going through the docs. When I think of state machines I think about discreet operations like a literal machine. Like a robot of many steps it can step through. We have been talking about frontend frameworks like React - is this applicable to the more traditional systems like mechanical control or is it geared towards Vue layered applications?

40:23 – Guest: Absolutely. We have BIG TEST and it has a Vue component.

41:15 – Guest: when you create a microstate from a type you are creating an object that you can work with.

42:11 – Guest: Joe, I know you have experience with Angular I would love to get your insight.

42:33 – Joe: I feel like I have less experience with RX.js. A lot of what we are talking about and I am a traditionalist, and I would like you to introduce you guys to this topic. From my perspective, where would someone start if they haven’t been doing Flux pattern and I hear this podcast. I think this is a great solution – where do I get started? The official documents? Or is it the right solution to that person?

43:50 – Guest: Draw out the state machine that you want to represent in your Vue. These are the states that this can be in and this is the data that is required to get from one thing to the other. It’s a rope process. The arrow corresponds to the method, and...

44:49 – Panel: It reminds me back in the day of rational rows.

44:56 – Guest: My first job we were using rational rows.

45:22 – Panelist: Think through the state transitions – interesting that you are saying that. What about that I am in the middle – do you stop and think through it or no?

46:06 – Guest: I think it’s a Trojan horse in some ways. I think what’s interesting you start to realize how you implement your state transitions.

48:00 – (Guest continues.)

48:45 – Panel: That’s interesting. Do you have that in the docs to that process of stopping and thinking through your state transitions and putting into the microstate?

49:05 – Guest: I talked about this back in 2016. I outlined that process. When this project was in the Ember community.

49:16 – Guest: The next step for us is to make this information accessible. We’ve been shedding a few topics and saying this is how to use microstates in your project. We need to write up those guides to help them benefit in their applications.

50:00 – Chuck: What’s the future look like?

50:03 – Guest: We are working on performance profiling.

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.

52:12 – Guest: Getting documentation. We have good README but we need traditional docs, too.

52:20 – Chuck: Anything else?

52:28 – Guest: If you need help email us and gives us a shot-out.

53:03 – Chuck: Let’s do some picks!

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: cowboyd@frontside.io
• 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

Sponsors

• Sentry use the code “devchat” for 2 months free on Sentry small plan
• Clubhouse
• CacheFly

Host: Charles Max Wood

Special Guest: Miško Hevery

Episode Summary

In this episode of My JavaScript Story, Charles hosts Miško Hevery, creator of Angular and Senior Computer Scientist at Google.

Miško was introduced to computers when his father brought a Sinclair ZX Spectrum home for them to play with. When they moved to the United States from Czech Republic, Miško attended Rochester Institute of Technology and studied Computer Engineering. After working for companies such as Adobe, Sun Microsystems, Intel, and Xerox, he joined Google where created the Angular framework. For more on the story of how Miško created AngularJS, listen to the ‘Birth of Angular’ episode on the Adventures in Angular podcast here.

Miško is currently working on Angular Ivy at Google and plans to restart a blog in the future.

Links

• Adventures in Angular: The Birth of Angular
• JavaScript Jabber: Dependency Injection in JavaScript with Vojta Jína & Misko Hevery
• Miško's Twitter
• Miško's GitHub
• Miško's Medium
• Miško's LinkedIn
• How to Talk so Kids Will Listen and Listen so Kids Will Talk
• https://devchat.tv/my-angular-story/

 Picks

Miško Hevery:

• Prusa3D - 3D Printers from Josef Prusa

Charles Max Wood:

• The Kingfountain Series by Jeff Wheeler

Sponsors

• Triplebyte offers a $1000 signing bonus
• Sentry use the code “devchat” for $100 credit
• Linode
• CacheFly

Panel

• AJ O’Neal

Joined by special guest: Sam Selikoff

Episode Summary

In this episode of JavaScript Jabber, Sam Selikoff, Co-Founder at EmberMap, Inc. starts with giving a brief background about himself and his work followed by a discussion with AJ O’Neal about the Ember community. Sam mentions some of the biggest advantages in using Ember, and what it should and should not be used for. He explains the architecture of Ember apps, addresses some of the performance concerns and then dives into Octane in detail. He talks about a bunch of Ember components, compiler compatibility, relative weight of Ember apps compared to other frameworks, the underlying build system, and security considerations. Sam then helps listeners understand the usage of ES6 classes and decorators in Ember at length. At the end, they discuss component rendering and element modifiers and move onto picks.

Links

• Sam’s website
• Sam on Twitter
• Sam on GitHub

Follow JavaScript Jabber on Devchat.tv, Facebook and Twitter.

Picks

AJ O’Neal:

• Good Mythical Morning - YouTube

Sam Selikoff:

• The Man In the High Castle  
• Tailwind CSS

Sponsors

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

• Ruby Rogues

• React Native Radio

• CacheFly

Host: Charles Max Wood

Joined by Special Guest: Sam Selikoff

Episode Summary

Sam Selikoff, Co-Founder at EmberMap shares his journey of how he became a developer. Sam was an Economics major in college and he really loved the theory of economics.

When he graduated, he started working as a consultant and while working with data for statistical analysis he found that he enjoyed working with SQL and that how he started his developing career.

Sam explains why he prefers Ember.js framework to other frameworks. He also talks about the projects he is working on currently.

Apart from coding Sam enjoys reading economics books and playing music with his family. He shares some of his favorite books to read on the Theory Of Economics.

Links

• JSJ 364: Ember Octane with Sam Selikoff

• EmberMap Podcast

• Sam's Twitter

Picks

Charles Max Wood

• Podcast Movement

Sam Selikoff

• UPLIFT Desk

• Midsommar Movie

Rado Stankov is the Head of Engineering at Product Hunt. He's based in Sofia Bulgaria. He walks us through learning Pascal and PHP and Flash. We then dive into Ruby and JavaScript and what he's working on now at Product Hunt.

Host: Charles Max Wood

Joined By Special Guest: Radoslav Stankov

Sponsors

• G2i | Enjoy the luxuries of freelancing

• CacheFly

______________________________________

"The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today!

______________________________________

Links

• MRS 077: Radoslav Stankov

• RR 396: GrapQL at Product Hunt with Radoslav Stankov

• RRU 042: React at Product Hunt with Radoslav Stankov

• React Native at Product Hunt feat. Radoslav Stankov and Vlad Vladimirov

• Prototypejs

• jQuery

Picks

Radoslav Stankov:

• Dependency cruiser

• The Unicorn Project

Charles Max Wood:

• The Name of the Wind

• LinkedIn

• Clean Coders Podcast

• Devchat.tv Workshops

JavaScript Remote Conf 2020

May 13th to 15th - register now!

Håkon Krogh is a Norweigan developer who focuses on web performance. We start out discussing working from home in the current pandemic. His current company works in Product Information Management. It's a headless ecommerce system. We dive into his experience learning learning to build applications and learning JavaScript and leading a team.

Host: Charles Max Wood

Joined By Special Guest: Håkon Krogh

Sponsors

• G2i | Enjoy the luxuries of freelancing

• Sentry

• CacheFly

"The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today!

Links

• RRU 078: The Uncanny Valley with Håkon Krogh

• Crystallize

• FindThatLead

• Twitter: Håkon Krogh

Picks

Håkon Krogh:

• High Performance Browser Networking

• Tiny Helpers

Charles Max Wood:

• Cleverly

• Scrabin

Konicek-Moran, Richard

Krutikov, Mikhail

Lahire, Nathalie

Pickover, Clifford A

Morrell, Sachiko Kaneko, 1930-

Sachikonye, L. M

Kondo, Manabu, author

Zelko, Frank S

Borisenko, V. E. (Viktor Evgenʹevich)

NATO Advanced Research Workshop on Nanoscale Devices - Fundamentals and Applications (2004 : Kishinev, Moldova)

Wolf, E. L