Dewey Library - HV6432.J445 2018

Earlier BJP party workers were charged Rs 5 for attending Modi's Bhopal rally.

Shinde emphasised that the govt is committed to its core principle of combating terrorism.

The ruling JD(U), however, is not impressed with such "cheap theatrics".

The clash between the President's visit and Modi's rally had become an issue between BJP and JD(U).

Bihar BJP minority cell Prez Khalid Rahman said that they offered prayer for the success of Modi's rally.

VHP's 'Sankalp Diwas' rally in Ayodhya has been banned by the state government.

This will be Modi's maiden political rally in rival Bihar Chief Minister Nitish Kumar's home turf.

The opposition party accused the state government of adopting a "casual and callous" attitude.

NSG commandos and jawans of Gujarat police would be present at the rally venue.

Organisers of the rally have also been asked to extend the area of the dais to seven metres.

Mars Orbiter is travelling at a distance of about 2.9 million km away from Earth.

Bowman, William D., author

Paulin, Sally, author

Oppenheimer, Michael, author

The company also announced the Swift Student Challenge, an opportunity for student developers to showcase their coding skills by creating their own Swift playground

Plant Operators Forum (2004 : Denver, Colo.)

Kelly, Errol G

The panelists discuss whether HTML5 and JavaScript can really replace Flash.

Javascript Jabber is hosted this week by Joe Eames, Aimee Knight, AJ O'Neal, Cory House, Charles Max Wood and their special guest Bowden Kelly. Bowden is a program manager at Microsoft and he shares some insight into the new features in Visual Studio 2017 RTM with Bowden Kelly.

JSJ 277: Dojo 2 with Dylan Schiemann and Kitson Kelly

This episode of JavaScript Jabber features panelists Aimee Knight, Cory House, and Charles Max Wood. They talk with Dylan Schiemann and Kitson Kelly about Dojo 2.

[00:02:03] Introduction to Dylan Schiemann

Dylan is the CEO at Sitepen and co-founder of the Dojo Toolkit.

[00:02:22] Introduction to Kitson 

Kitson is the CTO at Sitepen and project lead for Dojo 2.

[00:02:43] Elevator Pitch for Dojo

Dojo 1 has been around forever. Started back in 2004 as a way to solve the challenge of "I want to build something cool in a browser." Promises and web components were inspired by or created by Dojo. It's been a huge influence on the web development community.

Dojo 2 is a ground up re-write with ES 2015, TypeScript and modern API's. It's a modernized framework for Enterprise applications.

[00:04:29] How is Dojo different from other frameworks?

There's a spectrum: small libraries like React with an ecosystem and community of things you add to it to Angular which is closer to the MV* framework with bi-directional data binding. Vue lands somewhere in the middle. Dojo 2 is also somewhere in the middle as well. It's written in TypeScript and has embraced the TypeScript experience.

[00:06:00] Did the Angular 2 move influence the Dojo 2 development and vice-versa?

Dojo 2 had moved to TypeScript and 2 days later Angular announced that they were going to TypeScript. Angular also moved very quickly through their BETA phase, which caused some challenges for the Angular community.

With Dojo 2, they didn't start the public discussion and BETA until they knew much better what was and wasn't going to change. They've also been talking about Dojo 2 for 6 or 7 years.

The update was held up by adoption of ES6 and other technologies.

Dojo 1 was also responsible for a lot of the low-level underpinning that Angular didn't have to innovate on. Dojo 2 was built around a mature understanding of how web applications are built now.

People doing Enterprise need a little more help and assistance from their framework. Dojo provides a much more feature rich set of capabilities.

Angular could have pushed much more of TypeScript's power through to the developer experience. Dojo much more fully adopts it.

It's also easier if all of your packages have the same version number.

Call out to Angular 4 vs Angular 2.

[00:12:44] AMD Modules

Why use AMD instead of ES6 modules?

You can use both. Dojo 2 was involved in the creation of UMD. James Burke created UMD while working on Dojo.

ES6 modules and module loading systems weren't entirely baked when Dojo 2 started to reach maturity, so they went with UMD. It's only been a few months since Safari implemented the ES6 module system. Firefox and friends are still playing catchup.

The Dojo CLI build tool uses webpack, so it's mostly invisible at this point.

