International Symposium on Biohydrometallurgy (14th : 2001 : Ouro Preto, Minas Gerais, Brazil)

Manners, Ron (Ron B.)

Tropicana Joint Venture

ALTA Gold Ore Processing Symposium (1st : 2010 : Perth, W. A.)

ALTA Uranium Conference (6th : 2010 : Perth, W.A.)

ALTA Nickel/Cobalt/Copper Conference (1st : 2010 : Perth, W. A.)

Hydrometallurgy Meeting (39th : 2009 : Sudbury, Ont.)

ALTA Gold Conference (2nd : 2011 : Perth, W.A)

ALTA Uranium Conference (7th : 2011 : Perth, W.A)

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

Ndlovu, Sehliselo, author

Firm comes out with five schemes

‘Identify factories using poisonous gases and come up with a comprehensive report’

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

Panel Justin Searls (twitter github blog) Jamison Dance (twitter github blog) Joe Eames (twitter github blog) Merrick Christensen (twitter github) AJ O’Neal (twitter github blog) Charles Max Wood (twitter github Teach Me To Code) Discussion 01:33 - Justin Searls Test Double 02:14 - Jasmine Pivotal Labs 03:42 - Testing JavaScript 05:29 - CoffeeScript 07:22 - What Jasmine is Unit testing library RSpec DOM agnostic 10:16 - Testing the DOM 14:01 - Tragedy of the commons factory_girl 18:29 - Testing 23:53 - Syntax in Jasmine 26:23 - RSpec and Jasmine 28:07 - Async support in Jasmine 32:18 - Spies mockito Conditional stubbing jasmine-stealth jasmine-fixture 37:30 - jasmine-given Cucumber 43:19 - Running Jasmine jasminerice jasmine-rails jasmine-headless-webkit Testacular testem 49:17 - tryjasmine.com Picks Running MongoDB on AWS (Jamison) The Clean Coder by Robert C. Martin (Joe) Squire.js (Joe and Merrick) Rdio app (Merrick) Square (AJ) Allrecipes.com (AJ) Jenkins CI (Chuck) Apple’s Podcast app (Chuck) lineman (Justin) StarTalk Radio Show with Neil Degrasse Tyson (Justin) To The Moon PC Game (Justin) Transcript JAMISON:  Holy cow! JOE:  That was not annoying. CHUCK:  What’s not annoying? MERRICK:  He is punching a bag of Fritos? JOE:  Yeah. [Laughter] CHUCK:  Well, I was closing it up so they don’t get stale as fast. JOE:  You’re very thorough. Those are going to be the least stale… MERRICK:  Do you have like a Frito resealer or something? [Laughter] [Shrill sound] CHUCK:  Okay, sealed. [This episode is sponsored by Component One, makers of Wijmo. If you need stunning UI elements or awesome graphs and charts, then go to Wijmo.com and check them out.] [Hosting and bandwidth provided by the Blue Box Group. Check them out at Bluebox.net.] CHUCK:  Hey everybody, and welcome to Episode 38 of the JavaScript Jabber show. This week on our panel, we have Jamison Dance. JAMISON:  Hi guys! CHUCK:  Joe Eames. JOE:  Howdy? CHUCK:  Merrick Christensen. MERRICK:  What’s up? CHUCK:  AJ O’Neal is trying to join the call. He’s here. AJ:  Yo! Yo! Yo! Coming at you live from the Rental Agreement sphere of Provo, Utah. MERRICK:  He lives! CHUCK:  I’m Charles Max Wood from DevChat.tv. And this week, we have a special guest. That’s Justin Searls. JUSTIN:  Hello. CHUCK:  So, why don’t you tell us a little bit about yourself, Justin? JUSTIN:  Okay. Well, now that I’m on the spot, my name is Justin. I’m a software developer. I live in Columbus, Ohio. About a year ago, me and a guy named Todd Kaufman started a new company called Test Double. Previously, he and I had been doing consulting for a long, long time. And we’re up to eight people now. And we have a good time building software with an emphasis on terrific interaction design which has resulted in us kind of developing a specialty for well-crafted frontend code, predominantly JavaScript. And I imagine that’s probably why I’m here today. CHUCK:  Awesome. Alright. Well, we brought you on to talk about Jasmine. Jasmine was written by, was it Pivotal Labs?  JUSTIN:  Yeah, Pivotal Labs guys. A guy names Christian Williams who I think has since moved on to Square, and D.W. Frank who’s still at Pivotal. They wrote the core library and me and a whole bunch of other people in the community have piled on with different runners and add-ons and extensions in the sort of like little ecosystem of the 25 people who write unit tests for JavaScript. CHUCK:  All 25 of you, huh? JUSTIN:  Well, it’s not a lot, right? It’s been a fun journey of being one of the very few people who really, really got excited or chose to get excited about making it easier for folks to write tests in JavaScript or as easy as it would be for whatever servers and language they’d be using.

