search

tylerbenson / vyllage

https://www.vyllage.com
4 stars 0 forks source link

Investigate JS Data #777

Open tylerbenson opened 9 years ago

tylerbenson commented 9 years ago

http://www.js-data.io/

Would this be something useful?

tarex commented 9 years ago

checked their examples and their video presentation , IMO , i have found some similarities with facebook s relay , on relay we need to follow the GraphQL structure , GraphQL server implementation but in the Js-data , it has its own schema library and we can use RESTful api too , It needs server based implementation too , that is also required for the relay . I'm not sure about how it will do for the big application when data is complex , it will replace our reflux implementation . its stand on object.observe , so i think inside this it has lot of dirty checking, for framework agnostic work it can be useful . I'd prefer to go with relay for the future work .

tylerbenson commented 9 years ago

That sounds reasonable, but rather invasive. Would there be enough upside to make up for the work required?

tarex commented 9 years ago

for now we shouldn't use relay but many startup's are trying to adopt it . i'm still learning it , trying to build a CRUD application , it needs significant sever side changes . so it wouldn't be good idea to move right now but future we can try for couple of item .

nelonoel commented 9 years ago

How about React Transmit (https://github.com/RickWong/react-transmit)? It follows the same model as Relay (moves away from React mixins too!) but works with Promises instead of GraphQL queries. :)