Online Resource

Dewey Library - QH84.5.C67 2019

Dewey Library - QH51.G55 2019

Online Resource

Dewey Library - HV6692.T39 L48 2019

Dewey Library - UA668.I49 2019

Online Resource

Online Resource

Dewey Library - JK524.T36 2018

Dewey Library - JC311.N221234 2019

Dewey Library - JK305.S54 2018

Dewey Library - JC575.H378 2018

Genesis of Muzaffarnagar riots is not just that of two communities turned against each other.

The killer disease of children are undercut by a wily virus and administrative bottlenecks.

About 25,000 people from over 114 affected villages have been shifted to safer places.

Army's action came after reports of Pak troops occupying an uninhabited village emerged.

Analysis of this infiltration bid indicated the involvement of Pak Border Action Team.

Five Indian soldiers have been injured in the gunbattle that started on September 24.

No village has been occupied by militants. We will get them out soon, Bikram Singh said.

Army operation against the holed up militants in Keran Sector entered the 13th day today.

8 terrorists killed, 59 weapons including 18 AK rifles and war-like stores captured.

This is the second such incident in the last 5 days after jawans beat up officers in Meerut in UP.

Rahul Gandhi further said that he wanted the youth of the country to run the political system in future.

Officials said several bombs and rocket shells didn't explode as they had sunk into the earth.

BSF is at present deployed on the frontiers with Pakistan and Bangladesh.

Specs had gone missing three years ago and the matter was handed over to the state CID (Crime).

Army officials said that they would not like to move out from the glacier as it holds strategic importance.

Controversy and its fallout were, Devyani said, more a personal than a professional loss for her.

Montrie, Chad, author

Pretty, Jules N., author

EPD Congress (2012 : Orlando, Fla.)

Chappell, Marianne Diane, author

The panelists discuss Backbone.js with Jeremy Ashkenas.

The panelists talk to Jeremy Ashkenas about CoffeeScript.

Get your JS Remote Conf tickets!

Freelance’ Remote Conf’s schedule is shaping up! Head over here to check it out!

02:17 - Jessica Lord Introduction

• Twitter
• GitHub
• Blog

02:40 - Amy Palamountain Introduction

• Twitter
• GitHub
• Blog

03:14 - Electron

• Atom

04:55 - Cross-platform Compatibility

05:55 - Electron/Atom + GitHub

07:16 - Electron/Atom + React ?

07:57 - Use Cases for Electron

• muan/mojibar
• mafintosh/playback
• npm-scripts-gui
• Amy Palamountain: Building native applications with Electron @ Nordic.js 2015

15:09 - Creating Electron Apps on Phones

17:25 - Running a Service Inside of Electron  

• Visual Studio Code
• Adventures in Angular Episode #44: Visual Studio Code with Erich Gamma and Chris Dias

19:46 - Making an Electron App

• Photon
• conors/photon
• Photon Components
• N1

24:09 - Sharing Code

27:40 - Plugins for Functionality

• electron-accelerator
• electron-packager
• electron-prebuilt

31:08 - Keeping Up-to-date/Adding Features

33:14 - Pain Points

• NuGet

36:22 - Using Electron for Native

• JavaScript Jabber Episode #186: JSJ NativeScript with TJ VanToll and Burke Holland
• PhoneGap
• Reactive Native
• NativeScript

39:48 - What is a “webview”?

42:12 - Getting Started with Electron

43:28 - Robotics/Hardware Hacking with Electron

• JIBO

Picks

Autolux - Future Perfect (Jamison)
Move Fast and Break Nothing (Aimee)
[egghead.io] Getting Started with Redux (Dave)
Destructuring and parameter handling in ECMAScript 6 (Dave)
JS Remote Conf (Chuck)
Freelance Remote Conf (Chuck)
React Remote Conf (Chuck)
Pebble Time Steel (Chuck)
UglyBaby Etsy Shop (Amy)
Jimmy Fallon: Kid Theater with Tom Hanks (Jessica)

This episode was recorded live from The Microsoft Build Conference 2016. In this episode we chatted with Jeremy Thake of Microsoft about MS Office. You can follow him on Twitter, see what he’s done over on GitHub, or visit his blog.

Resources:

Office Dev Center

Picks

Billions (Jeremy)

JSJ 265 Wade Anderson and Ramya Rao on Visual Studio Code

This episode is live at the Microsoft Build 2017 with Charles Max Wood and AJ O’Neal. We have Wade Anderson and Ramya Rao from the Visual Studio Code Team at Microsoft. Tune in and learn more about what’s new with Visual Studio Code!

[00:01:20] – Introduction to Ramya Rao and Wade Anderson

Ramya Rao and Wade Anderson are in the Visual Studio Code Team at Microsoft.

Questions for Wade and Ramya

[00:02:00] – Elevator Pitch for Visual Studio Code

Our vision on Visual Studio Code is to take what was best out of the IDE world (Visual Studio, Eclipse, IntelliJ, etc.) and bring what was best from the lightweight editor world (Sublime Text, Notepad++, Atom) and merge those two together. We wanted the lightweight features from text editors and the debugging capabilities of Visual Studio and Eclipse. We did general availability last year. We’ve been stable for a year. Additionally, this is Visual Studio Code for Mac, Windows, or Linux. It’s also built in Electron.

[00:03:45] – What are your roles on the team? Do you have particular parts that each of you work on?

Wade’s title is a Program Manager. He does more non-developer things but Ramya is an engineer on the team so she gets a lot more coding that Wade does. Everybody has a key area to own but nothing stops them to go into another area. We try to share knowledge between people but we always have that one key owner that you always go to.

Ramya is a recent addition to the team. She started out maintaining the Go extension, maintaining and adding features. She’s slowly branching out to the Emmet features of the product.

[00:05:30] What is Emmet?

Emmet, or Zen Coding, is a must-have tool for you. You can write, say abbreviations and that expands to really huge HTML to update tags, rename tags, etc. That is one of the features of Emmet and Sergey actually wrote the library. We have an in built integration in the product. I [Ramya] am currently working on that.

[00:06:28] Does Visual Studio Code make it easy to go to the parts that I need to customize on an HTML?

In that case, we have a multi-cursor software in Visual Studio Code, as well. You could place your cursor in different positions, and then, simultaneously edit things.

[00:07:42] Is Emmet an extension or does it come with Visual Studio Code?

Right now, it’s in Built. If you want to know more about Emmet features, you can to emmet.io. That has all the documentation that you need to learn about Emmet features. In Visual Studio Code right now, we’re looking at making into an extension. We pull it out of the main code and maybe more people can contribute and make it even more better.

[00:08:21] – What’s new in Visual Studio Code?

One of our main pillars for this year is to improve performance of the product. We’ve grown a larger team so we’re adding a lot more features every month. Last few months has been, “How can we get some stability on the issues coming in while making sure we’re reducing our tech load?” We really keep to those core principles that we started with at the beginning, which was, we want a fast, lightweight editor.

We built a few extensions that we call key map extensions. They are just a mapping of key bindings that you learned in Sublime Text. You don’t have to re-learn any key bindings in Visual Studio Code.

We also build this Welcome page where you can flip through and see features really briefly. In that Welcome page, one of the key things is an interactive playground where you can play with existing code in different sections. Additionally, as we’ve mentioned, we also put multi-cursor features.

Another thing is workbench naming. You can change the theme of Visual Studio Code but it will be restricted to the editor and not the rest of the workbench.

[00:13:40] – Do you know how Xterm.js works as it was one of the features that you’ve added in Visual Studio Code?

Daniel’s another engineer that’s here with us today. He was the largest contributor to the Xterm.js project. He built the integrated terminal for Visual Studio code so I can’t speak to the internals of how that works.

[00:14:12] – Are we going to start seeing Visual Studio Code integrated into web experiences with other Microsoft products?

That’s actually where we started. We were Monaco editor where you get this cloud-based editing experience. We’re getting people to use it but we’re only getting people who were already using Microsoft products.  When electron came out, we saw an opportunity of, “Hey, can we port this  Monaco editor to Electron and we could then, run it on Mac and Linux.”

[00:19:45] – What are the performance things that you’ve done?

One thing that we did recently was adding an ability to calculate the start time for Visual Studio Code? That’s one of our full steps to get more information from the user-side. How can you get a profile of what things are running? Which part of the process took much time?

We also need to identify what are the things people are doing that’s causing the editor slow down. An example is when you open a large file and things get laggy.

Another exercise we did was we looked at all of our extension API’s to see which one of those could be a malicious extension.

The difference between VS Code and Atom is that, we ask questions like, “Are we using good data structures? Are we managing our memory properly? Are we removing stuff we don’t need anymore?” That just comes down to all those little things you learn from basic textbooks that have been around for decades about how to write good code. That’s what we have been doing and that’s what we’ll continue to try to do, to try and improve the performance.

[00:25:55] – Do you have problem on the desktop? Are all the modules just load at once?

We definitely don’t load everything at once. Different parts of the editor is loaded differently. When you do the Require, we don’t do it at first load. We do it when we notice that the user wants to use Emmet. We don’t try to load all the library at the beginning and delay the whole process.

We try to lazy load as much as possible, even the extensions. We have a separate process called extension host that takes care of loading all the extensions. Whether the extensions are completed loading or not, that does not stop you from typing in a file. Simple actions shouldn’t be bugged down by fancy actions.

[00:28:25] – What’s coming next for Visual Studio Code?

Every month, when we plan our iteration, we create iteration draft plan. We put it out there for people to see. Performance and helping people get started are probably the top two for us. You can look at github.com/Microsoft/vscode, look for the label ‘iteration plan draft.’ So that’s the current work that we’re doing that month.

Another feature is the multi-root workspace where you can open multiple folders. When you look at the issues and sort by most comments, multi-root is the number one. The second one that is little paper cuts around formatting and auto-intending – just things that make your code prettier.

Picks

AJ O’neal

• Breath on the Wild
• Microsoft’s Intelligent Edge

Charles Max Wood

• Boom Beach
• Bluetick.io
• Emacs key binding extension for Visual Studio Code

Wade Anderson

• Kindle Paperwhite
•  Twitter @waderyan_

Ramya Rao

• Open source
• Twitter @ramyanexus

Tweet this episode

JSJ BONUS: Web Apps on Linux with Jeremy Likness and Michael Crump

In this episode Aimee Knight and Charles Max Wood discuss Microsoft's Web Apps on Linux offering with Jeremy Likness and Michael Crump.

[00:37] Michael Crump Introduction

Michael is on the developer experience team for Azure.

[00:52] Jeremy Likness Introduction

Jeremy is on the cloud developer advocacy team. Their mission is to remove friction and support developers and work with teams to build a positive experience.

The NodeJS team is headed up by John Papa. They have teams around the world and involved in many open source communities.

They're focused on building documentation and creating great experiences

[02:54] What is it about Azure that people should be getting excited about?

Azure is a huge platform. It can be overwhelming. They're trying to help you start with your problem and then see the solution as it exists on Azure.

Azure is growing to embrace the needs of developers as they solve these problems.

The experience is intended to be open and easy to use for any developer in any language on any platform. It allows you to work in whatever environment you want.

Standing up applications in production is tough. Azure provides services and facilities (and interfaces) that make it easy to manage infrastructure.

You don't have to be an operations expert.

Chuck mentions this messaging as he heard it at Microsoft Connect() last year.

It's not about bringing you to .NET. It's about making it easy where you're at.

