au

Modern physical metallurgy and materials engineering / contributors, William A. Brantley, Satish B. Alapati et al ; [edited and compiled by Auris Reference Editorial Board]




au

Govt. will take up safety audit of 86 industries, says Mekapati

‘It may take up to 48 hours to neutralise styrene vapours’




au

006 JSJ Chrome Dev Tools with Paul Irish

The panelists discuss Chrome dev tools with Paul Irish.




au

099 JSJ npm, Inc. with Isaac Schlueter, Laurie Voss, and Rod Boothby

The panelists discuss npm, Inc. with Isaac Schlueter, Laurie Voss, and Rod Boothby.




au

122 JSJ Socket.IO with Guillermo Rauch

The panelists talk to Guillermo Rauch about Socket.io.




au

146 JSJ React with Christopher Chedeau and Jordan Walke

The panelists talk to Christopher Chedeau and Jordan Walke about React.js Conf and React Native.




au

157 Moving Your Rendering Engine to React with Amit Kaufman and Avi Marcus

02:43 - Amit Kaufman Introduction

03:07 - Avi Marcus Introduction

04:35 - Why Move Your Rendering Engine to React?

07:25 - Using JavaScript

09:57 - Business Process and Progression (Getting Managerial Approval)

12:46 - Manipulation

15:11 - Layout and Performance

  • Measuring and Patching

20:21 - Building Client-Side Applications in General

  • Abstraction
  • Make Code Predictable and Clear
  • Have a Goal

26:00 - Events

29:30 - Storage

  • Lazy Components

31:31 - Immutability

34:36 - Flux and Keeping Code Maintainable

  • Packages

38:19 - Two-way Data Binding

Picks

Notes on the book "Art & Fear" by David Bayles & Ted Orland (Jamison)
Papers (Jamison)
Dynamo: Amazon’s Highly Available Key-value Store (Jamison)
LDS Conference Talks (AJ)
Stephen Young: Why your code is so hard to understand (Aimee)
Kombucha (Aimee)
Pascal Precht: Integrating Web Components with AngularJS (Pascal)
Template Syntax Constraints and Reasoning (Design Doc) (Pascal)
RUNNING WITH RIFLES (Joe)
[Pluralsight Webinar] AngularJS 2.0: What you need to know with Joe (Joe)
Whiplash (Amit)
Dan Ariely: What makes us feel good about our work? (Amit)
React Templates (Amit)
Esprima (Avi)
Big Hero 6 (Avi)

 

Check out and sign up to get new on React Rally: A community React conference on August 24th and 25th in Salt Lake City, Utah!




au

163 JSJ Flow with Jeff Morrison and Avik Chaudhuri

03:32 - Jeff Morrison Introduction

03:46 - Avik Chaudhuri Introduction

04:27 - Flow

05:36 - Static Type Checking

09:52 - Flow and Unit Testing

12:39 - Gradual Typing

15:07 - Type Inference

17:50 - Keeping Up with New Features in JavaScript

20:49 - Generators

24:46 - Working on Flow

28:27 - Flow vs TypeScript

35:41 - Putting the “Java” Back in JavaScript

  • Server/Client Overview
  • Prototyping

45:26 - Flow and the JavaScript Community

46:43 - React Support

48:39 - Documentation

Picks

Nolan Lawson: We have a problem with promises (Aimee)
Jim 'N Nick's BBQ Restaurant (Aimee)
Frank McSherry: Scalability! But at what COST? (Jamison)
Frank McSherry: Bigger data; same laptop (Jamison)
Greg Wilson: What We Actually Know About Software Development, and Why We Believe It's True (Jamison)
Marron: Time-Travel Debugging for JavaScript/HTML Applications (Jeff)
Real World OCaml (Jeff)

Muse (Jeff)
Shtetl-Optimized (Avik)
Chef's Table (Avik)




au

166 JSJ New Relic with Wraithan and Ben Weintraub

