ALTA Nickel/Cobalt/Copper Conference (2nd : 2011 : Perth, W.A)

ALTA Gold Conference (3rd : 2012 : Perth, W.A)

ALTA Uranium Conference (8th : 2012 : Perth, W.A)

ALTA Nickel/Cobalt/Copper Conference (3rd : 2012 : Perth, W.A)

Cocks, Robert J., author

Check out Freelance Remote Conf and React Remote Conf!

02:31 - Jochen Krause Introduction

• Twitter
• EclipseSource

03:21 - Ian Bull Introduction

• Twitter
• GitHub
• Blog

04:01 - Tabris.js

• tabris-js (GitHub)

04:48 - Tabris vs React, Cordova, and React Native

• Exposing Bluetooth Functionality

08:25 - Benefits/Advantages of Using Tabris

• j2v8

12:45 - Creating Panels and Flows

14:26 - Getting Started Experience

16:40 - Handling Updates; Live Updating

• The Tabris.js Developer App
• Will Apple eventually ever have to give in?

25:15 - Views (Declarative and Imperative UI)

• Ext JS

29:09 - "Write once, run anywhere." vs "Learn once write anywhere."

35:21 - Why have other projects failed or not failed?

• Xamarin

39:41 - What does it mean to be statically compiled?

40:44 - Styling: Creating a Middle Group that Looks and Feels Good (iOS vs Android)

• Cross-platform Logic and Ecosystems

47:51 - ES6 Implications

49:29 - Plugins

• CocoaPods and Widgets'

Picks

Star Wars Essentials (AJ)
Star Wars: The Force Awakens (AJ)
Thing Explainer: Complicated Stuff in Simple Words by Randall Munroe (AJ)
James Edwards: Making a Mini-Lisp: Introduction to Transpilers (Aimee)
Nick Saban (Aimee)
Lloyd Borrett: Bill Gates and Petals Around the Rose (Jamison)
Dan Luu: Normalization of Deviance in Software: How Completely Broken Practices Become Normal (Jamison)
Craig Stuntz: Programs that Write Programs: How Compilers Work (Jamison)
Microsoft (Dave)
Tina Fey (Dave)
thoughtram Blog (Dave)
Pascal Precht (Dave)
CES (Chuck)
The Modern Team (Ian)
Eric Elliott (Ian)
Thinking, Fast and Slow by Daniel Kahneman (Jochen)

JSJ 275: Zones in Node with Austin McDaniel

The panel for this week on JavaScript Jabber is Cory House, Aimee Knight, and Charles Max Wood. They speak with special guest Austin McDaniel about Zones in Node. Tune in to learn more about this topic!

[00:01:11] Introduction to Austin

Austin has worked in JavaScript for the past ten years. He currently works in Angular development and is a panelist on Angular Air. He has spent most of his career doing work in front-end development but has recently begun working with back-end development. With his move to back-end work he has incorporated front-end ideas with Angular into a back-end concept.

[00:02:00] The Way it Works

NodeJS is an event loop. There is no way to scope the context of a call stack. So for example, Austin makes a Node request to a server and wants to track the life cycle of that Node request. Once deep in the scope, or deep in the code, it is not easy to get the unique id. Maybe he wants to get the user from Passport JS. Other languages – Python, Java – have a concept called thread local storage. They can associate context with the thread and throughout the life cycle of that request, he can retrieve that context.

There is a TC39 proposal for zones. A zone allows you to do what was just described. They can create new zones and associate data with them. Zones can also associate unique ids for requests and can associate the user so they can see who requested later in the stack. Zones also allow to scope and create a context. And then it allows scoping requests and capturing contacts all the way down.

[00:05:40] Zone Uses

One way Zone is being used is to capture stack traces, and associating unique ids with the requests. If there is an error, then Zone can capture a stack request and associate that back to the request that happened. Otherwise, the error would be vague.

Zones are a TC39 proposal. Because it is still a proposal people are unsure how they can use it. Zones are not a new concept. Austin first saw Zones being used back when Angular 2 was first conceived. If an event happened and they wanted to isolate a component and create a scope for it, they used Zones to do so. Not a huge fan of how it worked out (quirky). He used the same library that Angular uses in his backend. It is a specific implementation for Node. Monkey patches all of the functions and creates a scope and passes it down to your functions, which does a good job capturing the information.

[00:08:40] Is installing the library all you need to get this started?

Yes, go to npminstallzone.js and install the library. There is a middler function for kla. To fork the zone, typing zone.current. This takes the Zone you are in and creates a new isolated Zone for that fork. A name can then be created for the Zone so it can be associated back with a call stack and assigned properties. Later, any properties can be retrieved no matter what level you are at.

[00:09:50] So did you create the Zone library or did Google?

The Google team created the Zone library. It was introduced in 2014 with Angular 2. It is currently used in front-end development.

