Panel Joe Eames (twitter github blog) Tim Caswell (twitter github howtonode.org) Charles Max Wood (twitter github Teach Me To Code Rails Ramp Up) AJ O’Neal (twitter github blog) Discussion 00:56 - Why JavaScript is hard to learn 02:30 - This 05:30 - Bind 09:11 - Browsers 11:01 - Class-based inheritance Prototypal inheritance 16:37 - New function 18:51 - Closures 20:51 - JavaScript is asynchronous 22:14 - Variable scoping Hoisting 26:14 - Numbers and math (AJ joins the podcast) == ’s vs === ’s 32:15 - Things that make JavaScript hard after learning JavaScript Package management 35:06 - Numbers (cont’d) Crypto Bitwise operations Strings Effective JavaScript by David Herman 044 JSJ Book Club: Effective JavaScript with David Herman 40:16 - Changing/Evolving JavaScript 43:31 - Environmental reasons that make JavaScript Hard Tooling 48:25 - Few projects are primarily JavaScript 49:07 - Adolescence and the JavaScript Ecosystem 53:59 - Running JavaScript Picks Sharpie Metallic Silver (AJ) The how and why of auto-executing functions (in JavaScript) (AJ) The JavaScript Unicycle (AJ) RSA (Tim) OUYA (Tim) Borderlands 2 (Joe) MechWarrior Tactics (Chuck) Testing Clientside JavaScript (Joe) Fire Up Ember.js | PeepCode (Chuck) Meet Chef (Part 2 of 2) | PeepCode (Chuck) Next Week MooTools with Arian Stolwijk and Valerio Proietti Transcript TIM:  I’m just learning lots of math and attempting to do real math in JavaScript is a fun challenge. [Hosting and bandwidth provided by the Blue Box Group. Check them out at  Bluebox.net.] [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.] CHUCK:  Hey everybody and welcome to Episode 48 of the JavaScript Jabber show. This week on our panel, we have Joe Eames. JOE:  Howdy! CHUCK:  We also have Tim Caswell. TIM:  Hello! CHUCK:  And I’m Charles Max Wood from DevChat.tv. And when this episode goes out, you’re going to have about two weeks left if you wanted to sign up for my Rails Ramp Up course. You’ll find that at RailsRampUp.com. I’ve been working hard on that. This week, we’re going to talk about why JavaScript is hard. And I think it was Tim that came on and said, “So, we’re talking about why JavaScript sucks?” And I didn’t want to call it that but at the same time, it’s one of the -- I think the reasons that people find JavaScript hard and the reasons some people say that JavaScript sucks are kind of the same thing. So, if you want to think of it that way, go right ahead. But I kind of wanted to talk about this for a couple of reasons. One was that I was at the users’ group meeting last week and they talked about some of the things that make JavaScript hard and I don’t remember what they all were. But there were a few things that, there are some concepts that are markedly different from what you find in other languages or at least some of the concepts exist in the other languages but they aren’t kind of as important or as in-your-face as they are in JavaScript. Anyway, the other reason is that I was thinking about when I first started this show. And when I first started the show, I was a web developer that was kind of like, “jQuery, whoo!” And thought jQuery and JavaScript, you know, were mostly the same in the sense that the only way to write sane JavaScript was to use jQuery. And so, I wanted to talk around some of the things that I’ve learned over the last year from the other panelists and help people who are coming into JavaScript understand the real power behind some of these other concepts. So that being said, let’s go ahead and get started. I’m a little curious as to what you guys think are some of the hard things that people run into in JavaScript, like why do they struggle with it? TIM:  Alright. So,

02:54 - Everyone Gets It But Me

• Martin Fowler

04:06 - Tools You “Need” to Know

06:29 - Clojures

07:39 - JavaScript as “Object-Oriented” vs “Event-Oriented”

• Object-Oriented Programming

09:30 - Code That Can’t Be Serialized or Deserialized

10:49 - Clojures (Cont’d)

14:32 - The DOM (Document Object Model)

• [YouTube] Angular + React = Speed by Dave Smith @ ng-conf 2015

19:52 - Math Is Hard

• IEEE754 (Floating-Point Arithmetic)

22:39 - Prototypes

• Sebastian Porto: A Plain English Guide to JavaScript Prototypes

25:43 - Asynchronous Programming

• Debugging
• Gregor Hohpe: Your Coffee Shop Doesn’t Use Two-Phase Commit
• How Do You Learn It?

32:23 - Browser Environments

34:48 - Keeping Up with JavaScript

35:46 - Node

• Nesting
• Context Switching

42:48 - UTF-8 Conversion

