Under President Donald Trump, the trajectory of US-Thai-Asean relations will be defined by three factors -- rising trade imbalances, intensifying US-China rivalry and Asean's long-term aspirations under its Community Vision 2045. Donald Trump's "America First" policies will impose many challenges.

There’s only a single flash-forward in Season 2 of “Bad Sisters,” and it’s the very first scene. Four of the five Garvey sisters — eldest Eva (Sharon Horgan), nurse Ursula (Eva Birthistle), one-eyed Bibi (Sarah Greene) and baby Becka (Eve Hewson) — are in a car, attempting to dispose of a dead body. Becka’s face is swollen […]

The Bearded Reedling used to be known as the Bearded Tit. The name change wasn’t down to some odd political stance. After all, the Great Tit, Blue Tit, Long-tailed Tit, and even the Penduline Tit are all still tits. No, the rationale for the rename is that the Beardie is not a tit all. It … Continue reading "Bearded Reedling redux"

Christopher Nolan's epic new film "Oppenheimer" is no mere biopic… nor is it the first attempt to capture the father of the atomic bomb in fiction. We look at prior dramatizations of this very complicated man—including one wherein J. Robert Oppenheimer played himself!—and examine why they worked or didn't. In this episode: Physicist-turned-photographer Minesh Bacrania shares his experience photographing inside the top-secret labs at Los Alamos National Laboratory, where J. Robert Oppenheimer and other scientists created the first nuclear weapon. Next, with Christopher Nolan’s film Oppenheimer exceeding commercial expectations, Smithsonian magazine writer Andy Kifer discusses the complexities of Oppenheimer's genius and how prior attempts to depict him in film and television and on stage have fared. Read Andy Kifer’s “The Real Story Behind Christopher Nolan’s Oppenheimer” here (https://www.smithsonianmag.com/history/the-real-history-behind-christopher-nolans-oppenheimer-180982529/) . See Minesh Bacrania’s photographs of Los Alamos and read Smithsonian senior editor Jennie Rothenberg Gritz’s text here (https://www.smithsonianmag.com/history/exclusive-behind-scenes-look-los-alamos-lab-where-robert-oppenheimer-created-atomic-bomb-180982336/) or in the July/August 2023 issue of Smithsonian. Original release date: July 27, 2023 There’s More to That is a production of Smithsonian magazine and PRX Productions. From the magazine, our team is Chris Klimek, Debra Rosenberg and Brian Wolly. From PRX, our team is Jessica Miller, Genevieve Sponsler, Adriana Rozas Rivera, Terence Bernardo, and Edwin Ochoa. The Executive Producer of PRX Productions is Jocelyn Gonzales. Episode artwork by Emily Lankiewicz. Music by APM Music.

Maybe those pesky sites are good for something after all. 

It's been six years since Pfizer boldly announced the launch of its "clinical trial in a box". The REMOTE trial was designed to be entirely online, and involved no research sites: study information and consent was delivered via the web, and medications and diaries were shipped directly to patients' homes.

Despite the initial fanfare, within a month REMOTE's registration on ClinicalTrials.gov was quietly reduced from 600 to 283. The smaller trial ended not with a bang but a whimper, having randomized only 18 patients in over a year of recruiting.

Still, the allure of direct to patient clinical trials remains strong, due to a confluence of two factors. First, a frenzy of interest in running "patient centric clinical trials". Sponsors are scrambling to show they are doing something – anything – to show they have shifted to a patient-centered mindset. We cannot seem to agree what this means (as a great illustration of this, a recent article in Forbes on "How Patients Are Changing Clinical Trials" contained no specific examples of actual trials that had been changed by patients), but running a trial that directly engages patients wherever they are seems like it could work.

The less-openly-discussed other factor leading to interest in these DIY trials is sponsors' continuing willingness to heap almost all of the blame for slow-moving studies onto their research sites. If it’s all the sites’ fault – the reasoning goes – then cutting them out of the process should result in trials that are both faster and cheaper. (There are reasons to be skeptical about this, as I have discussed in the past, but the desire to drop all those pesky sites is palpable.)

However, while a few proof-of-concept studies have been done, there really doesn't seem to have been another trial to attempt a full-blown direct-to-patient clinical trial. Other pilots have been more successful, but had fairly lightweight protocols. For all its problems, REMOTE was a seriously ambitious project that attempted to package a full-blown interventional clinical trial, not an observational study.