02:27 - Coding House Scholarship Winners with AJ and Aimee

  • Emily Dreisbach (50% scholarship winner)
  • Blake Gilmore (50% scholarship winner)
  • Berlin Sohn (100% scholarship winner)

Congratulations from the panelists of JavaScript Jabber!

 

09:48 - Ben Weintraub Introduction

10:40 - Wraithan Introduction

11:01 - Why Care About Monitoring?

13:08 - Mixedpanel

13:57 - How it Works on the Backend

17:26 - New Relic’s CEO: Lew Cirne

18:37 - How the Node Agent Works

23:27 - Deciding Which Databases to Support

26:41 - Browser Monitoring

32:54 - Using Zombie.js?

34:11 - Tree of Causality

39:37 - Monetizing Aspect, Viewable Source/Source Available Code

47:28 - Performance

01:00:53 - New Relic

Picks

mraleph Blog (Wraithan)
v8-perf (Wraithan)
The Dear Hunter: A Night on the Town (Jamison)
React Rally (Jamison)
caddy (AJ)
Windows 10: Setup your Raspberry Pi 2 (AJ)
Remote debugging protocol (Ben)
Chrome Dev Tools Filmstrip View (Ben)




au

196 JSJ Tabris.js with Jochen Krause and Ian Bull

Check out Freelance Remote Conf and React Remote Conf!

 

02:31 - Jochen Krause Introduction

03:21 - Ian Bull Introduction

04:01 - Tabris.js

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

  • Exposing Bluetooth Functionality

08:25 - Benefits/Advantages of Using Tabris

12:45 - Creating Panels and Flows

14:26 - Getting Started Experience

16:40 - Handling Updates; Live Updating

25:15 - Views (Declarative and Imperative UI)

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

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

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

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)




au

197 JSJ Auth0 with Kassandra Perch

02:03 - Kassandra Perch Introduction

02:46 - Auth0

04:10 - Centralized Auth Services: Handing Out User Data to Third Parties

05:32 - Security, Storage, and Compliance

08:48 - Managing Session Data

09:35 - Cookies vs JSON Web Tokens (JWTs)

  • How Authentication Works

12:47 - OAuth

14:12 - Identification, Authorization, and Authentication

20:16 - Auth0 Infrastructure

22:10 - Using Node

23:06 - The Backend

24:25 - Documentation and Education

36:42 - The Value of OpenID Connect

38:25 - Identity

Picks

Add AJ on Tri-Force Heroes (AJ)
Making a Murderer (AJ)
Mazie's Girl Scout Digital Cookie Site (Aimee)
React (with Introduction to Flux Architecture) (Aimee)
Jordan Scales: Let’s Make A Webpage In 2016 (Jamison)
building-brooklynjs (Jamison)
Cult of the Party Parrot (Jamison)
CSS-Tricks (Jamison)
Auth0 Docs (Kassandra)
OpenID Foundation (Kassandra)
Mario & Luigi: Paper Jam (Kassandra)




au

203 JSJ Aurelia with Rob Eisenberg

Check out React Remote Conf!

 

02:31 - Rob Eisenberg Introduction

02:55 - Aurelia

03:43 - Selling People on Aurelia vs Other Frameworks

11:09 - Using Aurelia Without Directly Engaging with the API

  • Web Components

15:10 - Production Usage

18:46 - Specific Uses

23:03 - Durandal

25:26 - Aurelia and Angular 2

30:32 - Convention Over Configuration

34:56 - Web Components

  • Content Projection (Transclusion)
  • Polymer

41:13 - One-directional Data Flow; Data Binding

  • Using a Binding System as Messaging System

46:55 - Routing

49:47 - Animation

52:56 - Code Size

55:06 - Version Support

56:27 - Performance

  • Tools

01:00:20 - Aurelia in ES5

01:01:29 - Data Management

Picks