44:56 - Jamison’s Stack

• React
• Koa    
• RethinkDB
• io.js
• Webpack

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!

Picks

Jason Orendorff: ES6 In Depth (Aimee)
Cat Strollers (Aimee)
Stephano Legacy of the Void (Joe)
A Gentleman's Guide to Love and Murder (Joe)
Gregor Hohpe: Your Coffee Shop Doesn’t Use Two-Phase Commit  (AJ)
Firefox OS (AJ)
Flame (AJ)
OpenWest 2015 (AJ)
801 Labs Hackerspace (AJ)
Stack Overflow Careers (AJ)
Dota 2 (Jamison)
Beats, Rye & Types Podcast (Jamison)
JS Remote Conf Talks (Chuck)
Workflowy (Chuck)

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

In this episode of JavaScript Jabber, Charles talks about the new direction he has for the company. He wants  to drive people to the point that they have the skills that make people want to hire and work with them, to teach them how to ‘Max out’. Today the panel the skills that developers need to progress in their careers: social skills. 

The panel talks about their observations from work that the people who advanced and grow in their career were the ones with social skills, not necessarily with technical skills. The company wants to get stuff done, and if your social skills are getting in the way of projects getting done because you can’t work with others, you are not that useful to the company, and you will be stuck in the lower ranks while others who may not have the same technical skills will rise in the ranks because they are pleasant to work with. Mani talks about his personal experience getting laid off for lacking these soft skills. But then he read the book 48 Laws of Power by Robert Green, realized his shortcomings, and started to apply just one lesson from the book. Within 6 months, he was promoted.

Mani delves deeper into the first lesson taught in 48 Laws of Power, Never Outshine the Master. Fundamentally, this means that you don’t try to prove in meetings how good you are, or that they’re wrong, or that you think that you are better than them. The more you the aforementioned things, the less likely you will be to get promoted or trusted. Mani talks about how he used to do these things and how it cost him multiple jobs. When he put this lesson into practice, he changed his methods and the boss started to like him, leading to his promotion 6 months later. The panel discusses this lesson and what benefits can come from it. 

Mani shares another lesson that he learned through the story of a friend trying to get him to invest in his business. After Mani refused to invest multiple times, his friend stopped asking him to invest, but instead asked him for business advice. Eventually, Mani invested in the business because when he saw that his friend was influenced by his advice, it engendered trust between them. The panel agrees that if you want to influence someone, you have to be influenced by them. It is important to treat someone as a person rather than an asset or wallet, and ensure them that their investment is not their end goal. One of the most fundamental social skills that you must be able to like people, because other people can smell manipulation. 

The panel transitions to talking about the paradoxical nature of social skills and that they are often the opposite of what you think will work in a situation. Unfortunately, there will always be difficult people to work with. To illustrate how to work with difficult people, Mani shares the story of how Gengis Khan was convinced not to destroy a city of artists and engineers by his advisor, Yelu Chucai. Gengis Khan agreed because Yelu Chucai was able to structure his plea in a way that would also benefit Gengis Khan. 

The conversation shifts to how to conduct an interview to see if a candidate will fit into your team culture. First, you must know what you’re looking for and understand your team culture, and then ask for stories of when they accomplished something in the interview. If every story is all about how they did something and they don’t include other people, then that may indicate their self-centeredness. They discuss the Ben Franklin Effect. 

For those listeners wondering where to begin with all this self improvement, Mani has read over 2,000 books on business and offers a course on his website, 2000books.com. Mani has teamed up with JavaScript Jabber to offer a special deal to the listeners of this podcast. To get lifetime access to Mani’s courses at a 40% discount, follow the links below. 

Panelists

• Steve Edwards

• Charles Max Wood

With special guest: Mani Vaya

Sponsors

• React Native Radio

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

• React Round Up

Links

• 48 Laws of Power by Robert Green

• The 360 Degree Leader by John C. Maxwell

• The Ben Franklin Effect

• javascriptjabber.com/social and 2000books.com 

  • 40% off for the first 200 people

  • Coupon code: Jabber

Follow DevChatTV on Facebook and Twitter

Picks

Steve Edwards:

• Rex Chapman

Charles Max Wood:

• BombBomb

• IndieHackers.com 

• Stolen bike prank

Mani Vaya: 

• How I Built This by NPR

• As a Man Thinketh

Blumenthal, Noah, 1972-

Allhoff, Fritz

While the intent may be laudable, there are several problems with the approach

Edmonds, Mike, author

Norris, Pippa, author

Saldanha, Tony, author