In this context, it's great to see published results of the TAPIR Trial in vasculitis, which as far as I can tell is the first real attempt to run a DIY trial of a similar magnitude to REMOTE.

TAPIR was actually two parallel trials, identical in every respect except for their sites: one trial used a traditional group of 8 sites, while the other was virtual and recruited patients from anywhere in the country. So this was a real-time, head-to-head assessment of site performance.

And the results after a full two years of active enrollment?

• Traditional sites: 49 enrolled
• Patient centric: 10 enrolled

As voters across the United States head to the polls, we speak with New York Times writer Jim Rutenberg about how Donald Trump may try to preemptively declare victory and challenge election results. The former president has ramped up claims Democrats are “a bunch of cheats” and preemptively cast doubt on a win by Vice President Kamala Harris, following a similar playbook as 2020 when he baselessly claimed the election was stolen. Rutenberg spoke to pro-Trump election officials in battleground states of Arizona, Georgia, Nevada and Pennsylvania who say they are ready to refuse to certify local election results as part of a wide-ranging effort to throw the system into disarray. Rutenberg says after the failed insurrection of January 6, 2021, many in Trump’s orbit had a clear goal for 2024: “We have to go local.” He also discusses the Electoral Count Reform Act of 2022 that makes it harder to stop the final certification of results.

National Bureau of Economic Research

Surviving Self-Distancing-Day 4

All over Oakland right now people are wearing Warriors shirts and flying their Warriors flags from their cars, and as much as we like our hometown team here at 99pi, we've been following these NBA finals for another design-related reason. When you watch the games in Toronto the whole stadium is filled with people wearing red raptors jerseys, but every now and then you'll see these little flashes of purple. Those bold fans are wearing one of the most polarizing jerseys in the history of sports. A jersey that we actually did a whole episode about last year. So in honor of the Toronto Raptors, and the beautifully ugly jersey they gave the world, we're gonna rerun that episode for you today, along with an update from our new 99pi team member Chris Berube, a Torontonian and Raptors fan since he was a kid.

The Barney Design Redux

This is the newly updated story of a curvy, kidney-shaped swimming pool born in Northern Europe that had a huge ripple effect on popular culture in Southern California and landscape architecture in Northern California, and then the world. A documentary in three parts with a brand new update about how this episode resulted in a brand new skate park in a very special city.

The Pool and the Stream Redux

It was the middle of the night on March 27, 1964. Earlier that evening, the second-biggest earthquake ever measured at the time had hit Anchorage, Alaska. Some houses had been turned completely upside down while others had skidded into the sea. But that brief and catastrophic quake was just the beginning of the story. This is the story of one woman who held a community together.

This is Chance! Redux

Buy Jon Mooallem’s This is Chance!

Michael Mahemoff writes: To be effective, Rails cache sweepers need to be more fully understood.  They know no standard, so you must employ art. He goes on: Sweepers observe both your models and your controllers, but most workarounds focus on their controller nature.  Importantly: the sweeper must be explicitly added as an observer. Even more Read the rest...

Triple Spiral Audio has announced the release of Paradox Lost Redux, a unique Kontakt instrument library by Beautiful Void Audio based on strange, beautiful, and bizarre soundscapes, drones and “simple” tones. At times the sounds capture a fitting, paradoxical cross between evolving and static, beautiful and dirty, dark and light. Some sounds will seem familiar […]

The post Triple Spiral Audio launches Paradox Lost Redux by Beautiful Void Audio appeared first on rekkerd.org.

Karen and Bradley discuss the sexist comment issue that occurred a few months ago at PyCon USA 2013.

Show Notes:

Segment 0 (00:00:34)

• Bradley and Karen previously discussed conference behavior back in Episode 0x04.
• Bradley had blogged a few years ago about the issues of sexism through the computer industry, including this study showing the glass ceiling in CS academics. (05:17)
• Bradley mentioned that he'd blogged in the past that proprietary software companies also have issues of sexism at conferences (05:58)
• Bradley mentioned the How to Perform Like a Porn Star CouchDB talk at a Ruby Conference (06:13)
• There is indeed a Project named PyCorn. (09:38)
• Bradley mentioned the Planet Money story about Online Pharmacies but he couldn't find the original audio of the longer piece that ends with the phrase Stay Shady, Internet (21:30)
• Bradley mentioned a quote about the human mind being the most dangerous thing because everything is in it, which is actually from Heart of Darkness by Joesph Conrad. (23:40)
• Bradley mentioned that a keynoter at LinuxCon Europe made sexist comments back in 2011. (30:02)
• Bradley and Karen encouraged listeners to promote the GNOME Foundation Outreach Program for Women (31:20)
• Bradley mentioned Shuttleworth's comment at LinuxCon North America in 2009 (32:02).