Crispy Bacon (Joe)
A Gentleman’s Guide to Love and Murder (Joe)
Jamison Dance: Rethinking All Practices: Building Applications in Elm @ React.js Conf 2016 (Joe)
Vessel | Lorn (Jamison)
The Moon Rang Like a Bell | Hundred Waters (Jamison)
The Top 10 Episodes of JavaScript Jabber (Chuck)
Amazon Prime (Chuck)
WiiU (Chuck)
Sketch (Rob)
Zeplin (Rob)
servo (Rob)




au

213 JSJ Developer Evangelism with Greg Baugues

Check out Newbie Remote Conf! July 13-15, 2016

 

02:16 - Greg Baugues Introduction

02:41 - Developer Evangelism

04:23 - Evangelism at Twilio

07:05 - “Evangelism”

10:56 - Getting the Word Out

13:28 - Keeping Up-to-Date

18:28 - Skills to Have as an Evangelist

  1. Technical Credibility
  2. Patience
  3. Empathy
  4. Hustle

21:21 - Getting Help From Companies

25:39 - Handling Larger-scale Issues

27:15 - Building an Evangelist Team

29:44 - Panelist Experiences with Evangelism

 

Picks




au

217 JSJ The Now Project with Guillermo Rauch

Check out Newbie Remote Conf and get your tickets!

 

02:24 - Guillermo Rauch Introduction

03:07 - Now: Realtime Node.js Deployments

04:28 - Key Concepts

10:22 - Deployment Process

14:55 - Getting Started Experience

17:22 - Technology vs Design

20:36 - Running Now vs npm-install

27:17 - Simplicity; SSH and Metrics

35:33 - Debugging and Performance

37:34 - Security

41:44 - What’s Next?

 

Picks




au

MJS #023 Laurie Voss


My JS Story 023 Laurie Voss

This week we have another My JavaScript story. This week’s guest is Laurie Voss. Laurie has worked with NPM from the start and has been a vital piece to getting it off the ground. Hear how Laurie got interested in computers, how Laurie got started with NPM, as well as a few things about the newly released NPM 5.


How did you get into programming?

Laurie started by going into a computer camp, at the time Laurie hadn’t spent time around computers, and it wouldn’t be until the second time that he went to the computer camp that he would see a computer again. Laurie grew up in Trinidad where not many people could afford computers. He started making his first website in Angelfire using HTML before CSS became a thing.

How did you go from web development to hardcore Javascript?

Laurie had been writing JavaScript since it was invented. Laurie started a web development company in high school using JavaScript. Laurie met Issac while working at Yahoo and he introduced Laurie to Node which was a starting point to taking JavaScript more seriously for Laurie. When Node was ready in 2013, NPM Inc was on it’s way.

What do you do at NPM Inc?

IN the beginning of 2014, Laurie was doing a lot of the JavaScript and was the CTO. Laurie says that part of his strategy has always been to hire JavaScript developers that are better at writing JavaScript that he is. Making him the worst JavaScript programmer at NPM. Laurie’s main job was doing what was needed to get NPM happen, including talking to layers and the business side of things. There are many companies that don’t understand how open source works, and in many cases it leads to run ins with lawyers. Many times NPM acts as an umbrella for open source tools that aren’t able to fight overzealous corporations.

What do you think is your biggest contributions to NPM?

Laurie expresses that it has changed over the years. A year ago he would say that he would have to say it leans towards the piece of software that is the registry. It’s very scalable and has worked great for small scale up to very large scale. Laurie works hard to gather funds and help make NPM grow as well as be scalable. He says that he is very proud that he build something that let’s others build things.

How did you get involved?

Laurie has been with NPM since the beginning. He tells us how Issac had been running NPM on donated hardware in spare time while working with Node. NPM would break a lot and be down due to the borrowed equipment. They decided that they needed to create a business model around NPM to help it grow. Laurie had just finished working on a startup and knew how to get funding and got their first round in 2014.

How did you get to being profitable?