02:52 - David Herman Introduction

• Twitter
• Blog
• JavaScript Jabber Episode #54: JavaScript Parsing, ASTs, and Language Grammar w/ David Herman and Ariya Hidayat
• JavaScript Jabber Episode #44: Book Club! Effective JavaScript with David Herman
• Effective JavaScript by David Herman
  • @effectivejs
• TC39
• Mozilla

03:50 - The Rust Programming Language

• [GitHub] rust

06:31 - “Systems Programming Without Fear”

07:38 - High vs Low-level Programming Languages

• Garbage Collection and Deallocation
• Memory Safety
• Performance and Control Over Performance

11:44 - Stack vs Heap Memory

• Etymology of "Foo"
• RAII (Resource Acquisition Is Initialization)

16:52 - The Core of Rust

• Ownership
• Type System

24:23 - Segmentation Fault (Seg Faults)

27:51 - How much should programmers care about programming languages?

• Andrew Oppenlander: Rust FFI (Embedding Rust in projects for safe, concurrent, and fast code anywhere.)

32:43 - Concurrency and Multithreaded Programming

35:06 - Rust vs Go

37:58 - servo

40:27 - asm.js

• emscripten

42:19 - Cool Apps Built with Rust

• Skylight
• Wit.ai

45:04 - What hardware architectures does the Rust target?

45:46 - Learning Rust

• Rust for Rubyists by Steve Klabnik

Picks

Software Engineering Radio (Dave)
How Will You Measure Your Life? by Clayton M. Christensen (Dave)
The Presidents of the United States of America (Dave)
Design Patterns in C (AJ)
Microsoft Edge Dev Blog: Bringing Asm.js to Chakra and Microsoft Edge (AJ)
The Web Platform Podcast: Episode 43: Modern JavaScript with ES6 & ES7 (AJ)
Firefox Fame Phone (AJ)
iTunes U CS106A (Programming Methodology) (Aimee)
Valerian Root on Etsy (Aimee)
The Dear Hunter - Live (Jamison)
Designing Data-Intensive Applications by Martin Kleppmann (Jamison)
Fogus: Perlis Languages (Jamison)
Galactic Civilizations III (Joe)
Visual Studio Code (Joe)
Tessel 2 (Dave)
Event Driven: How to Run Memorable Tech Conferences by Leah Silber (Dave)
Plush Hello Kitty Doll (Dave)

Check out and get your tickets for React Remote Conf! May 11th-13th, 2016.

02:30 - Justin Meyer Introduction

• Twitter
• GitHub
• Bitovi
• JavaScriptMVC

03:02 - DoneJS and CanJS

• @DoneJS  
• @CanJS

05:44 - Versus Meteor

07:41 - Versus React

• Set Algebra

12:06 - Getting Started with DoneJS

• donejs.com/place-my-order.html

18:04 - Can <=> Done

• MVVM (Model–View–Viewmodel)
• Observables
  • Pagination
  • Preventing Loop Issues

25:39 - MVC => MVVM

28:24 - Flux vs MVVM

32:20 - Use Cases

39:19 - App Size

• StealJS

Picks

Beautiful Eyes Album by Taylor Swift (AJ)
When Amazon Dies (AJ)
PROTODOME (AJ)
City Libraries (AJ)
The Crucible of Doubt: Reflections On the Quest for Faith (AJ)
Learn X in Y Minutes (Aimee)
Which cat is your JavaScript framework? (Aimee)
@johnpapa Tweet (Joe)
SumoMe (Chuck)
Drip (Chuck)
7 Wonders (Chuck)
Shadow Hunters (Chuck)
Calamity (The Reckoners) by Brandon Sanderson (Chuck)
Staked (The Iron Druid Chronicles) by Kevin Hearne (Chuck)
BB-8™ by Sphero (Justin)
Hyperion Cantos Series (Justin)
UtahJS (Justin)

