"Because if a government of, by and for the people means anything at all, it means that a ballot has the power to give equal voice to the high and the low; the weak and the strong; those at the bottom as well as the top. It means that in the polling place, the line is just as long for the richest among us as it is for those who often work the hardest but have the least."

On this episode: the Iowa caucuses, tax reform, and meet a scholar who studies global poverty reduction. First, a Brookings expert answers a student’s question about why the Iowa caucuses are so important. This is part of the Policy 2020 Initiative at Brookings. If you have a question for an expert, send a audio file…

I am constantly amazed at the level of political discourse in the US. So a debate about health care degenerates into scares about "death panels" and boycotts of Whole Foods because their CEO is against it. It is all a bit much, and a complete mystery

Although there is no 2020 Wondermark calendar per se, observant Marksman Gary T. let me know that dedicated calendar fans can make a 2020 calendar at home with the aid of: • January–February: The 2014 Wondermark calendar • March–December: Either the 2009 or 2015 Wondermark calendar It’s Leap Day this year that throws things off. SO, […]

Modern jazz instrumental trio from Kolkata The Bodhisattwa Trio is making all the right noises with the release of their new offering, The Grey Alb­um. With the bonus track in th­eir seven-song effort, the ba­nd is mapping the evolution of their own sound over the last seven years. The track, called The Cronos, is a part of all their albums, and marks a change from their up-tempo and rock vibe in their debut album to their jazz sound today, complete with intricate drumming details and synth bass that compel you to keep the beat with your body movements.

A lot of this shift has to do with Arunava Shonai Chatterjee (synth and synth bass) replacing the band’s ba­ssist early last year, which nudged Bo­dhisattwa Ghosh (guitar) and Pr­emjit Dutta (drums) to experiment wi­th their sound. "We always had an inclination towards jazz but started out with progressive rock as we thought we could do justice to that kind of music. Having played as an outfit for so long, and opted for a synth bass, we felt we could go into uncharted territory and could handle difficult sounds and spontaneous creativity," says Ghosh.

Their Mumbai gig will feature all the tracks from their new album, which is divided into two pa­r­ts — chaos to creation, and creation to chaos. The first three songs comprise story-telling between the members and is built on the idea of the duality of an artist’s mind, explains Ghosh, adding that, "There’s an abstraction as artistes don’t think in one particular direction, and this dual nature can be seen in our art as well." Their music is inspired by life events and observations rather than sounds, says Ghosh.

The second half comments on how civilisation is spiralling out of control into chaos, with songs like The Last Train, which talks about the trains in the holocaust in the Second World War and the Indian Partition, and American Dream, which was composed after the members got talking about American capitalism and how we’re on the brink of nuclear war. "We end with Shame, which speaks about the death of a nation, and our chaotic political scenario," informs Ghosh.
They will also be playing songs from their previous album but in a new avatar.

TIME 9 pm onwards
AT The Little Door, off New Link Road, Andheri West 
CALL 9899928776

Catch up on all the latest Crime, National, International and Hatke news here. Also download the new mid-day Android and iOS apps to get latest updates

Singapore is engaging businesses on tweaking the design of its new carbon tax, which is proposed to be in place by 2019.

Nicola Sturgeon warned that Jeremy Corbyn would have to take a 'very firm anti-Brexit position' in order for the parties to work together.

Rep. Alexandria Ocasio-Cortez said she's never spoken to Joe Biden - nor has his campaign reached out to the progressive congresswoman, who was a surrogate for Bernie Sanders.

It is tragic that the new Amendment to the Child Labour (Prohibition & Regulation) (CLPR) Act, 2016, which has a seemingly progressive framework, has been largely diluted by chicanery, opines Kathyayini Chamaraj.

Over the past few years, demands for change have been getting louder in India. But when you have a political system which is not willing to run with this new tide, the cost of this transition is going to be much higher, says Pratap Bhanu Mehta, calling the Congress party a monarchy and the BJP a church.

A new legislation aims to bring in a rigorous process of planning, transparency and citizen participation together at the local level in Karnataka, says Vinay Baindur.

Hayden Library - HQ1438.S63 S685 2019

Dewey Library - HT1523.L285 2019

Australia. Parliament. Senate. Legal and Constitutional Affairs Legislation Committee, author, issuing body

Swarts, Heidi J

Sometimes it is fun to re-visit very basic HTML things and look what we can do with them nowadays. This is what I will do now with a radio button group. I will progressively enhance it to look great and still work with keyboard and screen readers. As part of my Logo-O-Matic upgrade, I added […]

