Skip to content

Document that barrier is currently not compatible with synergy#77

Closed
p12tic wants to merge 1 commit into
debauchee:masterfrom
p12tic:mention-interop-with-synergy
Closed

Document that barrier is currently not compatible with synergy#77
p12tic wants to merge 1 commit into
debauchee:masterfrom
p12tic:mention-interop-with-synergy

Conversation

@p12tic
Copy link
Copy Markdown
Member

@p12tic p12tic commented Jul 1, 2018

Fixes issue #62. This just documents the current state of affairs without trying to imply anything about the future.

@walker0643
Copy link
Copy Markdown
Member

I see that you're trying to mitigate confusion with this patch and I don't disagree. There are a couple arguments against....

  1. We don't want to say "Barrier isn't compatible with Synergy" or even "isn't compatible at this time" because we don't want people to assume that it's still true after we (hypothetically) have changed it just because they read it somewhere once. As I said in the issue you referenced, it may change now that Symless has moved back to the 1.x branch. In the very least I don't want to rule it out.

  2. Removing compatibility with Synergy was a conscious choice made for reasons (TM). Barrier may have been born from Synergy (which was born from CosmoSynergy) but it has gone its own way since (and so has Synergy). Especially in the main site readme we don't want to introduce the idea that "Barrier isn't compatible with Synergy" because the real message should be "Barrier isn't Synergy".

@walker0643 walker0643 closed this Jul 1, 2018
@p12tic
Copy link
Copy Markdown
Member Author

p12tic commented Jul 1, 2018

OK, agreed.

@p12tic p12tic deleted the mention-interop-with-synergy branch January 10, 2021 12:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants