Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GraphQL #315

Open
JakeHartnell opened this issue Feb 14, 2017 · 10 comments
Open

GraphQL #315

JakeHartnell opened this issue Feb 14, 2017 · 10 comments
Labels
Milestone

Comments

@JakeHartnell
Copy link
Member

JakeHartnell commented Feb 14, 2017

@aruntk
Copy link
Contributor

aruntk commented Feb 14, 2017

@JakeHartnell Do you want to stick with polymer as the frontend?

@JakeHartnell
Copy link
Member Author

For now. Unless it's lots of work...

Thoughts?

@aruntk
Copy link
Contributor

aruntk commented Feb 14, 2017

I guess it is okay to continue with polymer for now. But In my opinion react is the better FE framework.

@JakeHartnell
Copy link
Member Author

I guess it is okay to continue with polymer for now. But In my opinion react is the better FE framework.

Polymer was good experiment, but I agree. As of now react is much better for building something we can put into production. I was noticing a decent sized list of problems in browsers that weren't chrome...

@JakeHartnell JakeHartnell mentioned this issue Feb 15, 2017
@aruntk
Copy link
Contributor

aruntk commented Feb 15, 2017

@JakeHartnell In my opinion polymer is good enough (even better in some respects) for small apps/prototypes. My biggest issue with polymer is it's limited programming model. ie helper elements, bounded properties and helper functions cant match the flexibility offered by react. I hate the way they designed observers(for example compared to $watch in vuejs) and behaviors( it is getting deprecated in 2.0, thankfully), the use of link imports (which is way inferior to es6 imports). One issue I had in the past with the state management and data flow can now be solved using polymer-redux or google/uniflow-polymer. I'm trying to solve the lack of build tools myself. I think these issues will get solved as the popularity increases.

Biggest plus with polymer is it's simplicity(there is nothing much to understand anybody can create a functioning front end). Learning curve is almost nonexistent. You'll get things done much faster in the initial phase.

@JakeHartnell
Copy link
Member Author

JakeHartnell commented Mar 28, 2017

@aruntk It would be cool if we used https://github.com/CommonGarden/graphql-api in this main Grow-IoT repo.

@aruntk
Copy link
Contributor

aruntk commented Mar 31, 2017

@JakeHartnell
Copy link
Member Author

https://github.com/matteodem/graphqlizer

@JakeHartnell
Copy link
Member Author

@JakeHartnell
Copy link
Member Author

JakeHartnell commented Nov 18, 2017

So, we're going to try an experiment and test out our new Open Collective: https://opencollective.com/grow-iot

If we can get Grow-IoT using GraphQL then we'll be a step closer to moving away from Meteor and MongoDB, freeing people up to connect different GraphQL endpoints (and databases such as Postgres, Dynamodb, timescaledb, etc).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants