kfinley

Yes, most likely the restaurant employees. That's probably why they are starting with orders that are fulfilled by DoorDash employees.

From the article

> The service will begin with deliveries from DashMart, DoorDash’s owned and operated convenience, grocery, and retail store that also powers DashMart Fulfillment Services, with plans to expand over time.

> If any hedge funds are looking for analysts, I'm always open to offers...

How would you invest based on this prediction?

> The problem is that you can’t use the 16” with an external display and the lid open without the fans spinning at full speed.

I had the same problem, when connected to a USB-C monitor I wanted to use the keyboard, but not the built in monitor. Even with the display backlight off the fan would still run. After a lot of searching I found that you can disable the built in monitor by:

- Booting into recovery mode - Opening Terminal - Entering `sudo nvram boot-args="niog=1"` - Restarting - Close the clamshell - Plug in the external monitor - Open the monitor

I hope that helps.

> "You pop it into a headset which has eye sensors on it, which enables the next iPhone to have a higher apparent frame rate and polygon count than a PC with a Nvidia 1080 card in it."

Interesting. Ive said that the touch bar was the first step in a new paradigm. Maybe the next step is connect your iPhone as the display. That would explain why Apple stopped investing in displays.

> Does the 'fn' key force-change the touchbar to display F1-F12?

Yes it does

I suspect we will see the share desktop experience extend to other devices.

In an post release interview Jony Ive implied that the touch bar was the first step in a new paradigm.

Imagine the Photoshop toolbar being available on your iPad's touch screen, while you're editing a photo on your Mac. Or playing a video game while using your iPhone for controls.

That's a fair point. Kind of like adding a redux @connect in a child component.

Edit: To the idiomatic point. The first thing that struct me when using React, was that instead of having to use a custom Component for a for loop I could just use someArray.map(). I see this as a similar situation.

You can still do nesting within a case, or add another case 'about-team': and add another {var} to your component. That's essentially what RR would do. React Router approach is probably a little cleaner, however.

Interesting change. If I understand correctly, basically you have a base component that updates fragments of the UI based on the route.

    const App = () => (
      <BrowserRouter>
        <h1>Hello World</h1>
        <Match exactly pattern="/" component={Home} />
        <Match pattern="/about" component={About} />
        <Miss component={NoMatch}/>
      </BrowserRouter>
    )

Couldn't we take it one step farther and just use a switch statement? It seems like using pure JavaScript would be more idiomatic React. The URL pattern could be parsed in the data layer, and passed down as props. That way the components don't rely on global state, making them easier to test.

    const App = (screen, args) => {
      let content;
      switch (screen) {
      case 'home':
        content = <Home args={args} />
        break;
      case 'about':
        content = <About args={args} />
        break;
      default:
        content = <NoMatch args={args} />
        break;
      }
      return (
        <div>
          <h1>Hello World</h1>
          {content}
        </div>
      )
    }

It's probably just a matter of preference. Recently I started using React-Storybook, so I've become addicted to "dumb" components.