So, at this point, should I be using UMD modules? or ES6? Is there an advantage to using AMD?

With TypeScript you'd use ES6 modules, but UMD modules can be loaded on the fly.

[00:16:00] Are you using Grunt?

Internally, for tasks we use Grunt. But for users, we have a CLI tool that wraps around Webpack.

For package builds and CI, Grunt is used.

[00:18:30] What is the focus on Enterprise all about?

There are a lot of different challenges and complexities to building Enterprise apps. Dojo was the first framework with internationalization, large data grids, SVG charts, etc. Dojo has spend a long time getting this right. Many other systems don't handle all the edge cases.

Internationalization in Angular 2 or 4 seems unfinished.

Most Dojo users are building for enterprises like banks and using the features that handle large amounts of data and handle those use cases better.

[00:21:05] If most application frameworks have the features you listed, is there a set of problems it excels at?

The Dojo team had a hard look at whether there was a need for their framework since many frameworks allow you to build great applications. Do we want to invest into something like this?

React has internationalization libraries. But you'll spend a lot of time deciding which library to use and how well it'll integrate with everything else. A tradeoff in decision fatigue.

In the Enterprise, development isn't sexy. It's necessary and wants to use boring but reliable technology. They like to throw bodies at a problem and that requires reliable frameworks with easily understood decision points.

Producing code right is a strong case for TypeScript and they pull that through to the end user.

Many frameworks start solving a small set of problems, become popular, and then bolt on what they need to solve everything else...

Dojo tried to make sure it had the entire package in a clear, easy to use way.

You can build great apps with most of the big frameworks out there. Dojo has been doing this for long enough that they know where to optimize for maintainability and performance.

[00:29:00] Where is Dojo's sweet spot? 

The Sitepen Blog series on picking a framework

The biggest reason for using Dojo over the years is the data grid component.

They also claim to have the best TypeScript web development experience.

You may also want a component based system with the composition hassles of React.

The composability of components where one team may write components that another uses is a big thing in Dojo where one person doesn't know the entire app you're working on.

Theming systems is another selling point for Dojo.

[00:34:10] Ending the framework wars

Try Dojo out and try out the grid component and then export it to your Angular or React app.

There are a lot of frameworks out there that do a great job for the people who use them. The focus is on how to build applications better, rather than beating out the competition.

Sitepen has build apps with Dojo 2, Angular, React, Dojo + Redux, etc.

[00:39:01] The Virtual DOM used by Dojo

2 years ago or so they were looking for a Virtual DOM library that was small and written in TypeScript. They settled on Maquette.

The more you deal with the DOM directly, the more complex your components and libraries become.

Makes things simpler for cases like server side rendering getting fleshed out in BETA 3.

It also allows you to move toward something like React Native and WebVR components that aren't coupled to the DOM.

They moved away from RxJS because they only wanted observables and shimmed in (or polyfilled) the ES-Next implementation instead of getting the rest of the RxJS  that they're not using.

[00:46:40] What's coming next?

They're finishing Dojo 2. They're polishing the system for build UI components and architecture and structuring the app. They plan to release before the end of the year.

They're also wrapping up development on the Data Grid, which only renders what shows on the screen plus a little instead of millions of rows.

[00:49:08] Testing

They've got intern.

It pulls together unit testing, functional testing, continuous integration hooks, accessibility testing, etc.

It's rewritten in TypeScript to take advantage of modern JavaScript.

The Dojo CLI uses intern as the default test framework.

Kitson build the test-extras library to help with Dojo testing with intern.

Dojo Links

• dojo.io
• github.com/dojo/meta
• sitepen.com/blog
• gitter channel
• github.com/dylans
• twitter.com/dylans
• twitter.com/sitepen
• twitter.com/dojo
• github.com/kitsonk
• twitter.com/kitsonk

Picks

Cory

• Amateur vs Professional

Aimee

• DevFest Florida (use code 'jsjabber')

Chuck

• Taking some time off
• AudioTechnica ATR2100
• How to define your life purpose in 5 minutes

Dylan

• zenhub
• HalfStack Conference
• How to choose a framework series on the Sitepen Blog

Kitson

• Dunbar Number

Panel: 

Charles Max Wood

