Norman, M. A

Norman, M. A

Cromer, E. L

Norman, M. A

Deer, W. A. (William Alexander), author

Gilligan, Rorie Alexander, author

Raghavan, V., author

02:24 - Robert Damphousse Introduction

02:40 - OAuth

• OpenID
• JWT

07:15 - Stormpath

• @gostormpath
• [GitHub] Stormpath
• Blog

08:38 - Authorization Information Storage

11:29 - Stormpath Authentication vs OAuth Authentication

• Resource Owner Password Credentials Grant

14:43 - Caching

15:41 - Building Backends as a Service?

18:21 - Security

19:12 - Using Cassandra

• Stormpath in Planet Cassandra: 50k Accounts Imported in Under 200ms

20:27 - Use Cases

22:27 - Authentication as a Service

23:40 - 2FA (Two Factor Authentication)?

24:07 - REST APIs

• Launch a SaaS – and Battle Your Robot – With Stormpath

25:39 - Making Complete Apps

• FullContact
• Firebase

26:33 - Security (Cont’d)

27:34 - In-Between Layer (Authentication API)

28:40 - Browser-Based vs Mobile Application Use

29:44 - Angular, React, Flux,

32:02 - React Native?

33:05 - Stormpath Life Expectancy

35:09 - Customers

36:12 - Active Directory, LDAP (Lightweight Directory Access Protocol)

37:05 - Support and Pricing

Picks

Putting the "fun" back in "funeral"! Celebrating the death of old IE browsers on January 12! (Dave)
Giant Star Wars LEGO Super Star Destroyer Shattered at 1000 fps | Battle Damage (Dave)
GitLab (Dave)
Allen Pike: JavaScript Framework Fatigue (Aimee)
The Cult of Work You Never Meant to Join (Aimee)
Serial (AJ)
HotPlate (AJ)
Design Patterns in C (AJ)
OAuth3 (AJ)
JS Remote Conf Videos (Chuck)
Ruby Remote Conf (Chuck)
Traction: Get a Grip on Your Business by Gino Wickman (Chuck)
Startups For the Rest of Us (Chuck)
The Guest House: A Poem (Robert)
The Hiring Post (Robert)
Front-end Job Interview Questions (Robert)

Submit a talk or buy a ticket! Check out JS Remote Conf!

02:30 - Nik Molnar Introduction

• Twitter
• GitHub
• Blog

02:50 - What Microsoft’s Cross-Platform and Open Tooling Team Does

03:41 - Microsoft and Open Source

05:25 - Performance

08:15 - Is good, clean architecture at odds with high-performance code?

09:41 - Latency and Bandwidth

• Moore’s Law

20:23 - Hierarchy of Needs for Users of Software

• Aaron Walter: Emotional Interface Design: The Gateway to Passionate Users
• Maslow’s Hierarchy of Needs

24:36 - Controlling Performance

• “Performance Budget”

26:21 - The Cost of Performance (ROI)

31:57 - Speed Index

• WebPagetest

41:50 - Avoiding the “It feels fast on my machine” Syndrome

45:03 - RUM = Real User Monitoring

• Navigation Timing
• Resource Timing
• User Timing

46:24 - Synthetic Testing

47:50 - Performance Audits

• OODA Loop
  • Observe
  • Orient
  • Decide
  • Act

50:39 - Do Less

More From Nik

• Nik Molnar: Full Stack Web Performance
• Nik Molnar: Tracking Real World Web Performance
• Navigation Timing API
• Resource Timing: W3C Working Draft 20 October 2015

Picks

UtahJS 2015 (Dave)
ES6 Overview in 350 Bullet Points (Jamison)
Saturday Morning Breakfast Cereal (High Frequency Training) (Jamison)
Chris Zacharias: Page Weight Matters (Jamison)
React Rally Talks (Jamison)
MONEY Master the Game: 7 Simple Steps to Financial Freedom by Tony Robbins (Chuck)
Rush Revere and the Star-Spangled Banner by Rush Limbaugh (Chuck)
Visual Studio Code (Nik)
High Performance Browser Networking by Ilya Grigorik (Nik)
Nik's Pluralsight Courses (Nik)

There’s still time! Check out and get your JS Remote Conf tickets!

JavaScript Jabber Episode #184: Web Performance with Nik Molnar (Part 1)

02:04 - Nik Molnar Introduction

• Twitter
• GitHub
• Blog
• Glimpse
• [Pluralsight] WebPageTest Deep Dive

02:58 - RAIL (Response, Animation, Idle, Load)

06:03 - How do you know what is being kicked off? How do you avoid it?

08:15 - Frame Rates

• frames-per-second.appspot.com
• CSS Triggers

16:05 - Scrolling

• requestAnimationFrame

19:09 - The Web Animation API

21:40 - Animation Accessibility, Usability, and Speed

• haveibeenpwned.com
• Ilya Grigorik: Speed, Performance, and Human Perception @ Fluent 2014

27:14 - HTTP and Optimization

• Yesterday's perf best-practices are today's HTTP/2 anti-patterns by Ilya Grigorik
• Ruby Rogues Episode #135: HTTP 2.0 with Ilya Grigorik
• Hypertext Transfer Protocol Version 2 (HTTP/2)
• Can I use...
• Server Push

35:25 - ES6 and Performance

• ES6 Feature Performance
• six-speed

40:46 - Understanding the Scale

• Grace Hopper: Nanoseconds
• Grace Hopper on Letterman

43:30 RAIL (Response, Animation, Idle, Load) Cont’d

46:15 - Navigator.sendBeacon()

47:51 - Memory Management and Garbage Collection

• Memory Management Masterclass with Addy Osmani
• Addy Osmani: JavaScript Memory Management Masterclass
• Under the Hood of .NET Memory Management by Chris Farrell and Nick Harrison (Nik)
• Memory vs Performance Problems
• Rick Hudson: Go GC: Solving the Latency Problem @ GopherCon 2015

Picks

Hardcore History Podcast (Jamison)
Static vs. Dynamic Languages: A Literature Review (Jamison)
TJ Fuller Tumblr (Jamison)
Pickle Cat (Jamison)
WatchMeCode (Aimee)
Don’t jump around while learning in JavaScript (Aimee)
P!nk - Bohemian Rhapsody (Joe)
Rich Hickey: Design, Composition and Performance (Joe)
Undisclosed Podcast (AJ)
History of Gaming Historian - 100K Subscriber Special (AJ)
15 Minute Podcast Listener chat with Charles Wood (Chuck)
JS Remote Conf (Chuck)
All Remote Confs (Chuck)
Clash of Clans (Chuck)
Star Wars Commander (Chuck)
Coin (Chuck)
The Airhook (Chuck)
GoldieBlox (Chuck)

This episode was recorded live from The Microsoft Build Conference 2016. In this episode we chatted with Rob Wormald of the Angular Core team at Google about Angular. You can follow him on Twitter, or check out what he’s done over on GitHub.

Picks

• Visual Studio Code (Rob)
• Service Workers (Rob)
• Richard Campbell and Carl Franklin from .NETRocks (Chuck)

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)

JSJ 272: Functional Programming and ClojureScript with Eric Normand

This episode of JavaScript Jabber features panelists Aimee Knight and Charles Max Wood. Special guest Eric Normand is here to talk about functional programming and ClojureScript. Tune in to learn more!

[00:1:14] Introduction to Eric Normand

Eric works for purelyfunctional.tv. The main target market for his company is those people who want to transition into functional programming from their current job. He offers them support, shows them where to find jobs, and gives them the skills they need to do well.

[00:02:22] Address that quickly

Functional programming is used at big companies such as Wal-Mart, Amazon, EBay, Paypal, and banks. They all have Clojure but it is not used at the scale of Java or Ruby.

So yes, people are using it and it is influencing the mainstream programming industry.

[00:3:48] How do you build an application?

A common question Eric gets is, “How do I structure my application?” People are used to using frameworks. Most start from an existing app. People want a process to figure out how to take a set of features and turn it into code. Most that get into functional programming have development experience. The attitude in functional programming is that they do not want a framework. Clojure needs to be more beginner friendly. His talk is a four-step process on how to turn into code.

[00:05:56] Can you expand on that a little?

There are four steps to the process of structuring an application.

1. Develop a metaphor for what you are trying to do. Developing the first implementation. How would you build it if you didn’t have code?
2. Develop the operations. What are their properties? Example: will have to sort records chronological.
3. Develop relationships between the operations.
4. Run tests and refactor the program. Once you have that, you can write the prototype.

[00:13:13] Why can’t you always make the code better?

Rules can’t be refactored into new concepts. They have to be thrown away and started completely over. The most important step is to think before beginning to write code. It may be the hardest part of the process, but it will make the implementation easier.