Interview with Thomas Niederkrotenthaler, MD, PhD, MMSc, author of Association of Increased Youth Suicides in the United States With the Release of 13 Reasons Why

The complex mineral collection beneath northern New Jersey may offer clues to how Earth formed and how soil affects water purity and plant growth

Innovation, fast-paced change, and products that go down the drain give the sector its enduring appeal

They persist in the pharma business, even as chemical companies in the West have mostly exited

Variables in fabrics, fit, and user behavior can influence how well a mask might block the virus's spread

Variables in fabrics, fit, and user behavior can influence how well a mask might block the virus's spread

Two studies pinpoint nasal cells and others that express the molecules the virus uses to get inside

These are the recordings of the complete collection of all the talks by Ajahn Chah that have been translated into English and are published in 'The Collected Teachings of Ajahn Chah', 2011. This was read by Ajahn Amaro during the winter of 2012

The post Part 1 – Ch12 – Why Are We Here appeared first on Amaravati Buddhist Monastery.

Online Resource

Rotch Library - HT167.U7125 2018

Rotch Library - HT321.P64 2020

A `Bad Bank' is being touted as the panacea for industry’s ills, yet again.

Online Resource

A political scientist argues that Dalit social movements undermine the community’s electoral mobilisation

'For a working actor in Bollywood, it is nearly impossible to criticise its reigning deities.' 'Besides, due care ought to be taken when speaking of the dead too.'

'No Indian citizen should be humiliated by the US authorities.''And Shah Rukh Khan happens to be one of India's most well known citizens.'

'Aamir Khan, Shah Rukh Khan and Salman Khan now act in only about one film each year, and made money through advertisements and television.' 'This meant that many people, even if they had the money to spend on a movie and wanted to go, often had nothing available for them to watch.'

The beauty Mirzya is that it has no story. There is only poetry. Through the film one can feel the pulse of Gulzar's brilliant poetry coursing through it, says Syed Firdaus Ashraf.

Neither the filmmaker nor the actor who is being targeted, says Syed Firdaus Ashraf, has done anything illegal.

Syed Firdaus Ashraf, who grew up in the 1980s, tells us why Befikre is a must watch to understand the new generation.

'The film industry will remain soft targets and continue to be picked upon with no respite, with no choice but to give in due to personal safety and financial compulsions,' says director Suparn Verma.

Why you don't admire SRK in Raees

Although famously reclusive and fitful in his creative output, Daniel Day-Lewis's decision to hang up his boots feels both untimely and unexpected.

In March 1972, The Godfather was first screened in a New York theatre. The movies were never the same again. Forty six years later, longtime Rediff film critic Raja Sen talks about why that film means that much, and how it led him to a unique tribute.

Both Raazi and Veere Di Wedding are interesting films that worked. There is no point reading a trend in them, says Vanita Kohli-Khandekar.

Dibakar Banerjee delivers his finest work to date, and Sreehari Nair makes sure to applaud him.

'It is nice to know I am remembered even now,' Lataji tells Subhash K Jha.

No, no, it has nothing to do with Salman...

Why do the biggest, most talented and successful film-makers of India suck up to the establishment so breathlessly, asks Shekhar Gupta.

'Nawaz, who plays my husband, doesn't look at women when he has sex with them.''He never kisses them.''That moment when I am in front of him is decisive,' the New Wave actress tells Subhash K Jha.

It won't be easy for the half-British diva to step into the Desi Girl's sandals, feels Subhash K Jha.

'Mulk questions the very principle, of good-Muslim exceptionalism.''That, of course, we adore Abdul Hamid, A P J Abdul Kalam and Bismillah Khan and if only more Muslims were like them.''Anubhav Sinha sticks his neck out to say that these are no exceptions.''Most Muslims are like them. It is the terrorists who are exceptions,' says Shekhar Gupta.

'It started as a kind of joke. Now I think it has gone far enough.'

Favourite movie homes, comparing Amitabh-Shashi's beds in Kabhi Kabhie and discovering the truth about Salman Khan's 1990s chartbuster...All in Sukanya Verma's Super Filmi Week.

Politics, favouritism and poor taste in cinema have contributed to embarrassing choices for the Oscar race in the past.This little gem from India needs the love, emotional and financial support from the government as well as the Indian film industry, argues Aseem Chhabra.

'Deeply flawed, Sacred Games and Mirzapur come nowhere close to representing the diversity of stories from this country,' says Vikram Johri.

While Pa Ranjith proved yet again to be the salt of the earth in his land mafia film, Zoya Akhtar took a haphazard route to make something that was hardly rooted in Asia's biggest slum, feels J Jagannath.