Readit News logoReadit News
habibur · 4 years ago
This was done as a joke.

Go was released.

Someone else claimed he owns the name "Go" for a programming language. As a proof his github "go language" creation and commit date was shown. This wasn't fake, was real.

Google surely won't give up for this reason. Few days later google extended their go commit to 1972. Preceding that author's date by a long shot.

Guess you can find the news coverage from that time if you search.

throwawaygjdbsj · 4 years ago
Shitty joke. It was bought up in issue 9 in the golang repo and was a pretty big deal at the time.

I still think they should have renamed go to "nine". Alas Google had no problem just steamrolling the guy and then pissing on ten years of his work with a go fuck yourself in the form of this commit.

https://github.com/golang/go/issues/9

bargle0 · 4 years ago
Not unlike Apple steamrolling the Swift language from ANL.

https://www.anl.gov/mcs/swift-fast-parallel-scripting-langua...

geodel · 4 years ago
Perhaps pretty big deal for you. If it were pretty big deal in general we would have seen at least some copyright violation case about it.
metadat · 4 years ago
dsymonds strikes again..

David Symonds is a known type of bad actor within Google. Good luck if he latches onto your project or feature. This individual has consistently demonstrated a knack for deep sixing as much useful efforts as possible while simultaenously avoiding as much work as possible. The worst kind of BOFH developer I've encountered.

https://github.com/golang/protobuf/issues/156

It's just a sad aussie knoll troll situation.

rsc · 4 years ago
This was done as a joke, but not in response to the Go! issue. If you have the original Mercurial repo from the time of the release, you will see it there from the start.

I wrote a longer post about this at https://research.swtch.com/govcs.

dang · 4 years ago
Ongoing discussion here:

Go’s Version Control History - https://news.ycombinator.com/item?id=30333594 - Feb 2022 (8 comments)

cestith · 4 years ago
Many projects have changed names over the years to avoid confusion and give other projects some space in the realm of ideas. Perl was briefly Pearl, but dropped the 'a' due to such a conflict. Microsoft changed from "Git Virtual File System", abbreviated "GVFS", to "Virtual File System for Git", abbreviated "VFS for Git" because there was already a critical mass of articles and documentation for the GNOME Virtual File System. Where a name causes confusion among users, it's good practice to choose a new name even if there's no trademark.

Lots of other projects have similar names across different types of software projects, which can be a little confusing but not as confusing as the same name in the same sphere. "Sphinx" for example represents at least a documentation generator, a search engine and text indexer, a data collection package for research, materials simulation library (as "SPHInX"), an integrated hardware/software access control package, and a network monitoring system. "Argus" is at least a commercial real estate software package, a network and systems monitoring and alerting system similar to Nagios or Sensu, a museum collection management package, a network activity auditing package, safety case management software from Oracle, a high-tech optical analysis system for the sheet metal forming industry, a secure messaging solution for medical information, a suite of system monitoring and management tools for Windows, and an augmented reality (AR) system for support & troubleshooting in multiple manufacturing industries.

As for "Go" for a language, I don't think confusion was likely. This other language doesn't seem to have been in widespread use or documented broadly outside the one project lead's own pages. It might have been kind to this other creator to change the name, but I don't think it was really necessary to avoid pain in the broader community.

p_l · 4 years ago
Well, it's half joke if you know Go's history, but the half serious part would make that commit also the first commit of C++ and Objective-C
Jabbles · 4 years ago
Something about the way git works suggests to me that Google did not in fact just change the timestamp on the first commit in their repository.
Strom · 4 years ago
Force push works just fine for changing timestamps.
samatman · 4 years ago
Something tells me your model of how git works is completely incorrect.
cestith · 4 years ago
Step 1: change system clock

Step 2: make a commit

Step 3: rebase later commits to that commit

Step 4: force push to the main branch

Step 5: correct system clock

Try it. It works.

LAC-Tech · 4 years ago
The "Go!" language, right?

I mean the language was first IIRC.

IshKebab · 4 years ago
Ha sneaky. They messed it up a bit though by putting it in a `macho` directory when Mach-O didn't exist until 1985.
vkoskiv · 4 years ago
So any thoughts on this company, Repography? Their dashboards look really cool, but the only way to give them a go with my own repositories is to authorize their Github app to "Act on my behalf", whatever that means, or to curl some unknown code and pipe that into bash locally on my machine. Neither option is one I'm particularly fond of trying, without additional assurances that this is a legit org. I don't know. I just feel like they could have spent a bit more time convincing me it's safe to do that authorization thing. Likewise, I could have downloaded their script and audited it before running - I just don't have the time to do that right now.
arraypad · 4 years ago
Hi, I'm Arpad, one half of Repography.

There's an entry in our FAQ [1] about this. We only use OAuth to identify your GitHub account and then the GitHub app installation has much better defined permissions.

I'd love to be able to restrict the OAuth scope even further but GitHub doesn't let us. I've heard this concern a couple of times now so I'll have another look. I can hopefully at least improve how it's presented and communicated so it's more reassuring!

[1] https://repography.com/faq

red2awn · 4 years ago
The back button is broken on your website.
TazeTSchnitzel · 4 years ago
This seems to be a joke, but I was expecting it might be serious, because (AIUI) the Go compiler is derived from the Plan 9 C compiler. Of course, that was probably not started in 1972, but it does mean Go's source code is older than the language itself.
hobomatic · 4 years ago
One of the more strikingly recognizable steps along the way is the alef programming language, also a plan9/bell labs baby.
roboyoshi · 4 years ago
Russ cox wrote about it too: https://research.swtch.com/govcs
zarakshR · 4 years ago
How would that even work if git was released in 2005? Am I missing something?
zegl · 4 years ago
It’s just a joke. When creating a commit, you can override the timestamp to whatever you want.
csunbird · 4 years ago
chrisseaton · 4 years ago
A date is just a number in a file. You can create Git commits with any date you want.
rgoulter · 4 years ago
For the sake of interest, not quite any date.

https://stackoverflow.com/questions/21787872/is-it-possible-...

e.g. this repo which represented the US constitution in a Git repository couldn't use the actual dates it wanted to. https://github.com/JesseKPhillips/USA-Constitution#who-made-...

noselasd · 4 years ago
I have git repos with commits from before 2005 in projects converted from cvs, to subversion to git.
_ph_ · 4 years ago
Obviously, code that old couldn't have been originally committed to git. But it is quite common to have old repositories migrated to git and one would expect the original time stamps been maintained after the migration.
bregma · 4 years ago
In 1972 the web was still only available in black and white and a typical consumer laptop was the size of a steamer trunk.
iib · 4 years ago
You can modify the git history to your liking. There are tools for that, like reposurgeon [1].

[1] https://gitlab.com/esr/reposurgeon

alfredbez · 4 years ago
ksherlock · 4 years ago
There seems to be a lot of confusion. Check out the GIT_AUTHOR_DATE (or git commit --date) and GIT_COMMITTER_DATE environment variables for more insight.
kleton · 4 years ago
Presumably the original first commit was a CL on perforce, and copybara did not yet exist, so they arbitrarily did this when exporting to git.