React Remote Conf and Angular Remote Conf

03:15 - Justin Searls Introduction

• Twitter
• GitHub
• Blog
• Test Double
• JavaScript Jabber Episode #038: Jasmine with Justin Searls

04:13 - Testing

• testdouble.js
• teenytest
• Sinon.JS

08:44 - Mocking

• Growing Object-Oriented Software, Guided by Tests by Steve Freeman and Nat Pryce
• Jim Weirich

14:45 - Starting These Concepts as a Junior Developer

• Test-driven Development

17:55 - testdouble.js vs. sinon.js

• NIH = Not Invented Here

26:39 - Duck Typing, Monkey Patching, Duck Punching

32:22 - Node.js Negativity

• Design, Resources
  • Martin Fowler’s Refactoring and Patterns Books
  • Domain-Driven Design: Tackling Complexity in the Heart of Software by Eric Evans

42:52 - Community

45:08 - The AAA Rule: Arrange, Act, Assert

51:19 - Error Messages

Picks

• Unemployment (Jamison)
• React Rally (Jamison)
• Julia Evans' Tweet: how to be a wizard programmer  (Jamison)
• See the good in people (Aimee)
• Sinon.JS (Joe)
• How to Stay Motivated: Developing the Qualities of Success by Zig Ziglar (Chuck)
• The Harry Potter Series (Chuck)
• RetroPie (Justin)
• How Elm can Make you a Better JavaScript Programer (Justin)
• NEJS Conf (Justin)

On this week's episode of My JS Story, Charles Max Wood interviews Justin Searls. Justin was on the show on episode 38 and 226 in the show. He co-founded Test Double, a software agency which helps developers improve the quality of the software they write. Want to know how he got into this career path? Stay tuned!

My JS Story Justin Meyers

On this week’s episode of My JS Story, Charles Max Wood interviews Justin Meyers Co­founder and CEO of Bitovi, a Javascript consulting firm focused on simplifying Javascript development through the use and creation of open source tools as well general consulting, training, and web applications. He was on Episode 202 and talked about DoneJS and CanJS. Tune in to hear Justin’s full story!

7th Grade and a TI­82 [3:02]
Justin’s discovery of conditional statements and methods on a classic TI­82 was his first taste of programming. With a little guidance, he soon learned to program games on the TI­82 and then later moved onto bigger and better mediums like C and QBasic.

Grunt work is good for you. [4:51]
While studying Computer Science, Justin finds out that professors often have grunt work, and although they may not pay well now, sometimes they can in time lead to loads of experience and maybe even a bigger job. After 4 years of working on websites and writing documentation, he gets his first real job at Accenture.

Open Source and reducing waste. [6:23]
Accenture, while giving him a great chance to make some impressive projects, provoked Justin to see the efficiency in sharing code. Justin and a college friend get together to work on a project to build a platform that…builds. Although their project was unsuccessful, the tools they started to create for the project had plenty of potential.

The Last desperate gasp. AKA shaving his head. [9:40]
Justin talks about the Ajaxian blog and conference. Ten years ago, the Ajaxian blog was one of the best online resources for Javascript news. Justin was running low on funds and struggling and as his “last desperate gasp” he heads to the Ajaxian conference with his head shaved. Leaving only “Javascript MVC” shaped out of his hair. This stunt gets him remembered by many of the important attendees and also scores him his big break with a consulting job with T­-Mobile. Two to Three weeks later, Justin had a stroke. Justin talks about how incredible the timing was.

How Javascript MVC came to be. [13:23]
Justin talks about starting with JSJunction and modeling after it. Their first steps were to add a model layer as well as Event Delegation. Javascript MVC reflects some of Ruby on Rails. Justin worked with Peter Svensson from Dojo, with a methodology that at the time seemed crazy. Justin reminisces when Steve Jobs “Killed” Flash with HTML5 and CSS.