Aimee adds that as a new-ish person in the community and Azure excites her because the portal and tutorials are easy to follow for many new programmers.

A lot of these features are available across command lines, tools, and much more.

The documentation is great. See our interview with Dan Fernandez on the Microsoft Docs.

[12:04] Web Apps on Linux

Web application as a service offering from Microsoft. I don't need to worry about the platform, just what's different about my application.

Web Apps has traditionally been on Windows. Web Apps on Linux is in preview.

You can choose the size of your infrastructure. You only get billed for what you use and can scale up.

Setting up multiple servers, managing synchronization and load balancing is a pain. Web Apps gives you a clean interface that makes this management easy.

You can also scale across multiple datacenters around the world.

[15:06] Why Linux? What's hard about Windows?

Node was originally created on Linux and many tools run nicely on Linux. It was later ported to Windows.

The toolchains and IDE's and build processes is in an ecosystem that is targeted more toward Linux than Windows.

This allows people to work in an environment that operates how they expect instead of trying to map to an underlying Windows kernel.

Aimee gives the example of trying to set up ImageMagick on Windows.

Web Apps on Linux also allows you to build integrations with your tools that let you build, test, and deploy your application automatically.

[19:12] Supported Runtimes

Web Apps on Linux supports Node, PHP, Ruby, and .NET Core.

You can run a docker container with Node up to 6.x. If you want Node 7.x and 8.x you can create your own Docker container.

Web Apps on Linux is build on Docker.

The containers also have SSH, so developers can log into the docker container and troubleshoot problems on the container.

If you can build a container, you can also run it on this service.

At certain levels, there's automatic scaling.

[22:06] Consistency between containers? Shared ownership of state or assets

It depends on how you build your app. The Docker containers have a shared storage where all the containers have access to the same data and state.

There's a system called kudu that makes this really simple.

You can also pull logs across all systems.

You can also use SSH in the browser

[25:23] What's painful about Linux and containers?

How is the application built and how does it manage state so that you can isolate issues.

If you have 20 containers, can you connect to the right one.

It's up to you to manage correlation between containers so you can find the information you need.

Knowing your traffic and understanding what to do to prepare for it with scaling and automation is sometimes more art than science.

[28:28] How should you manage state?

A lot of these systems lend themselves to running stateless, but you don't want to run mongodb on each container versus running one mongodb instance that everything attaches. You want a common place to store data for the entire app for shared state.

[30:34] CosmosDB (was DocumentDB)

It's an API equivalent to MongoDB. It's a database as a service and you can connect your containers to the CosmosDB in Azure using your portal to make it super easy.

You may need to open up some firewall rules, but it should be pretty straightforward.

[34:14] Third Party Logging Management Apps

Azure has a service that provides metrics (Application Insights) and a logging service. Many other companies use elasticsearch based solutions that solve some of these problems as well.

[36:06] How do people use Web Apps on Linux?

Companies building new applications many times want to run without managing any infrastructure. So, they use Azure Functions, and other services on Azure.

Lift and shift: Take a virtual machine and change it into a web app container that they can run in the cloud. They also move from SQL Server on a server to SQL Server on the cloud. Moving from hosted MongoDB to CosmosDB.

You can also use any images on DockerHub.

[40:06] Continuous Integration and Continuous Deployment

Whether you're using a private registry or cloud registry. When you publish a new image, it'll use a webhook to pull the custom image and deploy it. Or to run it through Continuous Integration and then deploy it without any human interaction.

Chuck mentions the case when you haven't logged into a server for a while, there's a huge backlog of system updates. Updating your container definitions makes upkeep automatic.

[42:02] Process files and workers with PM2 format

You can set up instances to run across cores with the PM2 definitions. You can also make it run various types of workers on different containers.

Why did you use PM2? What other uses are there for this kind of setup?

You can tell it which processes to start up on boot. You can also have it restart processes when a file is changed, for example, with a config file you can have it restart the processes that run off that config file.