[00:17:20] What are your thoughts on when people take it too far and it makes the code harder to read?

He personally has written many bad abstractions. Writing bad things is how you get better as a programmer. The ones that go too far are the ones that don’t have any basis or are making something new up. They are trying to be too big and use no math to back up their code.

[00:20:05] Is the hammock time when you decide if you want to make something abstract or should you wait until you see patterns develop?

He thinks people should think about it before, although always be making experiments that do not touch production.

[00:23:33] Is there a trade off between using ClojureScript and functional JavaScript?

In terms of functional programming in JavaScript don’t have some of the niceties that there are in Clojure script. Clojure Script has a large standard library. JavaScript is not as well polished for functional programming; it is a lot of work to do functional programming it and not as much support.

[00:27:00:] Dave Thomas believes that the future of software is functional programming. Do you agree?

Eric thinks that it seems optimistic. He doesn’t see functional programming take over the world but does think that it has a lot to teach. The main reason to learn functional programming is to have more tools in your toolbox.

[00:31:40] If this is a better way to solve these problems, why aren’t people using it?

There is a prejudice against functional programming. When Eric was first getting into it, people would ask why he was wasting his time. Believes that people are jaded. Functional programming feels foreign because people are used to a familiar way of programming; they usually start with a language and get comfortable.

[00:40:58] If people want to get started with it, is there an easy way in?

Lodash is great to start replacing for loops. It will clean up code. There are other languages that compile to JavaScript. For example, Elm is getting a lot of attention right now. It is a Haskell like syntax. If you want more of a heavyweight language, use TypeScript or PureScript. ClojureScript is into live programming. You are able to type, save, and see results of the code immediately on the screen in front of you.

Picks

Aimee:

• The Hidden Cost of Abstraction 
• What Functional Language Should I Learn 

Eric

• Steven King, On Writing 
• Youtube Channel: Tested  

Charles

• Ionic Framework

Links

• Purely Functional TV 
• Blog 
• Building Composable Abstractions 

Panel:

• Charles Max Wood
• AJ ONeal

Special Guests: Kurt Mackey

In this episode, the JavaScript Jabber panel talks to Kurt Mackey about Fly.io. At Fly.io, they are "building a JavaScript platform that gives you the power to build your own CDN." They talk about how Fly.io came to fruition, how CDN caching works, and what happens when you deploy a Fly app. They also touch on resizing images with Fly, how you actually build JavaScript platforms using Fly, and more!

In particular, we dive pretty deep on:

• Fly.io
• Building a programmable CDN
• High level overview of Fly.io
• How did this project come together?
• CDNs didn’t work with dynamic applications
• Has been working on this since 2008
• Extend application logic to the “edge”
• Putting burden of JavaScript “nastiest” onto the web server
• Fly is the proxy layer
• Getting things closer to visitors and users
• CDN caching
• Cache APIs
• Writing logic to improve your lighthouse score
• Have you built in resizing images into Fly?
• Managing assets closer to the user
• Can you modify your own JavaScript files?
• What happens when you deploy a Fly app
• Having more application logic
• DOM within the proxy
• Ghost
• React and Gatsby
• Intelligently loading client JavaScript
• How do you build the JavaScript platform?
• And much, much more!

Links:

• Fly.io
• JavaScript
• Ghost
• Gatsby
• React
• @flydotio
• @mrkurt
• Kurt at ARS Technica
• Kurt’s GitHub

Sponsors

• Kendo UI
• Sentry
• Digital Ocean

Picks:

Charles

• GitLab

AJ

• Gitea
• Black Panther

Kurt

• Packet.net
• The Three-Body Problem by Cixin Liu

Panel:

• Aimee Knight
• Charles Max Wood
• Christopher Ferdinandi (Boston)

Special Guests: Dan Shappir (Tel Aviv)

In this episode, the panel talks with Dan Shappir who is a computer software developer and performance specialist at Wix.com. As Dan states, his job is to make 100 million websites (hosted on the Wix platform) load and execute faster! Past employment includes working for companies, such as: Ericom, Ericom Software, and BackWeb. He studied at Technion Institute of Management and currently lives in Tel Aviv, Israel. The panel talks about web performance API among other things. Check it out!

Show Topics:

1:29 – Charles: Let us know who you are and why you’re famous!

1:39 – “Hello!” from Dan Shappir.

2:25 – Charles: You should say that you go to EACH site EVERY day out of the millions of sites out there.

2:53 – Charles: My mom mentioned Wix to me at first. My mom teaches High School Math.

