no-privacy

Some people do not want to have a social or personal connection with their colleagues. But they still want a deep connection, and they look for that through the work itself. By doing it together, by talking about it, and by talking about the process behind the work, and the big ideas they have about all that.

But if they get matched with a colleague who wants to build a connection by getting to know the person beyond that, then that doesn't work well.

Hi Scott, you might want to see a recent HN thread about Adobe's billing practices here: https://news.ycombinator.com/item?id=30222165

It is a manipulative trick to offer users a 7 day free trial, and then lock them onto an annual plan, with penalty for early termination.

Figma use the word "open" to describe some restrictive APIs in their wall garden, which is disingenuous coming from programmers who know what "open" really means.

Usually collaboration is done using a Git-like external version control tool or just file syncing with Dropbox. Even Adobe Photoshop stores your data in files that you can share as you like. Figma's collaborative approach is certainly good UX, but on the whole a net-negative for the world if it catches on.

If your code is stored exclusively on GitHub and can only be edited through the UI then you are at GitHub's continued mercy to have access to your own data. You lose it when your subscription expires or when GitHub thinks they no longer like you. This is the general trend of software turning into services and they are actually locking you in with your own data. But it is also a challenge to provide seamless realtime collaboration on the same document if sits in files rather than on the web. The best of both worlds would be a software that has both the convenience and openness of individual files and has seamless collaboration.