Send feedback and comments on the cast to <oggcast@faif.us>. You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on on Twitter and and FaiF on Twitter.

Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums.

The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen discuss the key differences between 501(c)(3) and 501(c)(6) organizations in the USA, and discuss recent refusals by the IRS to grant such statuses to Open Source and Free Software orgs.

Show Notes:

Segment 0 (00:34)

• Bradley mentioned the 501(c)(3) vs. 501(c)(6) difference came up on FaiF 0x41. (03:35)
• Bradley mentioned that in 501(c)(3) status from the IRS is based on receiving some status governed by §170(b)(1)(A) of the tax code. (Most Free Software charities, such as Conservancy, are classifed as non-profit charities under §170(b)(1)(A)(vi).) (05:10)
• Bradley mentioned this issue had been discussed on FLOSS Foundations' mailing list (05:50)
• Bradley discussed that at the OSCON 2013 tutorial, Community Foundations 101, most of the 501(c)(6) representatives who spoke argued incorrectly that the differences between 501(c)(3)'s and 501(c)(6)'s were not substantive. (10:50)
• Karen referenced how the TV show Silicon Valley parodies the irony of for-profit software companies claiming they make the world a better place. (11:58)
• Bradley mentioned he was inspired by Michael Moore in his work on Free Software. (15:02)
• Bradley mentioned Karen's talk called Identity Crisis (15:21)
• Karen mentioned that open source was on the list of items the IRS gave additional scrutiny. (16:51)
• Bradley mentioned a blog post by Jim Nelson where Yorba's rejection was discussed; Yorba's 501(c)(3) application was previously discussed on was discussed on 0x1C, and covered in many other places. (17:46)
• Karen wrote a blog post about why she isn't worried for Conservancy's 501(c)(3) status at this time. (18:30)
• Bradley mentioned that IRS decisions don't make precedent, and if there's a dispute, it would go to USA Tax Court (19:00)
• Mozilla Foundation's odd hybrid for-profit/non-profit model was audited by the IRS, and Mozilla Foundation settled with the IRS. (20:22)
• Open Stack Foundation was initially denied 501(c)(6) status, as reported on Mark McLoughlin's blog. (25:10)
• Bradley promised links to both Yorba's 501(c)(3) denial letter from the IRS and Open Stack Foundation's 501(c)(6) denial letter from the IRS. (The response to the IRS from OpenStack, written by DLA Piper, OpenStack Foundation's law firm, is also available, too. (27:15)
• Bradley and Karen discussed Board of Directors meetings in FaiF 0x45: I'm Board (31:40)
• Bradley mentioned the How fresh stays fresh campaign, which includes the Nature's Pause Button television commercials by the American Frozen Food Institute, which is a 501(c)(6) organization. It's FY 2012 Form 990 is the most recent on available.
• Bradley also mentioned the Beef: It's What's For Dinner advertisting campaign that has existed for decades in the USA, which is sponsored by the National Cattlemen's Beef Association, Inc. which is a 501(c)(6) as well. It's FY 2012 Form 990 is the most recent on available.
(35:40)
• Bradley further mentioned the Pork: the other white meat advertising campaign, which has also existed for decades but is now called the Pork: Be Inspired campaign, seems a bit more dubious in its non-profit existence. It appears to be funded by the National Pork Board Foundation, which is ostensibly a 501(c)(3) but has no assets, revnue nor expenses, and appears to be a front for an org called the America's Pork Producers / Pork Checkoff, which appears to be some quasi-govermental agency related to pork (in other words, it's pork for pork). More research would probably be needed to figure out better what's going on here with regard to non-profit status, but it seems that unlike the Beef ads, which are clearly funded by a 501(c)(6), this campaign is funded by a separate legislation, presumably unrelated to §501(c). There is, BTW, also, a 501(c)(5) called the National Pork Producers Council, which appears to be where the big money is (— not surprisingly — 501(c)(4)'s and 501(c)(5)'s often make 501(c)(6)'s and 501(c)(3)'s look tiny by comparison). (36:13)