[45:38] How to get started

Getting started with Node

docs.microsoft.com

Trial account with a few hundred dollars in Azure credit.

Michael's Links

• michaelcrump.net
• @mbcrump
• github.com/mbcrump

Jeremy's Links

• bit.ly/coderblog
• @jeremylikness
• github/jeremylikness

Picks

Aimee

• Having a little bit of mindfulness while waiting on code and tests to run.

Joe

• Ozark on Netflix
• Star Wars: Rogue One

Chuck

• Travelers on Netflix

Jeremy

• Ozark filming in Woodstock, GA
• Autonomous Smart Desk
• LED light strips

Michael

• Conference Call Bingo
• Life (Movie)
• Get Out (Movie)

Panel: Charles Max Wood

Guest: Jeremy Likness

This week on My JavaScript Story, Charles speaks with Jeremy Likness. Jeremy works for Microsoft currently and first got into programming when he was kept home while having a sunburn and taught himself how to type in a program into his family’s TI-99 4A computer and then later moved on to the Commodore 64. They stress the fact that you can be a successful programmer, no matter your background and they talk about the pros and cons of being a cloud developer advocate.

In particular, we dive pretty deep on:

• How did you first get into programming?
• How much Microsoft is in the different programming aspects
• Cloud developer advocates
• Azure
• TI-99 4A and Commodore 64
• C and C+
• You don’t have to go the traditional route to be a programmer
• Having a CS major is not the only way
• How did you get into JavaScript?
• Discovered the internet in college
• Career focused on Web apps
• jQuery
• Backbone.js
• Hands-on career with the code
• He did consulting for 10 years
• Linux
• How has your earning changed?
• His biggest fear was getting out of touch with the realities of day-to-day programming
• Pros and cons of being a cloud developer advocate
• Community, Content, and Connection with engineering
• And much, much more!

Links:

• Microsoft Cloud developer advocates
• Azure
• JavaScript
• jQuery
• Backbone.js
• Linux
• @JeremyLikness
• Jeremy’s Blog

Picks

Charles

• BusyCal

Jeremy

• Dwitter.net
• Hello World: The Film
• Node.js documentation on Azure

Panel:

• Aimee Knight
• Joe Eames
• AJ ONeal

Special Guests: Jeremy Fairbank

In this episode, the JavaScript Jabber panel talks to Jeremy Fairbank about his talk Practical Functional Programming. Jeremy is a remote software developer and consultant for Test Double. They talk about what Test Double is and what they do there and the 6 things he touched on in his talk, such as hard to follow code, function composition, and mutable vs immutable data. They also touch on the theory of unit testing, if functional programming is the solution, and more!

In particular, we dive pretty deep on:

• Jeremy intro
• Works for Test Double
• What he means by “remote”
• What is Test Double?
• They believe software is broken and they are there to fix it
• His talk - Practical Functional Programming
• The 6 things he talked about in his talk
• Practical aspects that any software engineer is going to deal with
• Purity and the side effects of programming in general
• Hard to follow code
• Imperative VS declarative code
• Code breaking unexpectedly
• Mutable data VS immutable data
• The idea of too much code
• Combining multiple functions together to make more complex functions
• Function composition
• Elm, Elixir, and F#
• Pipe operator
• Scary to refactor code
• Static types
• The idea of null
• The theory of unit testing
• Is functional programming the solution?
• His approach from the talk
• And much, much more!

Links:

• Test Double
• His talk - Practical Functional Programming
• Elm
• Elixir
• F#
• @elpapapollo
• jeremyfairbank.com
• Jeremy’s GitHub
• Jeremy’s YouTube

Sponsors

• Kendo UI
• Sentry
• Digital Ocean

Picks:

Aimee

• American Dollar
• Force with lease

AJ

• Superfight

Joe

• The 2018 Web Developer Roadmap by Brandon Morelli
• Svelte

