so as i understand, the benefit is that React encourages standard I/O. but i also understand that nothing is stopping anyone from using a standard I/O with Backbone or Ember (which i recognize is why you say "from different people").
my point is that it's a people problem as much as a tooling problem. or is it impossible to build incompatible React views?
i'm currently working on a library that makes it easy to share patches (GUI included) for audio applications. i'm using React. one problem i struggle with is that without my own additional standard, nothing is preventing anyone from making a component that can't patch in. which is the same problem i would have if i were using Backbone.
if you're looking for a "standard" way to share components you need to make assumptions about what type of GUI you are building- not just how you are building it.
my point is that it's a people problem as much as a tooling problem. or is it impossible to build incompatible React views?
i'm currently working on a library that makes it easy to share patches (GUI included) for audio applications. i'm using React. one problem i struggle with is that without my own additional standard, nothing is preventing anyone from making a component that can't patch in. which is the same problem i would have if i were using Backbone.
if you're looking for a "standard" way to share components you need to make assumptions about what type of GUI you are building- not just how you are building it.