Bitovi begins. [17:24]
Justin talks about how the T­-Mobile job meant that he would need an official business. Originally dubbing it JupiterIT. Justin found that MVC was too encompassing and that programmers enjoyed a sense of creativity. By pulling Javascript MVC’s tools apart and creating single frameworks from the tools, Justin then created tools like CanJS and DoneJS.

Who does the heavy lifting at Bitovi? [20:48]
As the CEO of Bitovi, Justin has less time to program as before. Working with Open Source, development is a mix between contributors and full time employees. The majority being the employees. Justin talks about not having a sales force and focusing on their product to drive sales. Mainly, long term cost of ownership and the ability for the framework to last, working hard to make sure that clients that have committed to Javascript MVC years ago still have a relevant use for the framework.

Exploring HTTP2 and Push. [23:42]
With the emergence of HTTP2 and Push, Justin talks about working on and exploring different ways for streaming/server side rendering. Justin describes one of the experiments with building an empty skeletons, javascript assets, but also pushing instructions on how to mutate the page to the client. Before the javascript payload is fully loaded, the page starts to mutate. Allowing for optimal performance on slower connections, fantastic for mobile. Problems they are looking at for the future include things like different ways that CDNs can work with HTTP2 and Push. Justin has also worked with using Fetch to enable streaming by building tools around that. He suggests that HTTP2 and Push will maybe bring a renaissance in the developer world.

Justin’s side Parsing Project. [28:45]
Additional to his other work, Justin is working on a generic parsing project. Similar to BISON or JISON. Designed for simple parsing at faster speeds. He describes how to compiles to the code that parses your code. Working in runtime.

A way other companies can learn from Bitovi. [29:52]
We don’t know what the future is going to be for code, so packaging the framework into separate repos allows for better scheduling and a better way to manage long term. Updating a segment of a framework can sometimes break another segment if having it all happen together.

Picks [34:26]

Justin:

Dean Radcliff’s Antares Framework

Charles:

Boom Beach

Clash of Clans

BlueTick.io

Nimble

Keeping up with Justin’s work.

Bitovi.com’s Blog

Justin’s Twitter.

Sponsors

Cachefly.com
Newbie Remote Conf 2017

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

Panel:

• Aimee Knight
• Charles Max Wood (DevChat TV)
• Christopher Ferdinandi (Boston)
• Joe Eames

Special Guests: Justin Meyer

In this episode, the panel talks with Justin Meyer who is a co-author of DoneJS, CanJS, jQueryPP, StealJS, and DocumentJS. Justin currently works for Bitovi and is their Director of R&D. He is also a fan of basketball and Michael Jackson. The panel and Justin talk about CanJS in-detail – check it out!

Show Topics:

0:58 – We had you on Episode 202.

1:14 – Chuck: Can you tell everyone who you are?

1:20 – Justin tells us his background.

1:50 – Chuck.

1:58 – Justin.

2:06 – Chuck: Can you give us an introduction to what CanJS 4.0?

2:11 – Justin: It is a JavaScript framework and is similar to Vue. It adds a very model layer, and uses Real Time very well.

2:44 – Panelist.

2:49 – Justin.

2:55 – Panelist: What is the current...

3:09 – Justin: Compatibility is very important to us. A lot of the same tools are still available. It has over 80 different repositories.

Justin continues to talk about the differences/similarities between the different versions.

4:55 – Panelist: Angular, React, and Vue are dominating, so I have 2 questions.

1.) Where is the core strength of JS and its user base?

2.) What is like to be the CanJS when everyone is talking about the other programs?

5:31 – Justin: We have dealt with this for the past 10 years. Emotionally it’s not great, I wished it was more popular, but our priority is keeping our user-based happy. We’ve had big companies use it.

Justin answers the second question.

8:44 – Panelist: You mentioned two things.

9:22 – Aimee: I think everything has trade-offs. I would use something because it was the right tool for the job. I wouldn’t want to make something that was “cool.” I would want to make it super accessible in a network.

10:10 – Justin: That is a great marketing angle. We are trying to remove the worst parts of the program.

10:26 – Now I am intrigued.

10:32 – Justin: You have this mutable state and you aren’t sure. At least for CanJS I don’t see that occurring too often.

10:54 – Aimee.

