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

Cloud Source Repositories

cloud.google.com

Post reply on HN
Print view View original

41–50 of 74 posts

Re: Cloud Source Repositories

#41

Post by dvlsg »

ImJasonH wrote: post #19
cdoxsey wrote: post #12

It wasn't all that long ago that Google shut down Google Code. They said: https://opensource.googleblog.com/2015/03/farewell-to-google... > After profiling non-abusive activity on Google Code, it has become clear to us that the service simply isn’t needed anymore. And now they've created a new product which does pretty much the same thing... Wonder how long this one will last.

I disagree that CSR serves the same purpose as code.google.com, and is likely to meet a similar end. code.google.com hosted public repos, issues, wiki, downloads, etc., and was generally just ripe for abuse. Google created it largely because Sourceforge was the only thing that existed at the time, and it wasn't doing a great job. Today there's GitHub, Bitbucket, Gitlab, and more. CSR is primarily for hosting private…

Proper code search could be a pretty killer feature on its own. Half the time I need to find something on github I just clone the repo and search from my own computer.

Re: Cloud Source Repositories

#43

Post by tyingq »

dvlsg wrote: post #41
ImJasonH wrote: post #19

Earlier quoted context omitted.

I disagree that CSR serves the same purpose as code.google.com, and is likely to meet a similar end. code.google.com hosted public repos, issues, wiki, downloads, etc., and was generally just ripe for abuse. Google created it largely because Sourceforge was the only thing that existed at the time, and it wasn't doing a great job. Today there's GitHub, Bitbucket, Gitlab, and more. CSR is primarily for hosting private…

Proper code search could be a pretty killer feature on its own. Half the time I need to find something on github I just clone the repo and search from my own computer.

Heh, yes. Github's search is case insensitive and ignores sigils, braces, etc.

Re: Cloud Source Repositories

#44

Post by sanderjd »

tyingq wrote: post #43
dvlsg wrote: post #41

Earlier quoted context omitted.

Proper code search could be a pretty killer feature on its own. Half the time I need to find something on github I just clone the repo and search from my own computer.

Heh, yes. Github's search is case insensitive and ignores sigils, braces, etc.

I've been waiting years for GitHub to put some real effort into code search and cross-linking. I had given up on it, but I suspect this will be a high priority for Microsoft.

Re: Cloud Source Repositories

#45

Post by jchw »

derefr wrote: post #17
013a wrote: post #14

My biggest complaint with Google Cloud's UX, which applies to their new Cloud Source Repositories opt-in UI: They shard out so many of their user experiences into different websites and domains. Under the umbrella of Google Cloud you've got Google Cloud Console, Firebase, Stackdriver, Source Repositories, Dialog Flow, probably a couple others I'm forgetting. Almost all of these have entries on the Google Cloud Consol…

> I want to see a better unifying vision for what being a Google Cloud customer actually means The thing you've got to understand is that none of these products are "Google Cloud" products. They're Google services (or, even moreso, services of random third parties which Google has acquired) that you happen to be able to hook into from your GCP project and access through the GCP CLI. The closest comparison I can think…

It is true that a lot of GCP services were once external, like Firebase and Stackdriver, and it is true that there are numerous different domains and UIs that you manage GCP products under, but I believe the future direction is definitely towards unifying things, and the split right now is probably mostly technical. This isn't an official statement by any means, though.

Re: Cloud Source Repositories

#46

Post by Ayyar »

Xoogler here.

Internally as Google, you have a substantially power powerful version of Codesearch, which is semantic, i.e. it relies on actual binary artifacts produced by builds to index code. All of the code base uses Blaze ( open sourced as Bazel) to express the rules.

The version of code search here is cute, but it's still not a full blown structured semantic code search, which I really miss. Searching for and browsing code on Github feels underwhelming in comparison, because you wan't really find or explore code the way you think of it.

You can see a demo of semantic Codesearch tech externalized here at:

https://blog.bazel.build/2017/12/14/introducing-bazel-code-s... http://cs.chromium.org

For example if you click on a header or a symbol, you can get proper cross references to a symbol.

https://cs.chromium.org/chromium/src/pdf/document_loader_imp...

