2 ms·

Exactly - making context switches cheaper isn't very helpful if you're doing so at the expense of making context switches more frequent[0]. [0] and easier to d

• calinet6 13y ago
  This is a silly argument. You're all assuming this type of integration will be have the UI quality of your dishwasher. Of course context switches and irrelevant information will be distracting if done poorly. This is a UX challenge—not a reason to abandon the idea. Having the focus you need during concentrated tasks such as coding, while also enabling the integration of other tasks—such as high-level team context awareness and collaboration—is the key design challenge. Done well, it would be a killer app. Done poorly, as with anything, it will fail miserably. Programmers have a poor reputation for UI design prowess, and programmers tools are sadly usually made by programmers, and thus carry the same reputation. Very few amalgam programmer/designers exist to bridge the gap of motivation and ability to design a better toolset. But they do exist. Let's be optimistic, shall we?