10:58 – Justin: Deep inheritance is definitely a problem and it can create...

11:13 – Aimee.

11:19 – Justin: We have changed strategies a lot, and I think it’s helped CanJS grow; like 60% since January. We are doing a lot of user studies now. I run Meetups, etc. That being said inheritance schemes aren’t something that people will encounter. This is something that they won’t encounter months down the road.

13:00 – Aimee.

13:05 – Panelist: I would like to dig deeper into state-management. Everyone is doing Flux, talk about that with CanJS.

13:20 – Justin: Yeah. It depends on what kind of user you are talking to. When I talk to new users off the street (people who just graduated, etc.)...

If you look at React’s statistics – more than 50% doesn’t use any state management.

16:15 – Panelist: I think it’s interesting that there are people that aren’t “oh my gosh...”

16:43 – Justin: The last coolest thing I’ve done is...

18:02 – Justin continues.

18:16 – Panelist: I kind of have this belief that we as a community turn to frameworks and tools too much. From your perspective when does it make sense to turn to a tool like this or better off working with native...

18:56 – It depends on how complex your app is and our ability to work through those problems. I think that’s a generic answer, but hopefully that helps. I don’t think you really can’t live without.

19:49 – Panelist: I think that’s fair. One thing that I found is that there are many things layered into state-management. Because you mentioned performance, which is something I care about, too. At what point does the extra tooling become too heavy for the user’s experience? Where do you draw the line?

21:11 – Justin: It depends. I don’t know what the parallel is – it’s like a richer developer problem. You have too many users where you can make those fine tuned adjustments. Do whatever is going to deliver the product first and then worry about performance later? I think our things are geared towards performance by default.

22:41 – Panelist: Playing devil’s advocate, though. But isn’t there some danger in kind of suggesting that you focus on performance WHEN it’s a business issue? Maybe there is there a lack of empathy among developers. I worry that advice is hurting us.

23:53 – Justin: No matter what you can build your homepage with Angular weird monstrosity, but then when you get to the point when people are using your product – you can just use native HTML, and native methods and build that one widget and as easy and fast as possible.

24:50 – Panelist: Dealing with complexity. Now we need to do things like bundlers, and such to deal with this issue. I feel like a crotchety old man yelling because it takes forever.

25:38 – Justin: I think it depends on where you are sitting. I think that comes down to the design. If your design has a lot of complex states, then...

26:37 – Panelist: Because you care about performance...

26:54 – Advertisement

27:53 – Justin: I don’t think that the run time of CanJS is going to be a critical performance path for anybody. Is there a responsibility? This is the oldest question. It’s like saying: where do you draw the line that you need to choose success/be elected to fight the battles if you really want to win.

You need someone using your product or it doesn’t really matter. Start-ups use our product because they need to get something up and in. I am going to flip this back onto you guys.

30:48 – Panelist: I think that’s fair.

31:00 – Aimee: I have a question. You got into consultancy when do you recommend using CanJS or something else?

31:15 – Justin: I always suggest people using CanJS.

31:53 – Aimee: What do these people do when their contract is over? I have used an older version of Can, and...

32:20 – Justin: Are you on Gitter?

Aimee: No, I am not.

32:25 – Justin: We do offer promote job posting to help them find somebody. We try our best to help people in any way we can.

33:05 – Aimee: That’s helpful. Another question.

33:28 – Justin: DoneJS is that. It uses the full kitchen sink. That’s what DoneJS is.

33:50 – Panelist: Let’s talk about CanJS in the mark-up. Do you think it’s better now or worse than 2012? Less space or more space?

34:13 – Justin: It’s probably worse. I think the methodology that we are using: focusing on our users. We get their feedback frequently. We are listening to our users, and I think we are being smarter.

35:16 – Panelist: Is the space getting more welcoming or less?

35:31 – It depends on what framework you are. It’s very hard to compete if you are the exact same thing as...

The market is so dense and there are so many ideas, so it’s getting harder and harder. What helps people break-through? Is it the technology or the framework?

36:36 – Panelist: I appreciate the richness of the field, as it exists right now. There aren’t a few things SMELT and ELM

37:10 – Justin: Elm for sure. I don’t have a lot of experience with SMELT.

37:23 – Panelist continues the talk.

