Anyone knows if they plan to deprecate V3 (which is likely) and when?
GitHub announcements: Marketplace, Apps and GraphQL API
31–40 of 166 posts
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#32After trying new GitHub Desktop Beta mentioned in the article a week ago: it's still nowhere near compete enough to work: - You can only stage all changes in a file - so you can't discard 'console.log('Wooo'); debugger;' when committing, you have to remove those in your editor first, then commit. - you can't reverse commits. Need to roll HEAD back to a previous commit, push those fixes, then resume what you were work…
> You can only stage all changes in a file
If I'm understanding you correctly, this is wrong. You can add individual lines in a file to your commit. That's one of the main uses I have for the app: it's easier to split up file changes between commits than on the command line. See this screenshot: http://imgur.com/a/4CQG7 You have to click on the line numbers to add/remove individual lines.
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#33Earlier quoted context omitted.
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.
You should read about REST then :)
I have, a lot, and when I could only GET kinds of hierarchical data instead of lumping nested queries, I turned to graphQL (or a, er, homegrown subset of it - it had just been announced) to fill in the gaps. It turns out that most software doesn't, really, care about asking for or updating 'state' per se, and the amount of awkward munging you have to do interpret every kind of query as 'asking about state' is, in my opinion, largely pointless.
The REST philosophy is so conceptually big that it's useless for actually building a system; what I meant by 'in practice' is that REST in practice is 'how do I stuff what I want into the http verbs and make it seem plausibly like state transfer' and that's an exercise that I can't see myself doing 'for purity' again. (in a simple app that actually is just asking about and updating state, sure, it's fine. But when you have to make ten queries for different records because you can't ask the server to join things for you dynamically, it's less fun.)
(edit: especially when you need the results to be an atomic picture of the underlying data, gathered in a transaction. Do I invent a GET resource for every tuple of values I might want to query directly? Or do I stop blindly following an architecture and do the practical thing and implement real queries? A: Always the latter.)
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#34Earlier quoted context omitted.
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.
Monopoly in what sense? There is certainly healthy competition in the hosted Git repository space.
Not really. There are a couple of also-rans but I'd be amazed if GitHub had less than 95% of the market.
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#35I wonder how this will work with GitHub Enterprise?
GraphQL will be available in GitHub Enterprise 2.10, and GitHub Apps will be available in 2.11. For Marketplace, we will be researching how to solve similar problems for Enterprise customers after this initial launch.
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#36After trying new GitHub Desktop Beta mentioned in the article a week ago: it's still nowhere near compete enough to work: - You can only stage all changes in a file - so you can't discard 'console.log('Wooo'); debugger;' when committing, you have to remove those in your editor first, then commit. - you can't reverse commits. Need to roll HEAD back to a previous commit, push those fixes, then resume what you were work…
> You can only stage all changes in a file If I'm understanding you correctly, this is wrong. You can add individual lines in a file to your commit. That's one of the main uses I have for the app: it's easier to split up file changes between commits than on the command line. See this screenshot: http://imgur.com/a/4CQG7 You have to click on the line numbers to add/remove individual lines.
Not a very obvious UI!
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#37"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.
Atlassian takes 25% fee. If Atlassian takes 25%, GitHub does, if Atlassian has a marketplace, so does GitHub. But Atlassian makes money, while GitHub lost $66m in 9 months of 2016 ( https://developers.slashdot.org/story/16/12/16/1639222/build... ). GitHub is the fallacy of a valuation based on monthly users (33m) instead of based on actual invoices.
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#38Anyone knows if they plan to deprecate V3 (which is likely) and when?
We don't have a timeline yet, but any updates will be posted on the API blog: https://developer.github.com/changes/
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#39How about communities, forums, boards? When I see an interesting project I'd like to talk to the developer without cluttering the Issues section.
It could be the entry point of every repo, moderated by the owner of course (something like php docs where people can post interesting stuff related to the page at the end). And it would make Github more social.
Re: GitHub announcements: Marketplace, Apps and GraphQL API
#40I did not followed recent GitHub news closely. Is GraphQL a new thing at GitHub? And do you think GitHub integration benefits from this?
GraphQL sounds like a cool thing I should be using already. Now let me scroll down to find out why it's a dumpster fire I should avoid at all costs.