[00:10:12] Is the TC39 proposal based on the Zone library?

While Austin has a feeling that the TC39 proposal came out of the Zone library, he cannot say for sure.

[00:10:39] What stage is the proposal in right now?

Zone is in Stage Zero right now. Zone JS is the most popular version because of its forced adoption to Angular. He recommends people use the Angular version because it is the most tested as it has a high number of people using it for front-end development.

[00:11:50] Is there an easy way to copy the information from one thread to another?

Yes. The best way would probably be to manually copy the information. Forking it may also work.

[00:14:18] Is Stage Zero where someone is still looking to put it in or is it imminent?

Austin believes that since it is actually in a stage, it means it is going to happen eventually but could be wrong. He assumes that it is going to be similar to the version that is out now. Aimee read that Stage Zero is the implementation stage where developers are gathering input about the product. Austin says that this basically means, “Implementation may vary. Enter at your own risk.”

[00:16:21] If I’m using New Relic, is it using Zone JS under the hood?

Austin is unsure but there something like that has to be done if profiling is being used. There has to be a way that you insert yourself in between calls. Zone is doing that while providing context, but probably not using Zone JS. There is a similar implementation to tracing and inserting logging in between all calls and timeouts.

[00:17:22] What are the nuances? Why isn’t everybody doing this?

Zone is still new in the JavaScript world, meaning everyone has a ton of ideas about what should be done. It can be frustrating to work with Zone in front-end development because it has to be manually learned. But in terms of implementation, only trying to create a context. Austin recommends Zone if people want to create direct contacts. The exception would be 100 lines of Zone traces because they can get difficult.

Another issue Austin has is Node’s native basic weight. Weight hooks are still up in the air. The team is currently waiting on the Node JS community to provide additional information so that they can finish. Context can get lost sometimes if the wrong language is used. He is using Typescript and doesn’t have that problem because it is straightforward.

[00:21:44:] Does this affect your ability to test your software at all?

No, there have not been any issues with testing. One thing to accommodate for is if you are expecting certain contexts to be present you have to mock for those in the tests. After that happens, the tests should have no problems.

Picks

Cory:

• Apple AirPods

Aimee:​

• Blackmill
• Understanding Zones

Charles:

• Classical Reading Playlist on Amazon
• Building stairs for his dad
• Angular Dev Summit 

Austin:

• NGRX Library Redux 

Links

• Twitter
• GitHub

Panel: 

Charles Max Wood

Guest: Austin McDaniel

This week on My JavaScript Story/My Angular Story, Charles speaks with Austin McDaniel. Austin is a return guest and was previously featured on JavaScript Jabber episode 275 . Austin talks about his journey getting into programming as an 11year old, to recently, as a web developer with more complex technologies. Austin talks about building widgets, working in Angular, JavaScript, and more in-depth web development on many different platforms. Lastly, Austin talks about his contributions to NGX Charts and speaking at a variety of developer conferences.

In particular, we dive pretty deep on: 

• How did you get into programming? 11 years old
• Cue Basic
• Web developer
• College jobs was in web developing
• IE6
• Building Widgets
• Components
• jquery 
• Web is the future
• How did you get into Angular? 2013, v1.2
• Backbone
• Angular 1 & 2
• NG X Charts
• Speaking at Conferences
• Augmented Reality and VR
• Web AR
• Angular Air Podcast
• Working as a contractor with Google
• and much, much more!

Links: 

• JavaScript Jabber episode 275
• jquery
• http://amcdnl.com
• Angular Air Podcast
• @amcdnl
• github.com/amcdnl
•  

Picks

Austin

• Todd Motto 

Charles

• NG Conf
• Angular Dev Summit
• Angular Air Podcast

Guest Paige Niedringhaus has been a developer full time for 3 years, and today she is here to talk about Node 12. One of the things she is most excited about is the ES6 support that is now available, so things that used to require React, Angular, or Vue can now be done in Node. The require function will not have to be used in Node 12. AJ is worried about some of these changes and expresses his concerns. Paige assures him that in the beginning you won’t have to switch things to imports. You may have to change file extensions/types so Node can pick up what it’s supposed to be using. They are also trying to make it compatible with CommonJS.

Node 12 also boasts an improved startup time. The panel discusses what specifically this means. They talk about the code cache and how Node caches the built in libraries that it comes prepackaged with. The V8 engine is also getting many performance enhancements. 

Paige talks about the shift from promises to async. In Node 12, async functions will actually be faster than promises. They discuss some of the difficulties they’ve had in the past with Async08, and especially callbacks. 

Another feature of Node 12 is better security. The transcripted security layer (TLS), which is how Node handles encrypted strains of communication, is upgrading to 1.3. The protocol is simpler to implement, quicker to negotiate sessions between the applications, provides increased end user privacy, and reduces request time. Overall, this means less latency for everybody. 1.3 also gets rid of the edge cases that caused TLS to be way far slower than it needed to be. 