I really wish they add structured code search to Cloud Repos, even if it comes with some heavy restrictions such you must use Bazel as a build system.

It would be a killer feature, and to my knowledge there is no equivalent to such a product. IDEs offer some similar overlapping functionality, though other code search engines still operate in terms of strings rather than actually real binary symbols ( I think Sourcegraph is trying here but that still does not seem to use some kind of accurate and structured information like you have in the code, it still seems not use build rules).

Re: Cloud Source Repositories

#47

Post by manigandham »

dickeytk wrote: post #38

tl;dr: this isn't replacing github, it's solving a more specific problem I think everyone here is missing the point. The purpose here seems to be similar to github actions in providing workflows around repository events (though also including some basic ability to view the code as well). Having a clean way to cut a release that updates app servers on app engine and serverless functions in tandem is needed right now.…

>> Having a clean way to cut a release that updates app servers on app engine and serverless functions in tandem is needed right now.

This is the entire field of CI/CD with dozens of providers, including Github and Gitlab too.

Re: Cloud Source Repositories

#48

Post by derefr »

skj wrote: post #39
derefr wrote: post #17

Earlier quoted context omitted.

> I want to see a better unifying vision for what being a Google Cloud customer actually means The thing you've got to understand is that none of these products are "Google Cloud" products. They're Google services (or, even moreso, services of random third parties which Google has acquired) that you happen to be able to hook into from your GCP project and access through the GCP CLI. The closest comparison I can think…

I can tell you that your view does not match that of the engineers working on these products. If something is namespaced under a project and you use the cloud console or CLI to manage it, it is very much a GCP product. (I am one such engineer, and have worked on the CLI, cloud build, and container services)

You’re speaking of design intent, I think. I’m speaking of point-in-time experience from a user perspective. It’s clear what GCP wants to transition toward—but:

1. that’s not where many GCP-aegis’ed services are right now, and

2. newly-absorbed Google properties will always start out looking like this, so there’ll never be a time when GCP won’t look at least somewhat like this (unless the post-acquisition integration process is changed drastically.)

Re: Cloud Source Repositories

#49

Post by toeenredbluo »

Ayyar wrote: post #46

Xoogler here. Internally as Google, you have a substantially power powerful version of Codesearch, which is semantic, i.e. it relies on actual binary artifacts produced by builds to index code. All of the code base uses Blaze ( open sourced as Bazel) to express the rules. The version of code search here is cute, but it's still not a full blown structured semantic code search, which I really miss. Searching for and br…

How do you deal with things like system headers then? Force everyone to check in their OS (bye BSDs)? Assume everyone runs the same OS?

How do you deal with compiler provided internals, where someone might be using clang which has behavior X, but gcc / icc / msvc doesn't?

These problems are more prominent in C/C++, but are everywhere... Not easy...

Google can probably check in everything for themselves... Probably not so easy for other companies? Maybe? Can Google solve this without sinking too much resources into it?

Re: Cloud Source Repositories

#50

Post by sqs »

Ayyar wrote: post #46

Xoogler here. Internally as Google, you have a substantially power powerful version of Codesearch, which is semantic, i.e. it relies on actual binary artifacts produced by builds to index code. All of the code base uses Blaze ( open sourced as Bazel) to express the rules. The version of code search here is cute, but it's still not a full blown structured semantic code search, which I really miss. Searching for and br…

> I think Sourcegraph is trying here but that still does not seem to use some kind of accurate and structured information like you have in the code, it still seems not use build rules

Sourcegraph does use language servers (same as your editor would use) to get precise definitions and references.

For example ("find references" on some open-source code):

Go: https://sourcegraph.com/github.com/theupdateframework/notary...

TypeScript: https://sourcegraph.com/github.com/ReactiveX/rxjs/-/blob/src...

It understands many build tools, but not all. Go, JavaScript, TypeScript, Java, Python, and PHP support is all pretty solid. If you use the most common build tools for your language, it usually works well. It degrades un-gracefully if you use custom build tools or scripts, unfortunately, but we're working on making it support more build tools and customization. Sourcegraph development is open source; if you notice any problems, let us know in the issue tracker at https://github.com/sourcegraph/sourcegraph.

Post reply on HN