Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub-Next

githubnext.com

Post reply on HN
Print view View original

81–90 of 119 posts

Re: GitHub-Next

#81

Post by bastardoperator »

saurik wrote: post #41
vemv wrote: post #36

> GitHub Next investigates the future of software development. Yesterday I tried to use Datadog's Github integration for stacktraces and it asked me for "access Github on my behalf". It's been the same since the beginning of Github - they leave integrators with no better options, and users with an ambiguous UI dialog / docs that downplay the scope being granted. Sooooo maybe fix your own stuff before making such gran…

Why wouldn't this be done over git? It seems almost ridiculous for this to be a GitHub-specific API and authentication mechanism instead of merely authorizing an SSH key from Datadog (which would then allow whatever this service is doing with the source code to also work for any other source code hosting solution).

Metadata lives in the API, not the git repo. I would argue a github app with rotating hourly tokens which datadog seems to support is better than a users ssh key or an ssh key with access to many repos.

Re: GitHub-Next

#82

Post by 2Gkashmiri »

tpmoney wrote: post #71
2Gkashmiri wrote: post #66

Earlier quoted context omitted.

you know what i mean... i am talking about training it on windows OS code and adobe photoshop source code and other "proprietary software" code

Because scraping a public website is different from breaking into adobes private source control servers?

there is public DB of windows code out there, if "cant" is the word then let users submit the injest code and let it train on it. if "wont" is the word then who gave them the permission?

Re: GitHub-Next

#83

Post by blackoil »

2Gkashmiri wrote: post #10
blackoil wrote: post #9

Earlier quoted context omitted.

That's such a vague and novel area, that I don't think lawyers will recommend/allow commenting on it unless required by court of law. There is no precedent on if a computer reading your code or looking at the image is fair-use or not.

why not train it on copyright material also? whats the prima-facie reason for not doing so? i mean if you are doing "all public repos", why not everything else?

Officially, Github does not have access to those repos. It manages them doesn't mean all team have access to them.

Re: GitHub-Next

#84

Post by bern4444 »

Regarding visualization of codebases, something I've wanted for a long time is a graph of function calls across an entire project.

I want to know all the callers and callees of every function. This shouldn't be too hard, we already have find references via LSP.

Turning this into a graph would make it significantly easier to manage the entry and exit points of a code base and inform architecture decisions, refactors, type checking, hot paths etc.

Re: GitHub-Next

#85

Post by ilovecaching »

I really don't like the two trends Github is pushing for:

1. Code editor is full of telemetry and costs money, only accessible over the internet.

2. Code regressing into lots of boilerplate and automatically copied stack overflow answers by copilot, programmers using less critical thinking skills.

I don't trust Microsoft either.

Re: GitHub-Next

#86

Post by bastardoperator »

jacquesm wrote: post #57
temp-dude-87844 wrote: post #52

Earlier quoted context omitted.

This should absolutely be litigated to stop the blatant laundering of copyright under the guise of fair use. Copilot's API is surfacing snippets of work without licensing information attached alongside. It can be shown in discovery that Copilot does access the origin work. The sooner this is slapped down, the sooner we can avoid addressing the even more troubling question that exists today: is someone who used Copilo…

It's not complex at all: if you use Copilot to generate code for you you are engaging in copyright infringement. That you got the code from and entity that stole it somewhere else doesn't really matter. Generative models should respect copyright for their sources, and using a generative model to create new works that you intend to claim copyright on is stupid: someone may well show up one day with ironclad proof that…

Except every attorney that has taken a look disagrees with you. So it is complex and unless you have any standing or new data I think it's safe to dismiss your entire argument.

https://decoded.legal/blog/2021/06/github-copilot-initial-th...

https://fossa.com/blog/analyzing-legal-implications-github-c...

https://felixreda.eu/2021/07/github-copilot-is-not-infringin...

Re: GitHub-Next

#87

Post by ffhhj »

hbn wrote: post #7

Could they use the blurb of text at the top to give me like... a noun to describe what this is? It just says some vagueness about the future and investigating and exploring. Is it a conference? A team? An initiative? How does it work? Whatever this is supposed to be selling me on, they're doing a terrible job because I can't figure out what it is!

It's just a rebranding of GitHub OCTO:

https://github.com/githubocto

Re: GitHub-Next

#88

Post by FinalBriefing »

cmeacham98 wrote: post #47
cush wrote: post #26

Earlier quoted context omitted.

Did they add this in the last 40 mins? I'm seeing a pretty good description: " GitHub Next investigates the future of software development. We explore things beyond the adjacent possible. Tools and technologies that will change our craft. New approaches to building healthy, productive software engineering teams. "

That explains what it does (somewhat vaguely), but not what Github Next is and who makes it up. Is it a team at GitHub that employees work on full time? It it some kind of initiative where GitHub employees spend part of their time working on it? Is it a community effort? Am I able to join in?

I think you're thinking too hard about it. It's just a list of R&D projects that might be interesting to some people.

Or maybe they just updated the site in the last hour. It's got a list of team members and events and stuff.

Re: GitHub-Next

#89

Post by avg_dev »

bern4444 wrote: post #84

Regarding visualization of codebases, something I've wanted for a long time is a graph of function calls across an entire project. I want to know all the callers and callees of every function. This shouldn't be too hard, we already have find references via LSP. Turning this into a graph would make it significantly easier to manage the entry and exit points of a code base and inform architecture decisions, refactors,…

That’s a cool idea. I don’t know much about ASTs or anything but I know you are right about LSP being able to find most everything I am searching for in the mostly statically typed languages I’ve worked with. Would be fun to try that out over a weekend or three.

Re: GitHub-Next

#90

Post by avg_dev »

jacquesm wrote: post #14
Thev00d00 wrote: post #6

Earlier quoted context omitted.

Wow, that's crazy. Do we have something official that says as much?

It's infuriating, when you are large enough you can get away with anything when it comes to copyright violations but I remember the crazy pushback on things like format and time shifting against private individuals.

What is format and time shifting? I am wondering if you mean like code formatting and reordering history, but I’m not really sure. Thanks.
Post reply on HN