21–30 of 166 posts
Congratulations to the GitHub team for a great release here on the new Marketplace. I'm Matt - CEO at ZenHub [1], one of the launch partners for the Marketplace. We've been building apps on top of the GitHub platform for 3 years now and watching the evolution has been amazing. The three releases here have really helped with our biggest integrator pain points: GraphQL - better and faster access to data without hitting…
Earlier quoted context omitted.
GraphQL is a method of creating APIs for consumption by e.g. JavaScript apps or mobile apps that is gaining popularity at the moment. So it can be seen as a successor to REST. It gives you a pretty easy query language to specify which data on which objects you are interested in and that data is then fetched for you. An example could be a React app where each component specifies which data it needs to work on, and the…
REST and GraphQL are two completely different things, and one is not a replacement for the other. REST is an architectural concept, whereas GraphQL is a query language spec. https://philsturgeon.uk/api/2017/01/24/graphql-vs-rest-overv...
I'm a partner at Codetree[1], one of the four launch partners in the project management category of GitHub Marketplace[2]. Happy to answer questions about our experiences working with the GH team to integrate, why we decided to list in Marketplace, etc. [1] - http://blog.codetree.com/articles/project-management-launch-... [2] - https://github.com/marketplace/codetree
"Once your revenue reaches a minimum of $500 USD for the month, you'll receive an electronic payment from GitHub for 75% of the sales price." So it looks like Github takes a 25% fee. I thought maybe they would do something more innovative regarding the fee structure, or maybe have a lower intro fee like 15%. But here is seems pretty much on par with the 30% of the Heroku marketplace.
Wow, i think 25% is more than enough, they don't have costs that justify 25%. It's just their monopoly that allows them to charge that much.
Hm, I like Github but I don't like this. This is a great move, but we already have a code hosting monoculture, and this subtly piggy-backs on it towards lock-in for tooling. Github knows orgs have inertia. Sorry for the slippery slopeism. I'm just imagining a future where shipping an app without a middleman moves to inconvenient, then annoying, then difficult, then impossible. Because this is exactly how we lost the…
- Docker - Heroku - AWS - Google - Direct
Feels more for "discovery" than purchasing.
Earlier quoted context omitted.
REST and GraphQL are two completely different things, and one is not a replacement for the other. REST is an architectural concept, whereas GraphQL is a query language spec. https://philsturgeon.uk/api/2017/01/24/graphql-vs-rest-overv...
That's true in theory, but in practice REST is a (limiting) spec for the kinds of verbs you're allowed to use between systems, and graphQL is a significant and much needed expansion of that.
Earlier quoted context omitted.
REST and GraphQL are two completely different things, and one is not a replacement for the other. REST is an architectural concept, whereas GraphQL is a query language spec. https://philsturgeon.uk/api/2017/01/24/graphql-vs-rest-overv...
That's true in theory, but in practice REST is a (limiting) spec for the kinds of verbs you're allowed to use between systems, and graphQL is a significant and much needed expansion of that.
Earlier quoted context omitted.
GraphQL is a method of creating APIs for consumption by e.g. JavaScript apps or mobile apps that is gaining popularity at the moment. So it can be seen as a successor to REST. It gives you a pretty easy query language to specify which data on which objects you are interested in and that data is then fetched for you. An example could be a React app where each component specifies which data it needs to work on, and the…
REST and GraphQL are two completely different things, and one is not a replacement for the other. REST is an architectural concept, whereas GraphQL is a query language spec. https://philsturgeon.uk/api/2017/01/24/graphql-vs-rest-overv...
Congratulations to the GitHub team for a great release here on the new Marketplace. I'm Matt - CEO at ZenHub [1], one of the launch partners for the Marketplace. We've been building apps on top of the GitHub platform for 3 years now and watching the evolution has been amazing. The three releases here have really helped with our biggest integrator pain points: GraphQL - better and faster access to data without hitting…
I'm going to recommend it to others here, with a caveat: I really wish it would not be so aggressively hijacking the Github UI.
Tabs and side panels move around because the JS on the page finishes executing, making the Github UI feel super sluggish. We also have a lot of projects which end up with the settings tab in a "More" dropdown, despite Boards and Reports being more easily accessible from keyboard shortcuts (and we don't even use Reports)...
All those features are great, but there's no option to turn them off at the UI level, or customize them in any way. Very annoying :(