Two of the paper's authors work at the technology arm of Zozotown, one of Japan's largest fashion e-commerce sites, which points to how this could have practical benefits.

Ignoring platforms like Salesforce, some of the "product" apps that we see adopting native integrations instead of directing users to Zapier include apps that require:

1) synchronous interactive integrations and not just background automation. e.g. a user pulling a lead from Salesforce into a marketing app.

2) complex/multi-step integrations that offer way better UX and much lower support costs to just build natively for users.

3) integrations as a competitive differentiator, or without requiring users to pay for third-party tools.

4) integrations without an API of their own to integrate to.

That said, there are always a long tail of apps and use cases so I'm certain we'll see more specialized tooling pop up to handle specific complex workflows.

Agree with the commit message; I've probably spent way too much time the past decade firing up a python prompt or using an online epoch converter to do this.

I was curious and looked this up on Wikipedia [0]:

> It has been hypothesized that the 555 got its name from the three 5 kΩ resistors used within, but Hans Camenzind has stated that the number was arbitrary. [1]

[0] https://en.wikipedia.org/wiki/555_timer_IC#Design [1] http://www.semiconductormuseum.com/Transistors/LectureHall/C...