3:16 – Dan: Yes that is our mission statement. That everyone can get a website without the knowledge of how to build a website.

3:52 – Aimee makes her comments.

3:59 – Dan: On our platform we try to offer people flexibility. There are bounds and limits, but people can do their very own thing, though. To make Wix faster because as we add more features and functionality that is our goal.

4:40 – Chuck: Okay, I know how to make X perform a little bit better. You are looking at a platform that controls TONS of sites, how do you even go about that?

4:58 – Dan: It is more difficult then that. We have millions of users leveraging the platform but there are a lot of developers in Wix who are developing the platform. I don’t think anyone at Wix has a total grasp of the complexity of the platform that we built. We have hundreds of frontend people working on our platform. All of them have pieces to the kingdom. We have processes in place with code reviews and whatnot, but there is so much going on. There is a change every 2 minutes, 24/7. We need to make sure progressing instead of regressing. 

6:54 – Aimee: I think it was interesting in one of the links you sent over. Because you know when something is getting worse you consider that a bug.

7:15 – Dan: It is more than a bug because if we see regression in performance then that is a problem. I can literally see any part of the organization and say, “stop” if it will

7:57 – Chuck: We are talking about performance, but what does that mean? What measures are there?

8:15: Dan: We are looking at performance can mean different things in different contents. User sites, for example, most important aspect is load time. How quickly the page loads and gets open to the viewer to that specific site. When they click something they want it instantly and no drag time. It does change in different contexts.

9:58 – Chuck: People do talk about load time. People have different definitions of it.

10:12: Dan: Excellent question. When you look at the different sites through Wix. Different people who build sites – load time can mean something else to everybody. It can mean when you see the MAIN text or the MAIN image. If it’s on an ECON site then how soon can they purchase or on a booking site, how long can the person book X product.

I heard someone at a conference say that load time is when: HERO TEXT And HERO IMAGE are displayed.

12:14 – Chuck: What is faster React or Vue?

12:21 – NEW HOST: Not sure. It all depends.

12:34 – Dan: We are big into React. We are one of the big React users outside of Facebook. I joined Wix four years ago, and even back then we were rebuilding our framework using React. One of our main modifications is because we wanted to do server-side rendered.

13:27 – Christopher asks Dan a question.

14:16 – Dan: We are in transition in this regard. Before we were totally client-site rendered, and that was the case until middle of last year. Then we deployed...

Dan: We are 100% server-side rendered now. Some things we are still using JavaScript. We have another project going on now and it’s fully CSS, and little JavaScript as possible. What you might want to do with that site is...

You might get in a few months every Wix site will be visible even if JavaScript is disabled.

16:26 – Aimee adds in her comments and observations to this topic.

16:55 – Dan: We don’t want things displayed incorrectly before it lays out. We hide the content while it’s downloading then make it visible. They lay-outing are done faster, because...

17:44 – Christopher asks Dan a question.

18:04 – Dan: I got into API...

Either you are moving forward or are you moving back. AKA – You are either progressing or regressing.

Different stages:

1.) Development stage

2.) Pre-Production (automated tools that check the performance with specific use cases)

3.) Check it out!

It’s beneficial to use these APIs.

21:11 – Christopher: What is performance APIs?

21:38 – Dan: There is a working group – Todd from Microsoft and others who are exposing the information (that is available in the browser) out into the browser. When the browser downloads a certain source (image, font, etc.) it can measure the various stages of downloading that feature.  You have these different sages of downloading this resource. The browser can measure each of these stages and then expose them to you. Basically it’s for the browser to expose this information to you and in a way that is coherent and uniform. It essentially maintains this buffer that puts performance entries sequentially.

Dan continues explaining this topic in detail.

25:55 – Dan: You have this internal buffer...

28:45 – Advertisement – Sentry – They support opensource.

29:39 – Christopher: everything you are saying seems that I can use this or that tab right now...

Why would I prefer the API to something visual, hypothetically?

30:03 – Dan: Three Different Stages. (See above.)

This information is very, very helpful during the developmental stage. Say you got a link from someone...

Dan mentions: Performance.mark

34:04 – Aimee: When you were talking about resource-ends. Many people don’t know what this is. Can you spend 2-3 minutes about how you guys are using these? Are there people can add for big bang for their buck?

34:41 – Dan: This might want to be a topic for its own podcast show.

Dan gives a definition of what a resource-end means.

Go back to fonts as an example.