Segment 1 (39:43)

Conservancy and OSI jointly announced a working group on IRS applications and denials. (40:49)

Send feedback and comments on the cast to <oggcast@faif.us>. You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on on Twitter and and FaiF on Twitter.

Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums.

The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

In what seems like a decade ago (but was only early March), the ever talented Liz Tippett interviewed me for her brilliant Oregon Law Lab (in person!) about Trump’s Art of the Deal.  Spoiler alert:  We conclude that the book should best be read as a handbook for how to deal with lying…  Enjoy!

PotterCast is BACK after a long hiatus. This episode is our first crack at playing catch up on all the news we've missed since our last show at LeakyCon! We also begin digging into what we all know about Pottermore and where the PotterCast trio were sorted!

Episode 243 — Pottermore Redux

Find the latest episode and explore PotterCast interviews, discussions and more at PotterCast.com

Visit the-leaky-cauldron.org for the latest and greatest from Harry Potter's Wizard World.

Invitation Only Research Event

Event participants

Dr Joseph Pilat, Los Alamos National Laboratory and Woodrow Wilson International Center for Scholars
Chair: Dr Patricia Lewis, Research Director, International Security Programme, Chatham House

Hedibert F. Lopes, Nicholas G. Polson.

Source: Brazilian Journal of Probability and Statistics, Volume 33, Number 4, 745--755.

Abstract:
Bayesian hypothesis testing is re-examined from the perspective of an a priori assessment of the test statistic distribution under the alternative. By assessing the distribution of an observable test statistic, rather than prior parameter values, we revisit the seminal paper of Edwards, Lindman and Savage ( Psychol. Rev. 70 (1963) 193–242). There are a number of important take-aways from comparing the Bayesian paradigm via Bayes factors to frequentist ones. We provide examples where evidence for a Bayesian strikingly supports the null, but leads to rejection under a classical test. Finally, we conclude with directions for future research.

Sales of which electric car plunged the steepest leading into the U.S. pandemic slowdown? Which automaker reaffirmed its commitment to hydrogen fuel cells? This is our look back at the Week In Reverse—right here at Green Car Reports—for the week ending May 8, 2020. Our biggest combination of stories this week related to the most...

Why Mattel's diabolical darling could be a threat to children’s privacy, wellbeing, and creativity.

CDL relies on an incorrect interpretation of copyright’s “fair use” doctrine to give legal cover to Open Library and potentially other CDL users’ outright piracy—scanning books without permission and lending those copies via the internet. By restricting access to one user at a time for each copy that the library owns, the proponents analogize scanning and creating digital copies to physically lending a legally purchased book. Although it sounds like an appealing argument, the CDL concept is based on a faulty legal argument that has already been rejected by the U.S. courts.

In Capitol Records v. ReDigi, the Second Circuit held that reselling a digital file without the copyright holder’s permission is not fair use because the resales competed with the legitimate copyright holder’s sales. It found that market harm was likely because the lower-priced resales were sold to the same customers who would have otherwise purchased new licenses. In this regard, the court emphasized a crucial distinction between resales of physical media and resales of digital content, noting that unlike physical copies, digital content does not deteriorate from use and thus directly substitutes new licensed digital copies.

The same rationale applies to the unauthorized resale or lending of ebooks. Allowing libraries to digitize and circulate copies made from physical books in their collection without authorization, when the same books are available or potentially available on the market, directly competes with the market for legitimate ebook licenses, ultimately usurping a valuable piece of the market from authors and copyright holders.

To address our unprecedented global and immediate need for access to reading and research materials, as of today, March 24, 2020, the Internet Archive will suspend waitlists for the 1.4 million (and growing) books in our lending library by creating a National Emergency Library to serve the nation’s displaced learners. This suspension will run through June 30, 2020, or the end of the US national emergency, whichever is later.

During the waitlist suspension, users will be able to borrow books from the National Emergency Library without joining a waitlist, ensuring that students will have access to assigned readings and library materials that the Internet Archive has digitized for the remainder of the US academic calendar, and that people who cannot physically access their local libraries because of closure or self-quarantine can continue to read and thrive during this time of crisis, keeping themselves and others safe.