Laurie talks about making sure that their plan is in line with their customers. NPM could easily charge for many parts of NPM but they would rather charge for things that make sense to charge, so in this case the private packages. Enough people are using the private package to getting NPM to profitability. Laurie says that even if money stopped coming in they would have to git rid of a few employees but would be able to keep a small team and sustain the NPM registry, but would never build anything new. It’s always between being profitable or using money to build new things.

What are you working on now?

NPM 5 was just released and it’s much faster, five times faster. Laurie talks about being excited about the team and what they are putting into it. Things like making deployments easier. Many developers use NPM to put code together as well as to deploy it. If you didn’t have a lock file, it’s possible that it would change. But the lock file can take a long time, and you already know what needs to go there so they are adding npm store and npm fetch making deploys much faster. Additionally they will be adding a feature called insights. They are able to see information about different users packages, security information, performance information, etc. They can use that information to help developers with suggestions based off of data gathered by what other people are doing. Charles adds that it would be great for coming up with topics for the podcast.

Anything else?

Laurie reminds everyone about NPM Organizations as well as NPM Enterprise. NPM Organizations is a way to organize packaging as well as teams of developers and helps you to collaborate. NPM Enterprise allows for single sign on support, license auditing, and features that corporations care about.


Picks

Laurie

Zite and NextJS
Slides.com

Charles

VMWorld
Tweet or email if you’re looking at resources for learning VR AI or Iot


Links

Twitter
NPM Organizations
NPM Enterprise





au

JSJ 275: Zones in Node with Austin McDaniel

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:

Aimee:

Charles:

Austin:

Links




au

MJS 041: Austin McDaniel

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: 

Picks

Austin

Charles




au

JSJ 342: Aurelia in Action with Sean Hunter

Panel:

  • AJ O’Neal
  • Joe Eames
  • Jesse Sanders

Special Guest: Sean Hunter

In this episode, the panel talks with Sean Hunter who is a software developer, speaker, rock climber, and author of “Aurelia in Action” published by Manning Publications! Today, the panelists and Sean talk about Aurelia and other frameworks. Check it out!

Show Topics:

0:00 – Advertisement: KENDO UI

0:38 – Joe: Hello! Our panelists are AJ, Jesse, myself, and our special guest is Sean Hunter (from Australia)! What have you been doing with your life and what is your favorite movie?

1:45 – Guest talks about Vegemite!

2:20 – Guest: I was in the UK and started using Aurelia, which I will talk about today. I have done some talks throughout UK about Aurelia. Also, the past year moved back to Australia had a baby son and it’s been a busy year. Writing a book and being a new parent has been hard.

3:22 – Panel: Tell us the history of Aurelia, please?

3:31 – Panel: Is it like jQuery, React, Vue or what?

3:44 – Guest: Elevator pitch – Aurelia is a single-page app framework! It’s most similar to Vue out of those frameworks; also, similarities to Ember.js.

4:30 – Guest goes into detail about Aurelia.

6:15 – Panel: It sounds like convention over configuration.

6:42 – Guest: Yes that is correct.

7:21 – Panel: Sounds like there is a build-step to it.

7:39 – Guest: There is a build-step you are correct. You will use Webpack in the background.

9:57 – The guest talks about data binding among other things.

10:30 – Guest: You will have your app component and other levels, too.

10:37 – Panel: I am new to Aurelia and so I’m fresh to this. Why Aurelia over the other frameworks? Is there a CLI to help?

11:29 – Guest: Let me start with WHY Aurelia and not the other frameworks. The style that you are using when building the applications is important for your needs. In terms of bundling there is a CUI and that is a way that I prefer to start my projects. Do you want to use CSS or Webpack or...? It’s almost a wizard process! You guys have any questions about the CLI?

14:43 – Panel: Thanks! I was wondering what is actually occurring there?

15:25 – Guest: Good question. Basically it’s that Aurelia has some built-in conventions. Looking at the convention tells Aurelia to pick the Vue model by name. If I need to tell the framework more information then...