The conversation turns to properly configuring default heap limits to prevent an ‘out of memory’ error. Configuring heap limits is something necessary when constructing an incredibly large object or array of objects. Node 12 also offers formatted diagnostic summaries, which can include information on total memory, used memory, memory limits, and environment lags. It can report on uncaught exceptions and fatal errors. Overall, Node 12 is trying to help with the debugging process. They talk about the different parsers available and how issues with key pairing in Node have been solved. 

Paige talks about using worker threads in Node 12. Worker threads are really beneficial for CPU intensive JavaScript operations. Worker threads are there for those things that eat up all of your memory, they can alleviate the load and keep your program running efficiently while doing their own operations on the sideline, and returning to the main thread once they’ve finished their job. None of the panelists have really used worker threads, so they discuss why that is and how they might use Worker Threads in Node 12. 

In addition, Node 12 is making Native module creation and support easier, as well as all the different binaries a node developer would want to support. Paige makes it a point to mention the new compiler and minimum platform standards. They are as follows:

• GCC minimum 6

• GLIVC minimum 2.17 on platforms other than Mac and Windows (Linux)

• Mac users need at least 8 and Mac OS 10.10

• If you’ve been running node 11 builds in Windows, you’re up to speed

• Linux binaries supported are Enterprise Linux 7, Debian 8, and Ubuntu 14.04

• If you have different requirements, go to the Node website

Panelists

• J.C. Hyatt

• Steve Edwards

• AJ O’Neal

With special guest: Paige Niedringhaus

Sponsors

• Tidelift

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

• Sustain Our Software

Links

• Async

• CommonJS

• njs

• Promise

• Node

• Event Stream

• llhttp

• llparse

• LLVM

• Papa Parse

• Json.stringify 

• Json.parse

• Optimizing Web Performance TLS 1.3

• Overlocking SSL

• Generate Keypair

Follow DevChatTV on Facebook and Twitter

Picks

J.C. Hyatt:

• AWS Amplify framework

• 12 Rules for Life: An Antidote to Chaos by Jordan Petersen

• React and Gatsby workshops

Steve Edwards:

• The Farside comic coming back?

AJ O’Neal:

• Field of Hopes and Strings

• Link’s Awakening

• Dune

Paige Niedringhaus:

• DeLonghi Magnifica XS Automatic Espresso Machine, Cappuccino Maker

• CONNECT.TECH Conference

Follow Paige on Twitter, Medium, and Github

JavaScript Remote Conf 2020

May 14th to 15th - register now!

Paige Niedringhaus started her career as a Digital Marketer before making the move to becoming a software developer at the Home Depot. She current works with React and Node building internal apps for them. This episode discusses the ins and outs of making that transition in a semi-recent world and community.

Host: Charles Max Wood

Joined By Special Guest: Paige Niedringhaus

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

• JSJ 398: Node 12 with Paige Niedringhaus

• Syntax.

• GitHub testing-library/react-testing-library

• Gatsby

• NextJS

• Interview Cake

• Medium - Paige Niedringhaus

• Follow Paige on Twitter: @pniedri

Picks

Paige Niedringhaus:

• Breville Milk Frother

• Stuff You Should Know

Charles Max Wood:

• Instant Pot

• Sphero BB-8

Lause, Mark A

Austin, James H., 1925-

Austin, James H., 1925-

Australia. Parliament. Senate. Environment and Communications References Committee, author

Kondo, Manabu, author

Castro, Peter, author

Davis, John K., author

Australia. Parliament. Senate. Environment and Communications References Committee, author, issuing body

Yeo, Sue-Yee Sharon, author

Coen, Natasha Jeanne, author

Knauss, John A., author

Martin, Sarah, author

Edger, Graham, author, photographer

Jackson, W. J., author

Murray-Darling Basin Authority (Australia)

Hart, Barry T., author

Frid, Chris, author

Australia. Productivity Commission, author, issuing body

Archer, John, 1941-

Valentine, Peter Sinclair, author

Ebel, Hans Friedrich

Saito, R. (Riichiro)

Shah, Monali, author

Anglican Church of Australia, author

Chilton, Hugh, author

Riches, Tanya, author

Interview with Andrew J. Dannenberg, MD, author of Association of Body Fat and Risk of Breast Cancer in Postmenopausal Women With Normal Body Mass Index: A Secondary Analysis of a Randomized Clinical Trial and Observational Study

Interview with Katrina E. Abuabara, MD, MA, MSCE, author of Assessment of Sleep Disturbances and Exhaustion in Mothers of Children With Atopic Dermatitis

Interview with Sarah Larney, PhD, author of All-Cause and Cause-Specific Mortality Among People Using Extramedical Opioids: A Systematic Review and Meta-analysis