37:54 – Chuck.

38:00 – Justin: I think it spreads by word-of-mouth. I used to think it was “technology” or... all that really matters is “can you deliver” and the person have a good experience.

Usability is the most important to me. We will see how this turns out. I will be either right or wrong.

39:18 – Panelist: Can we talk about the long-term future of Can JS?

39:28 – Justin: We are connecting to our user-base and making them happy. If I had it my way (which I don’t anymore) I think JSX is the best template language. We have been building integrations between JSX and...

I am putting out proposals where most people don’t like them.

Justin continues this conversation.

44:24 – Picks!

44:28 - Advertisement

Links:

• JavaScript
• jQuery
• React
• Elixir
• Elm
• Vue
• Polyfill.io
• Dinero.js
• Vanilla JS Toolkit
• CanJS’ Website
• CanJS’ GitHub
• CanJS’ Twitter
• JSX
• JSX- NPM
• Justin Meyer’s GitHub
• Justin Meyer’s Twitter
• Past Episode with Justin Meyer

Sponsors:

• Kendo UI
• Sentry
• Cache Fly
• Get a Coder Job

Picks:

Aimee

• Taking a walk for creativity
• https://ohshitgit.com

Chris

• PolyFill.io
• Dinero.js
• https://vanillajstoolkit.com/

Joe

• Pitch Meeting
• Solo

Charles

• Phoenix Framework
• The Queens Poisoner
• A View From The Top

Justin

• The Killing of H2Push
• Browser Contributor Days
• JSJ Episode 326 with Tom Dale

Sponsors

• Sentry use the code “devchat” for $100 credit
• Triplebyte
• Clubhouse
• CacheFly

Panel

• Charles Max Wood

Joined by special guest: Aaron Gustafson

Episode Summary 

This episode of JavaScript Jabber comes to you live from Microsoft Ignite. Charles Max Wood talks to Aaron Gustafson who has been a Web Developer for more than 20 years and is also the Editor in Chief at “A List Apart”. Aaron gives a brief background on his work in the web community, explains to listeners how web standardization has evolved over time, where Progressive Web Apps (PWAs) come from, where and how can they be installed, differences between them and regular websites and their advantages. They then delve into more technical details about service workers, factors affecting the boot up time of JavaScript apps, best practices and features that are available with PWAs. 

Aaron mentions some resources people can use to learn about PWAs, talks about how every website can benefit from being a PWA, new features being introduced and the PWA vs Electron comparison. In the end, they also talk about life in general, that understanding what people have gone through and empathizing with them is important, as well as not making judgements based on people’s background, gender, race, health issues and so on.

Links

• Creating & Enhancing Netscape Web Pages
• A List Apart
• A Progressive Roadmap for your Progressive Web App
• Windows Dev Center - Progressive Web Apps
• MDN web docs
• PWA Stats
• PWA Stats Twitter
• Aaron’s website
• Aaron’s Twitter
• https://www.facebook.com/javascriptjabber/
• https://twitter.com/JSJabber

Picks

Aaron Gustafson:

• Homegoing
• Zeitoun

Charles Max Wood:

• Armada 

JavaScript Remote Conf 2020

May 14th to 15th - register now!

Mani Vaya joins Charles Max Wood to talk about how developers can add the enterepreneur hat to the others they wear by starting a side gig. They discuss various ideas around entrepreneurship, the books they got them from, and how they've applied them in their own businesses.

Panel

• Charles Max Wood

Guest

• Mani Vaya

Sponsors

• Taiko

__________________________________________________

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

__________________________________________________

Picks

Mani Vaya:

• Good to Great
• The Lean Startup

Charles Max Wood:

• Expert Secrets
• The Masked Singer

Follow JavaScript Jabber on Twitter > @JSJabbber

Konicek-Moran, Richard

Horn, Michiel, 1939-

Little, Kimberly K

Crommelin, Claude August, 1840-1874

Boland, Mary L

Cousineau, Robert Henri

Austin, James H., 1925-

Austin, James H., 1925-

Going by a letter written by Nawaz Sharif to Narendra Modi, that he was 'much satisfied' with their meeting in New Delhi, the two prime ministers have succeeded in striking up a working relationship.

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

Kondo, Manabu, author