17:46 – Panel: I think that for people who are familiar with one or more framework then where on that spectrum would Aurelia fall?

18:20 – Guest: It’s not that opinionated as Ember.js.

19:09 – Panel: Talking about being opinionated – what are some good examples of the choices that you have and how that leads you down a certain path? Any more examples that you can give us? 

19:38 – Guest: The main conventions are what I’ve talked about already. I can’t think of more conventions off the top of my head. There are more examples in my book.

20:02 – Panel: Your book?

20:10 – Guest: Yep.

20:13 – Panel.

20:20 – Guest. 

21:58 – Panel: Why would I NOT pick Aurelia?

22:19 – Guest: If you are from a React world and you like having things contained in a single-file then Aurelia would fight you. If you want a big company backing then Aurelia isn’t for you.

The guest goes into more reasons why or why not one would or wouldn’t want to use Aurelia.

24:24 – Panel: I think the best sell point is the downplay!

24:34 – Guest: Good point. What does the roadmap look like for Aurelia’s team?

25:00 – Guest: Typically, what happens in the Aurelia framework is that data binding (or router) gets pushed by the core team. They are the ones that produce the roadmap and look forward to the framework. The core team is working on the NEXT version of the framework, which is lighter, easier to use, and additional features. It’s proposed to be out for release next year.

26:36 – Advertisement – Sentry.io

27:34 – Panel: I am going to take down the CLI down and see what it does. I am looking at it and seeing how to teach someone to use it. I am using AU, new command, and it says no Aurelia found. I am stuck.

28:06 – Guest: What you would do is specify the project name that you are trying to create and that should create it for you. 

28:40 – Panel.

28:45 – Panel.

28:50 – Panel: Stand up on your desk and say: does anyone know anything about computers?!

29:05 – Panelists go back-and-forth.

29:13 – Panel: What frameworks have you used in the past?

29:17 – Guest: I was using single-paged apps back in 2010.

31:10 – Panel: Tell us about the performance of Aurelia?

31:17 – Guest: I was looking at the benchmarks all the time. Last time I looked the performance was comparable. Performances can me measured in a number of different of ways.

The guest talks about a dashboard screen that 20 charts or something like that. He didn’t notice any delays getting to the client.

33:29 – Panel: I heard you say the word “observables.”

33:39 – Guest answers the question.

35:30 – Guest: I am not a Redux expert, so I really can’t say. It has similar actions like Redux but the differences I really can’t say.

36:11 – Panel: We really want experts in everything! (Laughs.)

36:25 – Panelist talks about a colleagues’ talk at a conference. He says that he things are doing too much with SPAs. They have their place but we are trying to bundle 8-9 different applications but instead look at them as...

What are your thoughts of having multiple SPAs?

37:17 – Guest.

39:08 – Guest: I wonder what your opinions are? What about the splitting approach?

39:22 – Panel: I haven’t looked at it, yet. I am curious, though. I have been developing in GO lately.

40:20 – Guest: I think people can go too far and making it too complex. You don’t want to make the code that complex.

40:45 – Panel: Yeah when the code is “clean” but difficult to discover that’s not good.

41:15 – Guest: I agree when you start repeating yourself then it makes it more difficult.

41:35 – Panel: Chris and I are anti-framework. We prefer to start from a fresh palette and see if a framework can fit into that fresh palette. When you start with a certain framework you are starting with certain configurations set-in-place. 

42:48 – Joe: I like my frameworks and I think you are crazy!

43:05 – Panel.

43:11 – Joe: I have a love affair with all frameworks.

43:19 – Panel: I think I am somewhere in the middle.

43:49 – Panel: I don’t think frameworks are all bad but I want to say that it’s smart to not make it too complex upfront. Learn and grow.

44:28 – Guest: I think a good example of that is jQuery, right?

45:10 – Panelist talks about C++, jQuery, among other things.

45:34 – Guest: Frameworks kind of push the limits.