IA is using a global crisis to advance a copyright ideology that violates current federal law and hurts most authors. It has misrepresented the nature and legality of the project through a deceptive publicity campaign. Despite giving off the impression that it is expanding access to older and public domain books, a large proportion of the books on Open Library are in fact recent in-copyright books that publishers and authors rely on for critical revenue. Acting as a piracy site—of which there already are too many—the Internet Archive tramples on authors’ rights by giving away their books to the world.

[U]sing the Coronavirus pandemic as an excuse, the Archive has created the “National Emergency Library” and removed virtually all controls from the digital copies so that they can be viewed and downloaded by an infinite number of readers. The uncontrolled distribution of copyrighted material is an additional blow to authors who are already facing long-term disruption of their income because of the pandemic. Uncontrolled Digital Lending lacks any legal argument or justification.

I am not aware of any measure under copyright law that permits a user of copyrighted works to unilaterally create an emergency copyright act. Indeed, I am deeply concerned that your "Library" is operating outside the boundaries of the copyright law that Congress has enacted and alone has the jurisdiction to amend.

In an early analysis of the use we are seeing what we expected: 90% of the books borrowed were published more than ten years ago, two-thirds were published during the twentieth century. The number of books being checked out and read is comparable to that of a town of about 30,000 people. Further, about 90% of people borrowing the book only looked at it for 30 minutes. These usage patterns suggest that perhaps that patrons may be using the checked-out book for fact checking or research, but we suspect a large number of people are browsing the book in a way similar to browsing library shelves.

After writing my post a few months ago on building your own redux app, I have been asked a couple times to write a guide on creating redux middleware and how it works. This will be a quick post on how you can acheive anything with your own middleware!

##Basic middleware

const customMiddleware = store => next => action => {
  if(action.type !== 'custom') return next(action)
  //do stuff!
}

Applying it:

import { createStore, applyMiddleware, } from 'redux'
import reducer from './reducer'
import customMiddleware from './customMiddleware'

const store = createStore(
  reducer,
  applyMiddleware(customMiddleware)
)

Whaaa? store => next => action => I know that looks confusing. Essentially you are building a chain of functions, it will look like this when it gets called:

//next looks something like this:
let dispatched = null
let next = actionAttempt => dispatched = actionAttempt 

const dispatch = customMiddleware(store)(next)

dispatch({
  type: 'custom',
  value: 'test'
})

All you are doing is chaining function calls and passing in the neccesary data. When I first saw this I was confused a little due to the long chain, but it made perfect sense after reading the article on writing redux tests.

So now that we understand how those chained functions work, let’s explain the first line of our middleware.

if(action.type !== 'custom') return next(action)

There should be some way to tell what actions should go through your middleware. In this example, we are saying if the action’s type is not custom call next, which will pass it to any other middleware and then to the reducer.

##Doing Cool stuff

The official guide on redux middleware covers a few examples on this, I’m going to try to explain it in a more simple way.

Say we want an action like this:

dispatch({
  type: 'ajax',
  url: 'http://api.com',
  method: 'POST',
  body: state => ({
    title: state.title
    description: state.description
  }),
  cb: response => console.log('finished!', response)
})

We want this to do a post request, and then call the cb function. It would look something like this:

import fetch from 'isomorphic-fetch'

const ajaxMiddleware = store => next => action => {
  if(action.type !== 'ajax') return next(action)
  
  fetch(action.url, {
    method: action.method,
    body: JSON.stringify(action.body(store.getState()))
  })
  .then(response => response.json())
  .then(json => action.cb(json))
}

It’s pretty simple really. You have access to every method redux offers in middleware. What if we wanted the cb function to have access to dispatching more actions? We could change that last line of the fetch function to this:

.then(json => action.cb(json, store.dispatch))

Now in the callback, we can do:

  cb: (response, dispatch) => dispatch(newAction(response))

As you can see, middleware is very easy to write in redux. You can pass store state back to actions, and so much more. If you need any help or if I didn’t go into detail enough, feel free to leave a comment below!

One of the most common problems that I run into when using Redux is trying to figure out why an action is not being captured by a reducer. For someone just getting starting with Redux, debugging this issue can be especially overwhelming because of how Redux manages data flow. So before you start pouring over configuration code, or the logic contained in your action creators and reducers, please, make sure your action types are defined and spelled correctly.