In his The Case for Progressive Web Apps presentation at An Event Apart in Chicago, Jason Grigsby walked through the process of building Progressive Web Apps for your Web experiences and how to go about it. Here's my notes from his talk:

• Progressive Web Apps (PWAs) are getting a lot of attention and positive stories about their impact are coming out. PWA Stats tracks many of these case studies. These sorts of examples are getting noticed by CEOs who demand teams build PWAs today.
• A PWA is a set of technologies designed to make faster, more capable Web sites. They load fast, are available online, are secure, can be accessed from your home screen, have push notifications, and more.
• But how can we define Progressive Web Apps? PWAs are Web sites enhanced by three things: https, service worker, and a manifest file.
• HTTPS is increasingly required for browsers and APIs. Eventually Chrome will highlight sites that are not on https as "insecure".
• Service Workers allow Web sites to declare how network requests and the cache are handled. This ability to cache things allows us to build sites that are much faster. With service workers we can deliver near instant and offline experiences.
• A Web manifest is a JSON file that delivers some attributes about a Web site. Browsers use these files to make decisions on what to do with your site (like add to home page).
• Are PWAs any different than well-built Web sites? Not really, but the term helps get people excited and build toward best practices on the Web.
• PWAs are often trojan horses for performance. They help enforce fast experiences.

Feels Like a Native App

• Does your organization have a Web site? Do you make money off your Web site? If so, you probably need a Progressive Web Site.
• Not every customer will have your native app installed. A better Web experience will help you reach people who don't. For many people this will be their first experience with your company, so you should make it as good as possible.
• Getting people to install and keep using native apps is difficult. App stores can also change their policies and interfaces which could negatively impact your native app.
• The Web can do much more than we think, the Web has APIs to access location, do fast payments using fingerprint identification, push notifications, and more.
• What should we use to design PWAs? Native app styles or Web styles? How much does your design match the platform? You can set up PWAs to use different system fonts for iOS and Android, should you? For now, we should define our own design and be consistent across different OSs.
• What impact does going "chrome-less" have on our PWAs? You loose back buttons, menu controls, system controls. Browsers provide us with a lot of useful features and adding them back is difficult. Especially navigation via the back button is complex. So in most cases, you should avoid going full screen.
• While not every person will add your PWA to their home screen, every person will "install" your PWA via the service worker.
• An app shell model allows you put your common UI (header, footer, nav, etc.) into the app cache. This makes the first loading experience feel a lot faster. Should you app shell or not? If you have architected as a single page app, this is possible but otherwise might not be worth the effort.
• Animating transitions can help with way-finding and polish on the Web. This gives Web sites even more personality.

Installation and Discovery

• Using a Web manifest file, allows you specify a number of declarations for your app. In addition to name, icon, and even theme colors.
• Once you have a PWA built and a manifest file, browsers will being prompting people to install your Web site. Some Browsers have subtle "add" actions. Other use more explicit banner prompts. "Add to home screen" banners are only displayed when they make sense (certain level of use).
• Developers can request these banners to come up when appropriate. You'll want to trigger these where people are mostly likely to install. (like checkout)
• Microsoft is putting (explicitly and implicitly) PWAs within their app store. Search results may also start highlighting PWAs.
• You can use Trusted Web Activity or PhoneGap to wrap native shells around your PWA to put them into Android and iOS app stores.

Offline Mode

• Your Web site would benefit from offline support. Service Workers enable you to cache assets on your device to load PWAs quickly and to decide what should be available offline.
• You can develop offline pages and/or cache pages people viewed before.
• If you do cache pages, make it clear what data hasn't been updated because it is not available offline.
• You can give people control over what gets cached and what doesn't. So they can decide what they want available for offline viewing.
• If you enable offline interactions, be explicit what interactivity is available and what isn't.

Push Notifications