46:08 – Panelist talks about JavaScript, frameworks, and others.

47:04 – Panel: It seems simple to setup routes – anything to help with the lazy way to setup?

47:35 – Guest answers question.

48:37 – Panel: How do we manage complexity and how does messaging work between components?

48:54 – Guest: The simple scenario is that you can follow a simple pattern, which is (came out of Ember community) and that is...Data Down & Actions Up!

50:45 – Guest mentions that Aurelia website!

51:00 – Panel: That sounds great! Sounds like the pattern can be plugged in easily into Aurelia.

51:17 – Picks!

51:20 – Advertisement: Get A Coder Job!

END – Advertisement: CacheFly!

Links:

Sponsors:

Picks:

Joe

AJ

Jesse Sanders

Sean




au

JSJ 374: CosmosDB with Steve Faulkner LIVE at Microsoft BUILD

Sponsors

Panel

Charles Max Wood

Joined by Special Guest: Steve Faulkner

Episode Summary

Coming to you live from the podcast booth at Microsoft BUILD is Charles Max Wood with Steve Faulkner. Steve is a Senior Software Developer for Azure Cosmos DB at Microsoft. Cosmos DB is a global distributed, multi-model noSQL database. Steve explains the Cosmos DB service and scenarios it can be used in. They discuss how Cosmos DB interacts with Azure functions and how partition keys work in Cosmos DB.

Listen to the show for more Cosmos DB updates and to find out how Steve he got his twitter handle @southpolesteve.

Links

Picks

Steve Faulkner:




au

JSJ 384: FaunaDB: Support for GraphQL and Serverless Development with Evan Weaver

Sponsors

  • Sentry– use the code “devchat” for $100 credit 

Panel

  • Charles Max Wood

  • AJ O’Neal

  • Joe Eames

  • Aimee Knight

With Special Guest: Evan Weaver

Episode Summary

Evan Weaver is the CEO and cofounder of FaunaDB, a serverless database and a great way to get started with GraphQL. Evan talks about what went into building the FaunaDB and his background with Twitter. FaunaDB arose from trying to fix Twitter’s scalability issues, and the panel discusses scalability issues encountered in both large and small companies. They talk about the difference between transient and persistent data. They discuss how to develop locally when using a serverless database and the importance of knowing why you’re using something. Evan talks about how developing locally works with FaunaDB. He addresses concerns that people might have about using FaunaDB since it is not backed by a tech giant. Evan talks about some of the services FaunaDB offers and talks about the flexibility of its tools. He talks about how to get started with FaunaDB and what the authentication is like. Finally, Evan talks about some well known companies that are using FaunaDB and what they are doing with it. 

Links

Follow DevChat on Facebook and Twitter

Picks

Charles Max Wood:

Aimee Knight:

Joe Eames:

Evan Weaver




au

JSJ 397: Design Systems with Kaelig Deloumeau-Prigent

Kaelig Deloumeau-Prigent is a self taught web developer from west France. He has worked for BBC, The Guardian, and The Financial Times in the UK. He has also worked in the US for SalesForce and currently works for Shopify on their Polaris design system. Shopify has multiple design systems, and Polaris is open source. Today the panel is talking about design systems and developer tooling around design systems. 

To begin, Kaelig explains what a design system is. A design system is all of the cultural practices around design and shipping a product. It includes things like the words, colors, spacing grid system, and typography, plus guidance on how to achieve that in code. The panelists discuss what has made design systems so popular. Design systems have been around for a while, but became popular due to the shift to components, which has been accelerated by the popularity of React. The term design system is also misused by a lot of people, for it is much more than having a Sketch file. 

Next, they talk about whether design systems fall under the jurisdiction of a frontend developer or web designers. Kaelig has found that a successful design system involves a little bit of everyone and shouldn’t be isolated to one team. They talk about what the developer workflow looks like in a design system. It begins with thinking of a few common rules, a language, and putting it into code. As you scale, design systems can become quite large and it’s impossible for one person to know everything. You either give into the chaos, or you start a devops practice where people start to think about how we build, release, and the path from designer’s brain to production.