One of the most common problems that I run into when using Redux is trying to figure out why an action is not being captured by a reducer. For someone just getting starting with Redux, debugging this issue can be especially overwhelming because of how Redux manages data flow. So before you start pouring over configuration code, or the logic contained in your action creators and reducers, please, make sure your action types are defined and spelled correctly.

In any application that I have built, most bugs that I have run into are simply due to typos. However, the solution to this particular problem is harder to spot because no errors are raised when the application is run. Take a look at the snippet below.

// actionTypes.js

export const FETCH_FILE_REQUEST = 'fetch_file_request';
export const FETCH_FILE_SUCCESS = 'fetch_file_success';
export const FETCH_FILE_FAIL = 'fetch_file_fail';


// filesReducer.js

import {
  FETCH_FILE_REQUEST,
  FETCH_FILE_SUCESS,
  FETCH_FILE_FAIL
} from '../actions/actionTypes';

const filesReducer = (state = {}, action) => {
  switch (action.type) {
    case FETCH_FILE_SUCESS:
      return { ...state, file: action.payload };
    default:
      return state;
  }
}

export default filesReducer;

Assuming we dispatched an action with type FETCH_FILE_SUCCESS, the filesReducer should catch the action before the default case is returned. But what if that is not happening? Where do we start the debugging process. There does not appear to be anything wrong with the code in the reducer; the action type was imported and matches the case in the switch statement. There are no errors in the browser. Where is the issue?

You may have noticed that I misspelled SUCCESS in filesReducer.js, but the reason this can be hard to catch is because importing undefined types does not cause an error, so when we import FETCH_FILE_SUCESS, its value is actually undefined, so our reducer always hits the default case.

It would be nice if the existing import/export system could help us catch this. Unfortunately, since action types are just strings, validating their existence is challenging. Luckily, we have another option.

Enter Proxies

Proxies are a feature of ES2015 that allow us to customize operations on a object. They can be used in many different ways, and you can find some useful examples here and here. For our problem, this example from Mozilla looks promising:

let validator = {
  set: function(obj, prop, value) {
    if (prop === 'age') {
      if (!Number.isInteger(value)) {
        throw new TypeError('The age is not an integer');
      }
      if (value > 200) {
        throw new RangeError('The age seems invalid');
      }
    }

    // The default behavior to store the value
    obj[prop] = value;

    // Indicate success
    return true;
  }
};

let person = new Proxy({}, validator);

person.age = 100;
console.log(person.age); // 100
person.age = 'young'; // Throws an exception
person.age = 300; // Throws an exception

So if proxies can be used to validate that properties assigned to an object are of a certain type and value, we should definitely be able to ensure that our action types are never undefined, or else throw an error that will be easy for us to fix. Let’s refactor our actionTypes.js file.

// actionTypes.js

const types = {
  FETCH_FILE_REQUEST: 'fetch_file_request',
  FETCH_FILE_SUCCESS: 'fetch_file_success',
  FETCH_FILE_FAIL: 'fetch_file_fail'
}

const typeValidator = {
  get(obj, prop) {
    if (obj[prop]) {
      return prop;
    } else {
      throw new TypeError(`${prop} is not a valid action type`);
    }
  }
}

module.exports = new Proxy(types, typeValidator);

First, we define a object containing all our action types. Then we define our validator handler typeValidator. The get method inside our handler is called a trap, and provides access to the properties of a object. If the property we are looking for, an action type, in this case, exists in the types object, return that prop, unmodified. Otherwise, throw an error because the prop does not exist.

Finally, export a new proxy, passing the types object as the target and the typeValidator as the handler. However, it is important to note that the ES2015 module system does not work well with proxies, so module.exports and require() must be used for exporting and importing the types.

Barely any code needs to change in the reducer and action creator files, but in order for the action types to be imported successfully, we just need couple lines of code in a new file:

// actionTypesProxy.js

export const {
  FETCH_FILE_REQUEST,
  FETCH_FILE_SUCCESS,
  FETCH_FILE_FAIL,
} = require('./actionTypes');

// in the reducer and action creator files
// change '../actions/actionTypes' to
// '../actions/actionTypesProxy'

By creating a proxy to verify the existence of an action type, we no longer have to worry about correctly naming a property upon import because an error will be thrown in the browser console as soon as the application starts. So, reduce the number headaches you get when developing an application using Redux and start using proxies.

Interested in learning how to build applications using Redux with ReactJS. Check out this online course! Modern React with Redux

The British Film Institute has just launched a season of Woody Allen comedies, ranging from his knockabout beginnings to the recent Midnight in Paris, his biggest commercial success to date. Like Match Point (2005) and Vicky Christina Barcelona (2008), Midnight in Paris was hailed as a “return to form” by some – but has he really still got it? How does his recent output compare to the earlier films? And do those classics still resonate today? Raphael Abraham is joined in the studio by Geoff Andrew, Head of Film Program at the BFI, Peter Aspden, FT arts writer and Nigel Andrews, FT film critic. Produced by Griselda Murray Brown  

See acast.com/privacy for privacy and opt-out information.

A mega Indian Army exercise aimed at sharpening Army's deep strike capabilities in enemy territory concluded last month in Rajasthan. Firdaus Ahmed analyses why having the strike capabilities in this nuclear age might be a mixed blessing.

Online Resource

02:25 - Dan Abramov Introduction

• Twitter
• GitHub
• Dan Abramov: Live React: Hot Reloading with Time Travel @ react-europe 2015

02:43 - Dan’s Background and Journey Into Building Stuff with React

• Visual Basic

05:48 - redux and React    

10:07- The Elm Programming Language

12:19 - Reducers

14:04 - Hot Reloading

17:50 - “React makes you a better JavaScript developer.”

22:10 - Time Travel

28:26 - Storing Data and Managing State

• Interacting with the browser on CircleCI's VM

34:43 - [Patreon] Support Dan Abramov Creating Redux and React Hot Loader

36:24 - react-transform

• react-proxy
• babel-plugin-react-transform
• react-transform-catch-errors

41:34 - Using redux outside React

43:52 - Editors and Programmer Productivity

45:35 - Future Plans

Picks

The OAuth2 RFC (Aimee)
Michael Ries: Hiring Apprentices (Jamison)
@sebmck: "Sometimes having email history isn't always a good thing..." (Jamison)
Metal Gear Solid 5: The Phantom Pain (Jamison)
Firefly (Joe)
The Elm Programming Language (Joe)
Google Keep (Dave)
15 Minute Podcast Listener chat with Charles Wood (Chuck)
Pebble Time (Chuck)
100 Days of Burpees (Chuck)
Broad City (Dan)
Jamie xx: In Colour (Dan)
Cycle.js (Dan)

Twitter Lite uses Redux for state management and relies on code-splitting. However, Redux’s default API is not designed for applications that are incrementally-loaded during a user session.

This post describes how I added support for incrementally loading the Redux modules in Twitter Lite. It’s relatively straight-forward and proven in production over several years.

Redux modules

Redux modules comprise of a reducer, actions, action creators, and selectors. Organizing redux code into self-contained modules makes it possible to create APIs that don’t involve directly referencing the internal state of a reducer – this makes refactoring and testing a lot easier. (More about the concept of redux modules.)

Here’s an example of a small “redux module”.

// data/notifications/index.js

const initialState = [];
let notificationId = 0;

const createActionName = name => `app/notifications/${name}`;

// reducer
export default function reducer(state = initialState, action = {}) {
  switch (action.type) {
    case ADD_NOTIFICATION:
      return [...state, { ...action.payload, id: notificationId += 1 }];
    case REMOVE_NOTIFICATION:
      return state.slice(1);
    default:
      return state;
  }
}

// selectors
export const selectAllNotifications = state => state.notifications;
export const selectNextNotification = state => state.notifications[0];

// actions
export const ADD_NOTIFICATION = createActionName(ADD_NOTIFICATION);
export const REMOVE_NOTIFICATION = createActionName(REMOVE_NOTIFICATION);

// action creators
export const addNotification = payload => ({ payload, type: ADD_NOTIFICATION });
export const removeNotification = () => ({ type: REMOVE_NOTIFICATION });

This module can be used to add and select notifications. Here’s an example of how it can be used to provide props to a React component.

// components/NotificationView/connect.js

import { connect } from 'react-redux';
import { createStructuredSelector } from 'reselect';
import { removeNotification, selectNextNotification } from '../../data/notifications';