Jeremy

• Programming Elm
• The Secrets of Consulting by Gerald M. Weinberg
• Connect.Tech

Sponsors

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

Episode Summary  

In this episode of JavaScript Jabber, the panelists talk with Tommy Hodgins who specializes in responsive web design. He starts with explaining to listeners what it means by a responsive web layout and goes on to discuss the techniques in using JavaScript in CSS in depth.

He elaborates on dynamic styling of components, event-driven stylesheet templating, performance and timing characteristics of these techniques and describes different kinds of observers – interception, resize and mutation, and their support for various browsers. He also talks about how to go about enabling certain features by extending CSS, comparison to tools such as the CSS preprocessor and Media Queries, pros and cons of having this approach while citing relevant examples, exciting new features coming up in CSS, ways of testing the methods, caffeinated stylesheets, along with Qaffeine and Deqaf tools.

Links

• JS in CSS – Event driven virtual stylesheet manager
• Qaffiene
• Deqaf
• Tommy’s Twitter
• Fizzbuzz

Picks

Joe

• The Captain Is Dead

Aimee

• Developer on Call
• Tip – Try to follow a low-sugar diet

Chris

• Tommy’s snippets on Twitter – JS in CSS
• All things frontend blog
• Gulp project

Charles

• Coaching by Charles in exchange of writing Show Notes or Tags

Tommy

• JS in CSS

Sponsors

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

Host: Charles Max Wood

Joined By Special Guest: Jeremy Fairbank

Episode Summary

Jeremy is a Software Developer at Test Double and the author of Programming Elm book. Even though Jeremy majored in Chemistry in college, he was always interested in programming since middle school. After he graduated from college he went to work as a web developer at Plastic Industries and relied on blog posts and other online resources to teach himself how to code. Gradually as the company’s needs changed, Jeremy transitioned into an application developer. He taught himself JavaScript using the book Professional JavaScript for Web Developers . He then attented a Coursera classto learn on principles of functional programming and gained experience with many front end frameworks and libraries, including Elm, React, Redux, Backbone.js, and Marionette.js. Jeremy is based out of Hawaii and when he isn't coding, he spends his time playing his guitar and hiking and going to the beach with his family.

Links

• JSJ 325: Practical functional programming in JavaScript and languages like Elm with Jeremy Fairbank
• Jeremy’s GitHub
• Jeremy's LinkedIn
• Jeremy’s Blog
• Professional JavaScript for Web Developers by Nicholas C. Zakas
• Professional JavaScript for Web Developers by Matt Frisbie
• https://knockoutjs.com/
• https://marionettejs.com/
• https://www.coursera.org/
• https://www.coursera.org/learn/programming-languages
• elm-lang.org
• https://www.facebook.com/javascriptjabber
• https://twitter.com/JSJabber
• https://www.facebook.com/DevChattv

Picks

Jeremy Fairbank:

• Programming Elm
• The Umbrella Academy
• Beyond Burger

Charles Max Wood:

• Orphan Black
• https://devchat.tv/
• https://www.netlify.com/
• https://www.11ty.io/
• https://github.com/cmaxw/devchat-eleventy
• JavaScript Jabber - Devchat.tv

Tommy Hodgins is a developer that typically works on A/B tests figuring out how to get websites the outcomes they want. He got into JavaScript and front-end technologies and then read a paper that led him to realize the capabilities of writing software to solve problems. He maintains a front-end focus with his A/B testing work and CSS in JS and other work.

Host: Charles Max Wood

Joined By Special Guest: Tommy Hodgins

Sponsors

• Sentry

• CacheFly

______________________________________

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

______________________________________

Picks

Tommy Hodgins:

• QuickJS

• Language Learning with Netflix

Charles Max Wood:

• Gmelius

• The Man In the High Castle

• The Name of the Wind

• Verdict with Ted Cruz

Konicek-Moran, Richard