The panelists then talk about how to introduce a design system into a company where there are cultural conflicts. Kaelig shares his experience working with SalesForce and introducing a design system there. They discuss what aspects of a design system that would make people want to use it over what the team is currently doing. Usually teams are thankful for the design system. It’s important to build a system that’s complete, flexible, and extensible so that you can adapt it to your team. A good design system incorporates ‘subatomic’ parts like the grid system, color palette, and typography, referred to as design tokens. Design systems enable people to take just the bits of the design system that are interesting to them and build the components that are missing more easily. 

The conversation turns to the installation and upgrade process of a design system. Upgrading is left up to the customer to do on their own time in most cases, unless it’s one of the big customers. They talk about the role of components in upgrading a design system. Kaelig talks about the possibility of Shopify transitioning to web components. Kaelig shares some of his favorite tools for making a design system and how to get started making one. A lot of design teams start by taking a ton of screen shots and looking at all the inconsistencies.Giving them that visibility is a good thing because it helps get everyone get on the same page. The panelists talk about the role of upper management in developing components and how to prioritize feature development. Kaelig talks about what drives the decision to take a feature out. The two main reasons a feature would be removed is because the company wants to change the way things are done and there’s a different need that has arisen. The show concludes by discussing the possibility of a design system getting bloated over time. Kaelig says that Design systems takes some of the burden off your team, help prevent things from getting bloated, allow you to ship less code.

 

Panelists

  • Chris Ferdinandi

  • Aimee Knight

  • Steve Emmerich

With special guest: Kaelig Deloumeau-Prigent

Sponsors

Links

Follow DevChatTV on Facebook and Twitter

Picks

Steve Emmerich:

Aimee Knight:

Chris Ferdinandi:

Kaelig Deloumeau-Prigent:




au

JSJ 398: Node 12 with Paige Niedringhaus

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

Links

Follow DevChatTV on Facebook and Twitter

Picks

J.C. Hyatt:

Steve Edwards:

  • The Farside comic coming back?

AJ O’Neal:

Paige Niedringhaus:

Follow Paige on Twitter, Medium, and Github




au

MJS 135: Paul Cowan

My JavaScript Story this week welcomes Paul Cowan. Paul works as a consultant in front end development. He learned how to program at a really early age but didn't own an email address until he was 30 years old. When he was 30 years old he wanted to change his lifestyle and attended a course in London and took a job as a software developer.

Paul was interested in React because, for him, much of programming didn’t make a whole lot of sense until he read about the flux model and React Redux was one of the few frameworks that followed the flux model. Spending most of his life outside of the programming world has granted him a unique perspective framework like React.

 

Host: Charles Max Wood

Joined By Special Guest: Paul Cowan

Sponsors

______________________________________

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

______________________________________

Links

Picks

Paul Cowan:

Charles Max Wood:




au

MJS 136: Kaelig Deloumeau-Prigent

This My JavaScript Story episode is a discussion with Kaelig Deloumeau-Prigent. Kaelig works on the Polaris design system from Shopify. We walk through his journey into programming, HTML, and CSS. We wander through is career until he was building design systems at Shopify.

Host: Charles Max Wood

Joined By Special Guest: Kaelig Deloumeau-Pregent

Sponsors

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

  • CacheFly

___________________________________________________________________________________________

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

___________________________________________________________________________________________

Links

Picks

Kaelig Deloumeau-Prigent:

Charles Max Wood:




au

MJS 143: Paige Niedringhaus

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

______________________________________

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

______________________________________

Links

Picks

Paige Niedringhaus:

Charles Max Wood:




au

Yearning for the new age [electronic resource] : Laura Holloway-Langford and late Victorian spirituality / Diane Sasson

Sasson, Diane, 1946-




au

