cromat

Step by step guide to run redis-server inside WSL(Windows Subsystem for Linux) on Windows

I have tried to setup redis as starting background task with wsl-autostart, Task Scheduler and with lot vbs scripts including one described here but none of them seemed to work.

In the end I have manually created a simple one that does the job. This script basically starts a hidden Ubuntu Window and starts redis-server inside it.

1. Install WSL (this is tested with Ubuntu 18.04 version)
2. Install redis-server inside WSL sudo apt install redis-server
3. Add sudo permission to your user to execute service command without password

sebmarkbage

The Rules of React

All libraries have subtle rules that you have to follow for them to work well. Often these are implied and undocumented rules that you have to learn as you go. This is an attempt to document the rules of React renders. Ideally a type system could enforce it.

What Functions Are "Pure"?

A number of methods in React are assumed to be "pure".

On classes that's the constructor, getDerivedStateFromProps, shouldComponentUpdate and render.

a-h

import React from 'react';
import { shallow } from 'enzyme';

const Item = text => <p>Item {text}</p>;

const Composition = ({ showB }) => (
  <p>
    <Item text="A" />
    {showB && <Item text="B" />}
  </p>);

Rich-Harris

Stuff I wish I'd known sooner about service workers

I recently had several days of extremely frustrating experiences with service workers. Here are a few things I've since learned which would have made my life much easier but which isn't particularly obvious from most of the blog posts and videos I've seen.

I'll add to this list over time – suggested additions welcome in the comments or via twitter.com/rich_harris.

Use Canary for development instead of Chrome stable

Chrome 51 has some pretty wild behaviour related to console.log in service workers. Canary doesn't, and it has a load of really good service worker related stuff in devtools.

vasanthk

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

1. Clarify and agree on the scope of the system

• User cases (description of sequences of events that, taken together, lead to a system doing something useful)
  • Who is going to use it?
  • How are they going to use it?

tssm

About programms

• Death to the Dialog Box
• Defending Perpetual Intermediacy
• Are your exceptions silent?
• Teaching Users to Read
• You'll Never Have Enough Cheese
• Gold Plating
• Happy Talk Must Die
• The Broken Window Theory