Guest: Kitson Kelly

This week on My JavaScript Story, Charles speaks with Kitson Kelly. Kitson is a return guest, previously on JavaScript Jabber 277. Kitson is the CTO at SitePen, and has been working and maintaining Dojo 2 for the last couple years.

Kitson talks about his journey as a developer. First, sparking his interest with old Atari games and getting his first computer in his early years.  Kitson talks about his education background and introduction to computers in high school and hang out with other in the same programming niche. Kitson talks about his challenges not having a degree in computer science, but still very successful as a developer after climbing the corporate latter.

In particular, we dive pretty deep on:

• Atari Games and old first computer
• Hangout with the computer nerds
• Community college
• No actual formal computer science degree
• Tech Support and Self Taught
• Challenges with not degree
• Climbing the latter
• Troubles even with a degree
• Is a degree in computer science really needed?
• Experience verses degree
• Working with other people is important
• Getting into JavaScript and Dojo
• What kept you working in JavaScript
• How do you get to being CTO and SitePen?
• What are you most proud of with the work on Dojo
• Contributions
• Side Projects  - Dojo 2
• and much, much more!

Links: 

• https://github.com/kitsonk
• Kistson Kelly
• https://www.sitepen.com
• https://dojo.io

Picks:

Kitson

• SVG 
• Noun Project

Charles

• adminlte.io
• Ruby on Rails, Jquery
• podwrench.com

Panel: 

Charles Max Wood

Joe Eames

Aimee Knight

Special Guests: Russell Goldenberg and Adam Pearce

In this episode, JavaScript Jabber panelist speak with Russell Goldenberg and Adam Pearce Russell creates visualizations, interactive graphics, and documentaries for the web. Currently an editor at The Pudding.  Adam is a graphics editor at The New York Times and a journalist engineers/developer  Russell and Adam are on the show to talk about what Scrollytelling is, as well as Scrollama. Scrollama is a modern and lightweight JavaScript library for scrollytelling using IntersectionObserver in favor of scroll events. This is a great episode to understand another technology/tool created with JavaScript.

In particular, we dive pretty deep on:

• What is Scrollytelling!
• Graph Scroll library
• What is the intersection Observerable?
• How long does it take to build an interactive graphic…?
• How do you test something like this?
• Test on a lot of different devices
• Can you do automated testing?
• Do you have to understand the use cases or can you implement quickly?
• Recommendation for getting started?
• Is this a skill set people have to have before that some on board?
• How do design these interactions?
• Scroll jacking
• What JS developers should know about this technology.
• Position sticky
• What are other uses cases?
• What can devs use it for?
• Tax calculator
• And much more!

Links:

•  
• https://github.com/russellgoldenberg/scrollama
• https://pudding.cool/process/introducing-scrollama/
• @codenberg
• @adamrpearce
• https://pudding.cool/
• http://russellgoldenberg.github.io
• https://github.com/1wheel?direction=desc&sort=created&tab=stars
• https://roadtolarissa.com

Picks:

Adam

• Dominion - Broad Game

Charles

• Smoker
• Tiny Epic Galaxies
• Indiegogo Dev Chat TV

Aimee

• Deadlines
• Quest Protein Powder

Joe

• Giving!
• Board Game - Azul

Russel

• Crokinole
• Bust Out

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
• AJ O’Neal
• Aimee Knight

Special Guests: Valeri Karpov 

In this episode, the panel talks with programmer, Valerie Karpov from Miami, Florida. He is quite knowledgeable with many different programs, but today’s episode they talk specifically about Async/Await and Promise Generators. Val is constantly busy through his different endeavors and recently finished his e-book, “Mastering Async/Await.” Check-out Val’s social media profiles through LinkedIn, GitHub, Twitter, and more.

Show Topics:

1:20 – Val has been on previous episodes back in 2013 & 2016.

1:37 – Val’s background. He is very involved with multiple companies. Go checkout his new book!

2:39 – Promises generators. Understand Promises and how things sync with Promises. Val suggests that listeners have an integrated understanding of issues like error handling.

3:57 – Chuck asks a question.

6:25 – Aimee’s asks a question: “Can you speak to why someone would want to use Async/Await?”

8:53 – AJ makes comments.

10:09 – “What makes an Async/Await not functional?” – Val

