Mud walls of building may have been weakened by the recent downpour in the city, officials said.

Protesters said Shoma had failed to take corrective measures and demanded her immediate arrest.

'TBM is not suitable for tunnel excavation in HP and has been found to be a complete failure'.

Berlin ; New York : Springer, [2005]

Berlin ; New York : Springer, [2007]

Berlin ; New York : Springer, [2005]

Berlin ; New York : Springer, 2006

Berlin ; New York : Springer, [2006]

Holbrook, Neil John, compiler

Roseberry, Kimberly, author

UK's health organisation, NHSX, in a blog over the weekend said that it has prioritised security and privacy in all stages of the app's development, starting with the initial design, and user testing

Both companies said privacy and preventing governments from using the system to compile data on citizens was a primary goal

Plant Operators Forum (2004 : Denver, Colo.)

International Workshop on Process Hydrometallurgy (2nd : 2008 : Santiago, Chile)

‘Steps are being taken to send them home’

It also seeks details of paid quarantine facilities and death rate

Joe Eames and Charles Max Wood talk about the advantages and challenges of working from home.

The panelists talk about refactoring JavaScript Apps Into a Framework with Brandon Hays.

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

The panelists discuss the Ionic Framework with Max Lynch and Tyler Renelle.

The panelists talk about MV Frameworks with Craig McKeachie.

The panelists discuss remote work with Mike Hostetler.

The panelists talk about the Mozilla Developer Network with Les Orchard and David Walsh.

02:35 - John-Daniel Trask Introduction and Background

• Twitter
• GitHub
• Blog
• Mindscape
  • @MindscapeHQ

04:57 - Raygun.io

• @raygunio

06:23 - Crash Reporting The Right Way

• Error Grouping
• Suppress Notifications

10:06 - Most Common Errors

12:05 - Source Maps

19:16 - Managing Error Reporting in Gross Environments

22:17 - Determining Where The Issue Is

24:45 - Do People Write Their Own Errors?

26:23 - Frameworks Support

28:28 - Collecting Data: Privacy and Security

30:01 - Does working in error reporting make you judgemental of others’ code?

• “DDOSing Yourself”

32:42 - Planning for Rare Exceptions

33:36 - Tactics to Cut Down on Messages

35:53 - Gathering Basic Debugging Information

37:58 - Getting the BEST Information

• Promises
• Stockholm Syndrome

42:24 - The Backend: Node.js

• The raygun4node provider

43:24 - “Creating an Application”

Picks

LDS Connect (AJ)
LDS I/O (AJ)
TED Talk About Nothing (Dave)
OlliOlli 2 Soundtrack (Jamison)
Jurassic Park (Joe)
 ng-vegas (Joe)
WASD CODE 87-Key Illuminated Mechanical Keyboard with White LED Backlighting - Cherry MX Clear (Chuck)
Grifiti Fat Wrist Pad (Chuck)
Thank You Rails Clips Kickstarter Backers! (Chuck)
Mastery by Robert Greene (Chuck)
Ready Player One by Ernest Cline (Chuck)
The Pirates of Silicon Valley (John-Daniel)
littleBits (John-Daniel)

Panel: 

Charles Max Wood

Aimee Knight

AJ O'Neal

Special Guests: Kitson Kelly

In this episode, the JavaScript Jabber panelists talk with Kitson Kelly about evaluating web frameworks. Kitson is currently in Australia working for ThoughtWorks as a principle technologist. He has written many articles on frameworks and urges that people don’t get stuck on one framework in their programming. He talks about how using only frameworks that you know could hurt you in the long run. This episode is great for understanding when to use certain JavaScript frameworks and how branching out from what is comfortable might make your job easier.

In particular, we dive pretty deep on:

• Articles on web frameworks
• How do you pick a JavaScript framework to use?
• The framework depends on your changing needs
• Recommending less popular frameworks
• Angular, Ember, React
• React vs Redux
• Certain domains with different frameworks?
• Each framework takes a different approach
• How to decide which framework to use?
• Only give it a couple days to see if your app works with the framework
• Is it ever appropriate to not use a certain framework?
• Frameworks are there to make your job easier
• Don’t be afraid to try new frameworks
• Choose a framework that will “be there tomorrow”
• What is the future for frameworks?
• Experiment and be honest with what you need
• And much, much more!

Links:

• Linode
• ThoughtWorks
• Kendo UI
• LootCrate
• @KitsonK
• Kitson’s GitHub

Picks:

Charles

• Facebook
• The 12 Week Year by Brian P. Moore
• Google Drive for Business

Aimee

• Would College Students Retain More If Professors Dialed Back The Pace?
• URL to PDF Converter
• CSS History

AJ

• Tylenol Cold and Flu Severe

Kitson

• Microsoft Azure
• Zype

Panel:

• Charles Max Wood
• Cory House
• Aimee Knight
• Joe Eames
• AJ O'Neal

In this episode, the JavaScript Jabber panelists talk about the Framework Summit. It was the brainchild of Merrick Christensen. This summit includes talks on multiple different frameworks all in a two-day conference, which allows you to get exposed to new frameworks while still learning more about the framework your job requires you to use. Another goal of the conference is that it will be able to open people’s eyes up to the different frameworks available to them and show that no one framework is superior to another.

In particular, we dive pretty deep on:

• What is the Framework Summit?
• The framework you use plays a huge role in your programming
• For people who want to learn about more than one framework
• Allows you to explore
• The format of the conference
• Park City, Utah in October 2018
• Helps you answer which framework should you use?
• Goal is to open people’s eyes up to other frameworks
• Decrease internet arguments over which framework is better
• Fluent Conference
• Get to have conversation with other people who work in your framework
• Making connections
• React Rally Talk Evan Czaplicki
• The context matters
• Being able to deep dive into the different frameworks
• Using frameworks in conjunction with one another
• Have you seen “religionist” themes in programming frameworks?
• Why Good People Are Divided by Politics and Religion by Jonathan Haidt
• Some people will never look beyond their frameworks
• If it’s working, why would you mess with it?
• And much, much more!

Links:

• React Dev Summit
• JS Dev Summit
• Framework Summit
• Angular
• React
• Ember
• JavaScript
• Fluent Conference
• React Rally Talk Evan Czaplicki
• Why Good People Are Divided by Politics and Religion by Jonathan Haidt
• @FrameworkSummit

Picks:

Charles

• Parked Out By the Lake Dustin Christensen
• DevChat.tv
• Newspaper by Themeforest

Cory

• Quokka

Aimee

• Republic of Tea – Apple Cider Vinegar Tea
• The Way of Testivus

Joe

• Evan Czaplicki Talk

AJ

• Dinosaurs
• Cough Syrup by Young the Giant

Panel:

• Charles Max Wood
• Alyssa Nicholl
• Ward Bell

Special Guests: David Cramer

In this episode, the JavaScript Jabber panelists talk to David Cramer about error tracking and troubleshooting workflows. David is the founder and CEO of Sentry, and is a software engineer by trade. He started this project about a decade ago and it was created because he had customers telling him that things were broken and it was hard to help them fix it. They talk about what Sentry is, errors, workflow management, and more!

In particular, we dive pretty deep on:

• David intro
• Founder and CEO of Sentry
• What is Sentry?
• Working with PHP
• De-bugger for production
• Focus on workflow
• Goal of Sentry
• Triaging the problem
• Workflow management
• Sentry started off as an open-source side project
• Instrumentation for JavaScript
• Ember, Angular, and npm
• Got their start in Python
• Logs
• Totally open-source
• Most compatible with run-time
• Can work with any language
• Deep contexts
• Determining the root cause
• And much, much more!

Links:

• Sentry
• JavaScript
• Ember
• Angular
• npm
• Python
• Sentry’s GitHub
• @getsentry
• David’s GitHub
• David’s Website
• @zeeg

Sponsors

• Kendo UI
• FreshBooks
• Loot Crate

Picks:

Charles

• Socks as Swag

David

• VS Code
• Kubernetes

Sponsors

• Sentry use code “devchat” for 2 months free

• Triplebyte $1000 signing bonus

• Linode

Panel

• Charles Max Wood

• Aimee Knight

• Chris Ferdinandi

• AJ O’Neal

• Joe Eames

Episode Summary

Today the panel discusses the necessity of a front end framework. Overall, there is a consensus that frameworks are not necessary in all situations. They discuss the downsides of using frameworks, such as being restricted by the framework when doing edge development and the time required for learning a framework. They talk about the value of frameworks for learning patterns in programming.

The panel delves into the pros and cons of different frameworks available. Joe shares a story about teaching someone first without a framework and then introducing them to frameworks, and the way it helped with their learning. One of the pros of frameworks is that they are better documented than manual coding. They all agree that it is not enough to just know a framework, you must continue to learn JavaScript as well.

They talk about the necessity for new programmers to learn a framework to get a job, and the consensus is that a knowledge of vanilla JavaScript and a general knowledge of the framework for the job is important. New programmers are advised to not be crippled by the fear of not knowing enough and to have an attitude of continual learning. In the technology industry, it is easy to get overwhelmed by all the developments and feel that one cannot possibly learn it all. Charles gives advice on how to find your place in the development world. The show concludes with the panel agreeing that frameworks are overall a good thing and are valuable tools.

Links

• JWT

• Angular

• Vue

• Backbone

• GoLang

• Express

• React

• Redux

• Hyper HTML

• 4each

• Pascal

• JQuery

• Npm.js

Follow DevChat on Facebook and Twitter

Picks

Charles Max Wood:

• Podwrench

Aimee Knight:

• How to Love Your Job and Avoid Burnout

• So Good They Can’t Ignore You

Chris Ferdinandi:

• Vanilla JS toolkit

• Thinkster

• Artifact Conference

AJ O’Neal:

• Binary Cocoa

• Binary Cocoa Slamorama Kickstarter

• Binary Cocoa Straight 4

• Root

Episode Summary

Surma is an open web advocate for Google currently working with WebAssembly team. He was invited on the show today to talk about using web workers and how to move work away from the browser’s main thread. His primary platform is bringing multithreading out of the fringes and into the web. 

The panel talks about their past experience with web workers, and many of them found them isolated and difficult to use. Surma believes that web workers should pretty much always be sued because the main thread is an inherently bad place to run your code because it has to do so much. Surma details the differences between web workers, service workers, and worklets and explains what the compositer is. 

The panel discusses what parts should be moved off the main thread and how to move the logic over. Surma notes that the additional cost of using a worker is basically nonexistent, changes almost nothing in your workflow, and takes up only one kilobyte of memory. Therefore, the cost/benefit ratio of using web workers gets very large. They discuss debugging in a web worker and Surma details how debugging is better in web workers. 

Surma wants to see people use workers not because it will make it faster, but because it will make your app more resilient across all devices. Every piece of JavaScript you run could be the straw that breaks the camel’s back. There’s so much to do on the main thread for the browser, especially when it has a weaker processor, that the more stuff you can move away, the better.

The web is tailored for the most powerful phones, but a large portion of the population does not have the most powerful phone available, and moving things over to a web worker will benefit the average phone. Surma talks about his experience using the Nokia 2, on which simple apps run very slow because they are not being frugal with the user’s resources. Moving things to another thread will help phones like this run faster.  

The panel discusses the benefit of using web workers from a business standpoint. The argument is similar to that for accessibility. Though a user may not need that accessibility all the time, they could become in need of it. Making the app run better on low end devices will also increase the target audience, which is helpful is user acquisition is your principle metric for success. 

Surma wants businesses to understand that while this is beneficial for people in countries like India, there is also a very wide spectrum of phone performance in America. He wants to help all of these people and wants companies acknowledge this spectrum and to look at the benefits of using web workers to improve performance.

Panelists

• Charles Max Wood

• Christopher Buecheler

• Aimee Knight

• AJ O’Neal

With special guest: Surma

Sponsors

• Adventures in DevOps

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

• Adventures in Angular

Links

• Web workers

• Service workers

• Worklets 

• Ecto model

• Babel

• Swoosh

• Comlink

• WhatsApp

Follow DevChatTV on Facebook and Twitter

Picks

Charles Max Wood:

• For Love of Mother-Not

Surma:

• Follow Surma @DasSurma on Twitter and at dassur.ma

• WebAssembly Spec

AJ O’Neal:

• The GameCube Ultimate

• Pikmin for Wii and GameCube

• Super Monkey Ball

Christopher Buecheler

• CinemaSins Sincast podcast

O'Meara, Lauren J

Watkins, S. Craig (Samuel Craig)

Mandel, Debra

Busse, Richard C

International Labour Conference (93rd : 2005 : Geneva, Switzerland)

Callaars, Josephus

Badger, Michael

Badger, Michael

Stommel, Henry M., 1920-1992

Castro, Peter, author

Murray-Darling Basin Authority (Australia)