const mapStateToProps = createStructuredSelector({
  nextNotification: selectNextNotification
});
const mapDispatchToProps = { removeNotification };

export default connect(mapStateToProps, mapDispatchToProps);

// components/NotificationView/index.js

import connect from './connect';
export class NotificationView extends React.Component { /*...*/ }
export default connect(NotificationView);

This allows you to import specific modules that are responsible for modifying and querying specific parts of the overall state. This can be very useful when relying on code-splitting.

However, problems with this approach are evident once it comes to adding the reducer to a Redux store.

// data/createStore.js

import { combineReducers, createStore } from 'redux';
Import notifications from './notifications';

const initialState = /* from local storage or server */

const reducer = combineReducers({ notifications });
const store = createStore(reducer, initialState);

export default store;

You’ll notice that the notifications namespace is defined at the time the store is created, and not by the Redux module that defines the reducer. If the “notifications” reducer name is changed in createStore, all the selectors in the “notifications” Redux module no longer work. Worse, every Redux module needs to be imported in the createStore file before it can be added to the store’s reducer. This doesn’t scale and isn’t good for large apps that rely on code-splitting to incrementally load modules. A large app could have dozens of Redux modules, many of which are only used by a few components and unnecessary for initial render.

Both of these issues can be avoided by introducing a Redux reducer registry.

Redux reducer registry

The reducer registry enables Redux reducers to be added to the store’s reducer after the store has been created. This allows Redux modules to be loaded on-demand, without requiring all Redux modules to be bundled in the main chunk for the store to correctly initialize.

// data/reducerRegistry.js

export class ReducerRegistry {
  constructor() {
    this._emitChange = null;
    this._reducers = {};
  }

  getReducers() {
    return { ...this._reducers };
  }

  register(name, reducer) {
    this._reducers = { ...this._reducers, [name]: reducer };
    if (this._emitChange) {
      this._emitChange(this.getReducers());
    }
  }

  setChangeListener(listener) {
    this._emitChange = listener;
  }
}

const reducerRegistry = new ReducerRegistry();
export default reducerRegistry;

Each Redux module can now register itself and define its own reducer name.

// data/notifications/index.js

import reducerRegistry from '../reducerRegistry';

const initialState = [];
let notificationId = 0;

const reducerName = 'notifications';

const createActionName = name => `app/${reducerName}/${name}`;

// reducer
export default function reducer(state = initialState, action = {}) {
  switch (action.type) {
    case ADD_NOTIFICATION:
      return [...state, { ...action.payload, id: notificationId += 1 }];
    case REMOVE_NOTIFICATION:
      return state.slice(1);
    default:
      return state;
  }
}

reducerRegistry.register(reducerName, reducer);

// selectors
export const selectAllNotifications = state => state[reducerName];
export const selectNextNotification = state => state[reducerName][0];

// actions
export const ADD_NOTIFICATION = createActionName(ADD_NOTIFICATION);
export const REMOVE_NOTIFICATION = createActionName(REMOVE_NOTIFICATION);

// action creators
export const addNotification = payload => ({ payload, type: ADD_NOTIFICATION });
export const removeNotification = () => ({ type: REMOVE_NOTIFICATION });

Next, we need to replace the store’s combined reducer whenever a new reducer is registered (e.g., after loading an on-demand chunk). This is complicated slightly by the need to preserve initial state that may have been created by reducers that aren’t yet loaded on the client. By default, once an action is dispatched, Redux will throw away state that is not tied to a known reducer. To avoid that, reducer stubs are created to preserve the state.

// data/createStore.js

import { combineReducers, createStore } from 'redux';
import reducerRegistry from './reducerRegistry';

const initialState = /* from local storage or server */

// Preserve initial state for not-yet-loaded reducers
const combine = (reducers) => {
  const reducerNames = Object.keys(reducers);
  Object.keys(initialState).forEach(item => {
    if (reducerNames.indexOf(item) === -1) {
      reducers[item] = (state = null) => state;
    }
  });
  return combineReducers(reducers);
};

const reducer = combine(reducerRegistry.getReducers());
const store = createStore(reducer, initialState);

// Replace the store's reducer whenever a new reducer is registered.
reducerRegistry.setChangeListener(reducers => {
  store.replaceReducer(combine(reducers));
});

export default store;

Managing the Redux store’s reducer with a registry should help you better code-split your application and modularize your state management.