This has been my experience as well. It's incredibly grating to repeatedly read "genuinely load-bearing", "honestly?", etc. I've tried to get Opus to stop using these phrases via an entry in its memory, with mediocre results.
I think the disconnect here is that Google engineers are much more likely to answer the low volume of technical "nerd-snipey" questions from other developers than the high volume of non-technical questions they'd get from the general public for something like Gmail.
I had to google "cosplay market size" to confirm, but the paper's assertion that it's a billion-dollar industry does appear to be correct (!)
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.
I feel that complex workflows are best served by dedicated integrations, but it takes time for developers to build each integration natively into a product. We launched https://kloudless.com to simplify the process for app developers to natively integrate an entire category of SaaS services at once (I'm a co-founder).
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.
The critical component, MS Teams, is missing in G Suite. Google Chat feels more like posting on an internal message board, since it centers around creating threads rather than actual chatrooms. I can see why companies using G Suite, including ours, prefer Slack's UX or MS Teams' central approach to collaborate in Office 365.
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]