10:59 – “What’s wrong with Promises or Async/Await that people don’t like it?” - AJ

11:25 – Val states that he doesn’t think there really is anything wrong with these programs it just depends on what you need it for. He thinks that having both gives the user great power.

12:21 – AJ’s background is with Node and the Python among other programs.

12:55 – Implementing Complex Business Logic.

15:50 – Val discusses his new e-book.

17:08 – Question from Aimee.

17:16 – AJ answers question. Promises should have been primitive when it was designed or somewhat event handling.

17:46 – The panel agrees that anything is better than Call Backs.

18:18 – Aimee makes comments about Async/Await.

20:08 – “What are the core principles of your new e-book?” – Chuck

20:17 – There are 4 chapters and Val discusses, in detail, what’s in each chapter.

22:40 – There could be some confusion from JavaScript for someone where this is their first language. Does Async/Await have any affect on the way you program or does anything make it less or more confusing in the background changes?

24:30 – Val answers the before-mentioned question. Async/Await does not have anyway to help with this (data changes in the background).

25:36 – “My procedural code, I know that things won’t change on me because it is procedural code. Is it hard to adjust to that?” – AJ

26:01 – Val answers the question.

26:32 – Building a webserver with Python. 

27:31 – Aimee asks a question: “Do you think that there are cases in code base, where I would want to use Promises? Not from a user’s perspective, but what our preferences are, but actual performance. Is there a reason why I would want to use both or be consistent across the board?”

28:17 – Val asks for some clarification to Aimee’s question.

29:14 – Aimee: “My own personal preference is consistency. Would I want to use Promises in ‘x’ scenario and/or use Async/Await in another situation?”

32:28 – Val and AJ are discussing and problem solving different situations that these programs

33:05 – “When would you not want to use Async/Await?” – AJ

33:25 – Val goes through the different situations when he would not use Async/Await. 

33:44 – Chuck is curious about other features of Async/Await and asks Val.

36:40 – Facebook’s Regenerator

37:11 – AJ: “Back in the day, people would be really concerned with JavaScript’s performance even with Chrome.” He continues his thoughts on this topic.

38:11 – Val answers the AJ’s question.

39:10 – Duck JS probably won’t include generators.

41:18 – Val: “Have anyone used Engine Script before?” The rest of the panel had never heard of this before.

42:09 – Windows Scripting Host

42:56 – Val used Rhino in the past.

43:40 – Val: “Going back to the web performance question...”

47:08 – “Where do you see using Async/Await the most?” – Chuck

47:55 – Val uses Async/Await for everything on the backend because it has made everything so easy for him.

48:23 – “So this is why you really haven’t used Web Pack?” – AJ

49:20 – Let’s go to Aimee’s Picks!

50:18 – AJ’s story, first, before we get to Promises.

54:44 – Let’s transition to Promises Finally.

54:53 – Val talks about Promises Finally.

59:20 – Picks

Links:

• JavaScript
• Valeri Karpov’s GitHub
• Valeri Karpov’s Twitter
• Valeri Karpov’s LinkedIn
• New E-Book: Mastering Async/Await
• Node
• Python
• Windows Scripting Host
• Facebook’s Regenerator
• Rhino

Sponsors:

• Kendo UI
• Sentry
• Digital Ocean
•  

Picks:

Charles

• YouTube Video “IKEA” by Coulton
• Conference
• Amazon Prime Day

Aimee

• Blog Post Article

AJ

• IKEA
• https://ppl.family

Val

• https://www.npmjs.com/package/serve
• http://bit.ly/ultimate-skiing
• http://asyncawait.net/jsjabber
• New E-Book: Mastering Async/Await

Park, Jane Chi Hyun

Davis, Ronald L

The disappearance of inflammatory communal slogans from political speeches suggests development is the agenda for 2014.

Gershwin, Lisa-Ann, author

Coen, Natasha Jeanne, author

This study uses mendelian randomization to estimate the associations between genetic variants related to reduced HMG-CoA reductase activity and epithelial ovarian cancer in the general population and in BRCA1/2 mutation carriers.

O'Connor, Maeve

Online Resource

Hayden Library - TP548.P793 2018

Online Resource

Beavis, Mary Ann, author