Yii rapid application development hotshot [electronic resource] : become a RAD hotshot with Yii, the world's most popular PHP framework / Lauren J. O'Meara, James R. Hamilton III

O'Meara, Lauren J




au

Yoga for children with autism spectrum disorders [electronic resource] : a step-by-step guide for parents and caregivers / Dion E. Betts and Stacey W. Betts ; forewords by Louise Goldberg and Joshua S. Betts

Betts, Dion E. (Dion Emile), 1963-




au

You gotta stand up [electronic resource] : the life and high times of John Henry Faulk / by Chris Drake

Drake, Chris




au

Young America [electronic resource] : land, labor, and the Republican community / Mark A. Lause

Lause, Mark A




au

Young brothers massacre [electronic resource] / Paul W. Barrett and Mary H. Barrett

Barrett, Paul W




au

A young Dutchman views post-Civil War America [electronic resource] : diary of Claude August Crommelin / Claude August Crommelin ; translated by Augustus J. Veenendaal, Jr. ; edited with an introduction by Augustus J. Veenendaal, Jr., and H. Roger Grant

Crommelin, Claude August, 1840-1874




au

Youth entrepreneurship and local development in Central and Eastern Europe [electronic resource] / edited by Paul Blokker, Bruno Dallago




au

Youth gangs [electronic resource] : causes, violence and interventions / John G. Cooper, editor




au

The Youth labor market problem [electronic resource] : its nature, causes, and consequences / edited by Richard B. Freeman and David A. Wise




au

Chevalier au lyon. English

Chrétien, de Troyes, active 12th century




au

Chevalier au lyon. English

Chrétien, de Troyes, active 12th century




au

Zane Grey [electronic resource] : his life, his adventures, his women / Thomas H. Pauly

Pauly, Thomas H




au

Zarathustra and the ethical ideal [electronic resource] : timely meditations on philosophy / Robert H. Cousineau

Cousineau, Robert Henri




au

ZBrush professional tips and techniques [electronic resource] / Paul Gaboury

Gaboury, Paul R




au

Zen and the brain [electronic resource] : toward an understanding of meditation and consciousness / James H. Austin

Austin, James H., 1925-




au

Zen-brain reflections [electronic resource] : reviewing recent developments in meditation and states of consciousness / James H. Austin

Austin, James H., 1925-




au

Zenana [electronic resource] : everyday peace in a Karachi apartment building / Laura A. Ring

Ring, Laura A., 1968-




au

A Zionist among Palestinians [electronic resource] / Hillel Bardin ; foreword by Mubarak Awad and Edward (Edy) Kaufman

Bardin, Hillel




au

A Woman in Her 20s With Chest Pain and Arm Claudication

This case report describes bilateral calcified coronary aneurysms with a significant proximal left anterior descending and right coronary artery stenoses immediately distal to the aneurysms.




au

Maurer family correspondence, 1945-1999 [New Finding Aid]

Chiefly correspondence dated 1954-1999 by writer Philip Roth to Robert Maurer and his wife, Charlotte Maurer, regarding Roth’s development as a writer, other professional work, and personal life. Also includes one letter between other Maurer family members dated 1945.




au

Contemporary U.S. Latinx literature in Spanish: straddling identities / Amrita Das, Kathryn Quinn-Sánchez, Michele Shaul, editors

Dewey Library - PQ7070.C65 2018




au

Latin American technopoetics: scientific explorations in new media / Scott Weintraub

Dewey Library - PQ7082.P7 W45 2018




au

[ASAP] Vertically Aligned Ag<sub><italic toggle="yes">x</italic></sub>Au<sub>1–<italic toggle="yes">x</italic></sub> Alloyed Nanopillars Embedded in ZnO as Nanoengineered Low-Loss Hybrid

Nano Letters
DOI: 10.1021/acs.nanolett.0c00790




au

State party report on the state of conservation of the Great Barrier Reef World Heritage Area (Australia) : in response to the World Heritage Committee decision WHC 38 COM 7B.63