• Push notifications can help you increase engagement. You can send notifications via a Web browser using PWAs.
• Personal push notifications work best but are difficult to do right. Generic notifications won't be as effective.
• Don't immediately ask people for push notification permissions. Find the right time and place to ask people to turn them on. Make sure you give people control, if you'd don't they can kill them using browser controls.
• In the next version of Chrome, Google will make push notification dialogs blocking (can't be dismissed) so people have to decide if they want notifications on or off. This also requires you to ask for permissions at the right time.

Beyond Progressive Web Apps

• Auto-login with credential management APIs allows you to sign into a site using stored credentials. This streamlines the login process.
• Apple Pay on the Web converged with the Web Payment API so there's one way to use stored payment info on the Web.
• These next gen capabilities are not part of PWAs but make sense within PWAs.

How to Implement PWAs

• Building PWAs is a progressive process, it can be a series of incremental updates that all make sense on their own. As a result, you can have an iterative roadmap.
• Benchmark and measure your improvements so you can use that data to get buy-in for further projects.
• Assess your current Web site's technology. If things aren't reasonably fast to begin with, you need to address that first. If your site is not usable on mobile, start there first.
• Begin by building a baseline PWA (manifest, https, etc.) and then add front-end additions and larger initiatives like payment request and credential api later.
• Every step on the path toward a PWAS make sense on their own. You should encrypt your Web sites. You should make your Web site fast. These are all just steps along the way.

Browsery DVD ML394.R663 2015b

STACK SCORE Mu pts B73 piamu h

STACK SCORE MT245.B655 2018

STACK SCORE Mu pts Sch78 piamu l

Panel:

• Charles Max Wood
• Aimee Knight
• Chris Ferdinandi
• AJ O’Neal

Special Guest: Andy Bell

In this episode, the panel talks with Andy Bell who is an independent designer and developer who uses React, Vue, and Node. Today, the panelists and the guest talk about the power of progressive enhancements. Check it out!

Show Topics:

0:00 – Advertisement: KENDO UI

0:34 – Chuck: Hi! Our panel is AJ, Aimee, Chris, myself and my new show is coming out in a few weeks, which is called the DevRev! It helps you with developer’s freedom! I am super excited. Our guest is Andy Bell. Introduce yourself, please.

2:00 – Guest: I am an independent designer and developer out in the U.K.

2:17 – Chuck: You wrote things about Vanilla.js. I am foreshadowing a few things and let’s talk about the power and progressive enhancement.

2:43 – The guest gives us definitions of power and progressive enhancements. He describes how it works.

3:10 – Chuck: I’ve heard that people would turn off JavaScript b/c it was security concern and then your progressive enhancement would make it work w/o JavaScript. I am sure there’s more than that?

3:28 – The guest talks about JavaScript, dependencies, among other things.

4:40 – Chuck: Your post did make that very clear I think. I am thinking I don’t even know where to start with this. Are people using the 6^th version? How far back or what are we talking about here?

5:09 – Guest: You can go really far back and make it work w/o CSS.

5:49 – Chris: I am a big advocate of progressive enhancement – the pushback I get these days is that there is a divide; between the broadband era and AOL dialup. Are there compelling reasons why progressive enhancements even matter?

6:48 – Guest.

8:05 – Panel: My family lives out in the boonies. I am aware of 50% of American don’t have fast Internet. People don’t have access to fast browsers but I don’t think they are key metric users.

8:47 – Guest: It totally depends on what you need it for. It doesn’t matter if these people are paying or not.

9:31 – Chris: Assuming I have a commute on the trail and it goes through a spotty section. In a scenario that it’s dependent on the JS...are we talking about 2 different things here?

10:14 – Panelist chimes-in.

10:36 – Chris: I can take advantage of it even if I cannot afford a new machine.

10:55 – Panel: Where would this really matter to you?

11:05 – Chris: I do have a nice new laptop.

11:12 – Chuck: I had to hike up to the hill (near the house) to make a call and the connection was really poor (in OK). It’s not the norm but it can happen.

11:37 – Chris: Or how about the All Trails app when I am on the trail.

11:52 – Guest.

12:40 – Chris: I can remember at the time that the desktop sites it was popular to have...

Chris: Most of those sites were inaccessible to me.

13:17 – Guest.

13:51 – Chuck: First-world countries will have a good connection and it’s not a big deal. If you are thinking though about your customers and where they live? Is that fair? I am thinking that my customers need to be able to access the podcast – what would you suggest? What are the things that you’d make sure is accessible to them.

14:31 – Guest: I like to pick on the minimum viable experience? I think to read the transcript is important than the audio (MP3).

15:47 – Chuck.

15:52 – Guest: It’s a lot easier with Vue b/c you don’t’ have to set aside rendering.

17:13 – AJ: I am thinking: that there is a way to start developing progressively and probably cheaper and easier to the person who is developing. If it saves us a buck and helps then we take action.

17:49 – Guest: It’s much easier if you start that way and if you enhance the feature itself.

18:38 – AJ: Let me ask: what are the situations where I wouldn’t / shouldn’t worry about progressive enhancements?

18:57 – Guest answers the question.

19:42 – AJ: I want people to feel motivated in a place WHERE to start. Something like a blog needs Java for comments.

Hamburger menu is mentioned, too.

20:20 – Guest.

21:05 – Chris: Can we talk about code?

21:16 – Aimee: This is the direction I wanted to go. What do you mean by that – building your applications progressively?

Aimee refers to his blog.

21:44 – Guest.

22:13 – Chuck: I use stock overflow!

22:20 – Guest.

22:24 – Chuck: I mean that’s what Chris uses!

22:33 – Guest (continues).

23:42 – Aimee.

23:54 – Chris.

24:09 – Chris

24:16 – Chris: Andy what do you think about that?

24:22 – Guest: Yes, that’s good.

24:35 – Chris: Where it falls apart is the resistance to progressive enhancements that it means that your approach has to be boring?

25:03 – Guest answers the question.

The guest mentions modern CSS and modern JavaScript are mentioned along with tooling.

25:50 – Chuck: My issue is that when we talk about this (progressive enhancement) lowest common denominator and some user at some level (slow network) and then they can access it. Then the next level (better access) can access it. I start at the bottom and then go up. Then when they say progressive enhancement I get lost. Should I scrap it and then start over or what?

26:57 – Guest: If it’s feasible do it and then set a timeline up.

27:42 – Chuck: You are saying yes do it a layer at a time – but my question is HOW? What parts can I pair back? Are there guidelines to say: do this first and then how to test?

28:18 – Advertisement – Sentry.io

29:20 – Guest: Think about the user flow. What does the user want to do at THIS point? Do you need to work out the actual dependencies?

30:31 – Chuck: Is there a list of those capabilities somewhere? So these users can use it this way and these users can use it that way?

30:50 – Guest answers the question.

31:03 – Guest: You can pick out the big things.

31:30 – Chuck: I am using this feature in the browser...

31:41 – Guest.

31:46 – Chris: I think this differently than you Andy – I’ve stopped caring if a browser supports something new. I am fine using CSS grid and if your browser doesn’t support it then I don’t have a problem with that. I get hung up on, though if this fails can they still get the content? If they have no access to these – what should they be able to do?

Note: “Cutting the Mustard Test” is mentioned.

33:37 – Guest.

33:44 – Chuck: Knowing your users and if it becomes a problem then I will figure it out.

34:00 – Chris: I couldn’t spare the time to make it happen right now b/c I am a one-man shop.

34:20 – Chuck and Chris go back-and-forth.

34:36 –Chris: Check out links below for my product.

34:54 – AJ: A lot of these things are in the name: progressive.

36:20 – Guest.

38:51 – Chris: Say that they haven’t looked at it all before. Do you mind talking about these things and what the heck is a web component?

39:14 – The guest gives us his definition of what a web component is.

40:02 – Chuck: Most recent episode in Angular about web components, but that was a few years ago. See links below for that episode.

40:25 – Aimee.

40:31 – Guest: Yes, it’s a lot like working in Vue and web components. The concepts are very similar.

41:22 – Chris: Can someone please give us an example? A literal slideshow example?

41:45 – Guest answers the question.

45:07 – Chris.

45:12 – Guest: It’s a framework that just happens to use web components and stuff to help.

45:54 – Chuck: Yeah they make it easier (Palmer). Yeah there is a crossover with Palmer team and other teams. I can say that b/c I have talked with people from both teams. Anything else?

46:39 – Chuck: Where do they go to learn more?

46:49 – Guest: Check out the Club! And my Twitter! (See links below.)

47:33 – Chuck: I want to shout-out about DevLifts that has $19 a month to help you with physical goals. Or you can get the premium slot! It’s terrific stuff. Sign-up with DEVCHAT code but there is a limited number of slots and there is a deadline, too. Just try it! They have a podcast, too!

49:16 – Aimee: Yeah, I’m on their podcast soon!

49:30 – Chuck: Picks!

END – Advertisement: CacheFly!

Links:

• JavaScript
• React
• Elixir
• Ember.js
• Vue
• GO
• jQuery
• Node.js
• Puppeteer
• Cypress
• Past episode: AiA 115
• Past episode: JSJ 120
• Vue.js – Slots
• Using templates and slots – Article
• Web Components Club
• GitHub: Pwa – Starter – Kit
• Progressively Enhanced Toggle Panel
• Time Ago in under 50 lines of JavaScript
• GitHub: ebook-boilerplate
• Chris Ferdinandi’s Go Make Things Site
• Game Chops
• CNBC – Trump Article
• New in Node v10.12
• Quotes Archive
• My Amazon Interview Horror Story
• DevPal.io
• Honest Work
• Relative Paths
• DevLifts
• Andy Bell’s Twitter
• Andy’s Website

Sponsors:

• DevLifts
• Kendo UI
• Sentry
• CacheFly

Picks:

Aimee

• Hacker News  -  Programming Quotes
• My Amazon Interview Horror Story

Chris

• Time Ago in Under 50 Lines of JavaScript
• E-Book Boiler Plate
• JSJABBER at gomakethings.com

AJ

• Experimental Drugs Bill
• My Browers FYI
• New In Node,10.12
• Arcade Attack

Charles

• Getacoderjob.com
• Self-Publishing School
• MF CEO podcast

Andy

• Devpay.io
• Honest.work
• Relativepath.uk

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 

Maximiliano Firtman is a mobile web developer from Buenos Ares, Argentina. He has been a developer for 24 years and his most recent focus has been on progressive web apps, or PWAs. Steve and Max reflect on the technologies they were using when they first got started in web development and talk about their experience with mobile development. One area that Max emphasized was bringing the web into the mobile space. They discuss the progression of web access on mobile and some of the available tools. Max notes that responsible design has a very high cost in web performance for mobile devices, which requires unique approaches. They discuss some of the issues with latency in mobile, even on 4G. The solution to this latency is PWAs.

Progressive web apps are a set of best practices to create web apps that are installable. They can work offline at high speeds on several operating systems. Once installed, it looks like any other app on the system. Max delves into more details on how it works. He talks about how the resources for your application are managed. He assures listeners that it’s just a website that’s using a new API, they’re not changing the way the web works, and that when that API is there, the app can be installed. It will also generally use your default browser. Steve and Max discuss how local data is stored with PWAs. To write PWAs, you can use Angular, React, JavaScript, or Vue, and it’s a pretty transparent process. Max talks about some common tools used for local storage and some of the PWAs he’s worked on in the past. The benefit of using PWAs is that they generally run faster than regular web apps. To get started, Max advises listeners to install one and start exploring.

Panelists

• Steve Edwards

Guest

• Maximiliano Firtman

Sponsors

• G2i

____________________________

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

____________________________________________________________

Links

• Progressive Web Apps

• Appsco.pe

• IndexedDB

• Max's site

Picks

Steve Edwards:

• The Club

Maximiliano Firtman:

• Llama

• Follow Max on Twitter

JavaScript Remote Conf 2020

May 14th to 15th - register now!

Dave Karow is a developer evangelist for Split. He dives into how you can deliver software sustainably without burning out. His background is in performance and he's moved into smooth deliveries. He pushes the ideas behind continuous delivery and how to avoid getting paid to stay late in "free" pizzas.

Panel

• AJ O’Neal

• Aimee Knight

• Charles Max Wood

• Dan Shappir

Guest

• Dave Karow

Sponsors

• G2i | Enjoy the luxuries of freelancing

• Taiko - free and open source browser test automation

• CacheFly

____________________________________________________________

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

____________________________________________________________

Links

• Split.io

• Continuous Delivery

• zeit.co

• The Practical Test Pyramid

• Accelerate

• The Unicorn Project

• Ender's Game

• Ender's Shadow

• Atlassian Summit

• DeliveryConf

• JSJ 418: Security Scary Stories and How to Avoid Them with Kevin A McGrail

• Feature toggle

• split.io Dave Karow

• Progressive Delivery

• Speaker Deck Dave Karow

• Learn Enough Command Line to Be Dangerous

• Beyond Code Bootcamp

Picks

Aimee Knight:

• Designing for Performance

• Early Riser or Night Owl?

Dan Shappir:

• web.dev

AJ O’Neal:

• CineRAID CR-H458

• DataCenter 8TB Drives

• Tiltamax Wireless Follow Focus System

Charles Max Wood

• The Expanse

• Course Creator PRO

Dave Karow:

• Accelerate

Follow JavaScript Jabber on Twitter > @JSJabb

Interview with Benjamin Besse, MD, author of Hyperprogressive Disease in Patients With Advanced Non–Small Cell Lung Cancer Treated With PD-1/PD-L1 Inhibitors or With Single-Agent Chemotherapy

It has restored confidence of businesses as well as provided on-ground support that MSMEs need and farmers deserve, Co-founder of Udaan said

Rotch Library - N7304.5.P76 J86 2018

Hayden Library - PN6725.S35 2019

Lewis Library - ML421.B4 M57 2020

Lewis Library - ML3918.C68 H66 2018