Pre-connect for example, too.

39:03 – Dan: Like I said, it’s a huge topic.

You have to exercise some care. Bandwidth is limited. Make sure you aren’t blocking other resources that you do need right now.

40:02 – Aimee: Sounds like a lot of great things to tap into. Another question I have is about bundling.

40:27 – Dan: One of the things that we try to do (given that we are depending on the JavaScript we are downloading) we need to download JavaScript content to the client side. It has been shown often that JS is the most impactful resources that you need to download. You really want to be as smart as possible with that. What is even more challenging is the network protocols are changing.

Dan continues to go in-depth about this topic.

Dan: What we have found is that you want to strive to bundle resources together.

44:10 – Aimee: Makes sense.

44:15 – Dan continues talking about this topic.

45:23 – Chuck asks two questions. (First question is now and second question is at 51:32.)

2 Questions:

1. You gather information from web performance AI - What system is that?

45:42 – Dan: I am not the expert in that. I will try not to give misleading information. Actually let me phrase it different. There are 3^rd party tools that you can use leverage in your website. IF you are building for commercial reasons I highly recommend that you use performance-monitoring solution. I am not going to advertise one because there are tons out there. We ended up rolling out our own infrastructure because our use case is different than most.

At a conference I talked with a vendor and we talked about...

51:32 – 2^nd Question from Charles to Dan: Now you’ve gathered this information now what to you do? What patterns? What do you look for? And how do you decide to optimize things?

54:23 – Chuck: Back to that question, Dan. How should they react to it and what are they looking for

54:41 – Dan: Three main ways: 1.) Generate alerts 2.) See trends over long period of time 3.) Looking at real-time graphs.

Frontend developer pro is that likely being woken up in the middle of the night is lower. We might be looking at the real time graph after we deployed...

57:31 – Advertisement – Get a Coder Job!

58:10 – Picks!

Links:

• JavaScript
• jQuery
• React
• Elixir
• Elm
• Vue
• Wix
• Window Performance
• Web Performance
• Terra Genesis
• Terra Genesis: Space Colony
• The One Thing
• DevChat TV – YouTube
• GitHub: Off Side
• HBO: Insecure
• Wix: Engineering
• JavaScript Riddle
• JavaScript Riddles for Fun and for Profit
• Dan Shappir’s Twitter
• Dan Shappir’s LinkedIn
• Dan Shappir’s Crunch Base
• Dan Shappir’s GitHub
• Dan Shappir’s Talk through Fluent
• Dan Shappir’s Medium
• Dan Shappir’s YouTube Talk: JavaScript riddles for fun and profit

Sponsors:

• Code Badges
• Kendo UI
• Sentry
• Digital Ocean
• Cache Fly
•  

Picks:

Aimee:

• Waking up early!
• How to Deal with Dirty Side Effects in Your Pure Functional JavaScript

Chris:

• Offside - Toomuchdesign
• Insecure TV Show

Charles:

• Terraform - Game
• “The One Thing"
• Code Badge
• DevChat on YouTube

Dan

• Wix Engineering
• JavaScript Riddle

JavaScript Remote Conf 2020

May 14th to 15th - register now!

Dan Shappir takes the lead to explain all of the acronyms and metrics for measuring the performance of your web applications. He leads a discussion through the ins and outs of monitoring performance and then how to improve and check up on how your website is doing.

Panel

• AJ O’Neal
• Aimee Knight
• Steve Edwards
• Dan Shappir

Sponsors

• Taiko, free and open source browser test automation
• Educative.io | Click here for 10% discount

____________________________________________________________

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

____________________________________________________________

Links

• <picture>: The Picture element - HTML: Hypertext Markup Language | MDN

Picks

AJ O’Neal:

• The Way of Kings
• Taco Bell

Aimee Knight:

• web.dev
• @DanShappir

Dan Shappir:

• New accessibility feature in Chrome Dev Tools: simulate vision deficiencies, including blurred vision & various types of color blindness. In Canary at the bottom of the Rendering tab.
• Better Call Saul

Follow JavaScript Jabber on Twitter > @JSJabber

Bell, Vereen M., 1934-

Moon, Krystyn R., 1974-

Mallett, Margaret

Young, Vershawn Ashanti

Winkler, Ira

Australia. Bureau of Meteorology

Probert, P. Keith, author

Trujillo, Alan P., author

Alegre, Helena, author

Australia. Productivity Commission, author, issuing body

Trujillo, Alan P., author